From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@gmail.com>,
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: Fri, 09 May 2025 12:03:07 +0200 [thread overview]
Message-ID: <05954e6dde3369a0ecf26f5225643afa15850f60.camel@sipsolutions.net> (raw)
In-Reply-To: <20250509095040.33355-1-chunkeey@gmail.com>
On Fri, 2025-05-09 at 11:50 +0200, Christian Lamparter wrote:
>
> What's interessting/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
> (from what I know this is 43 patches on top of v6.12-rc2 as per the man page:
> "The command finds the most recent tag that is reachable from a commit. [...]
> it suffixes the tag name with the number of additional commits on top of the tagged
> object and the abbreviated object name of the most recent commit."
>
> But it was merged as part of: uml-for-linus-6.13-rc1 :
> https://lore.kernel.org/lkml/1155823186.11802667.1732921581257.JavaMail.zimbra@nod.at/
That's not all that implausible - UML maintenance is slow and we all
have a lot of things to do... so chances are we just didn't send a pull
request for 6.12-rc even though the tree was already there. I'm trying
to improve that but it's not really a focus for any of us.
johannes
next prev parent reply other threads:[~2025-05-09 10:46 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 [this message]
2025-05-11 19:23 ` Johannes Berg
2025-05-11 20:04 ` Christian Lamparter
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=05954e6dde3369a0ecf26f5225643afa15850f60.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin.berg@intel.com \
--cc=chunkeey@gmail.com \
--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).