From: Christian Lamparter <chunkeey@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, linux-um@lists.infradead.org
Cc: benjamin.berg@intel.com, sashal@kernel.org, richard@nod.at,
stable@vger.kernel.org
Subject: Re: [PATCH 6.12] Revert "um: work around sched_yield not yielding in time-travel mode"
Date: Sun, 11 May 2025 22:04:46 +0200 [thread overview]
Message-ID: <9086a511-bd3e-4a88-ad86-8c51d5a385ac@gmail.com> (raw)
In-Reply-To: <b09d6b4ef6291a2109dd7e1bada4ecff931a553f.camel@sipsolutions.net>
On 5/11/25 9:23 PM, Johannes Berg wrote:
> On Fri, 2025-05-09 at 11:50 +0200, Christian Lamparter wrote:
>>
>> What's interesting/very strange strange about this time-travel stuff:
>>> commit 0b8b2668f998 ("um: insert scheduler ticks when userspace does not yield")
>>
>> $ git describe 0b8b2668f998
>> => v6.12-rc2-43-g0b8b2668f998
>>
>
> Come to think of it, often you just want "git describe --contains":
>
> $ git describe --contains --match=v* 0b8b2668f998
> v6.13-rc1~18^2~25
yeah, I'm wondering if this 'git describe vs git describe --contains' could be the
reason why the patch was AUTOSEL'd? I have no idea how Sasha's helper works though.
As for UML: Your work is greatly appreciated. I've ran into this because OpenWrt is
currently in the process of adapting to the 6.12 LTS:
https://github.com/openwrt/openwrt/pull/18666
Cheers,
Christian
next prev parent reply other threads:[~2025-05-11 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 9:50 [PATCH 6.12] Revert "um: work around sched_yield not yielding in time-travel mode" Christian Lamparter
2025-05-09 10:03 ` Johannes Berg
2025-05-11 19:23 ` Johannes Berg
2025-05-11 20:04 ` Christian Lamparter [this message]
2025-05-12 13:30 ` Patch "[PATCH 6.12] Revert "um: work around sched_yield not yielding in time-travel mode"" has been added to the 6.12-stable tree gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9086a511-bd3e-4a88-ad86-8c51d5a385ac@gmail.com \
--to=chunkeey@gmail.com \
--cc=benjamin.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).