From: "Paul E. McKenney" <paulmck@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Zqiang <qiang.zhang1211@gmail.com>,
joel@joelfernandes.org, chenzhongjin@huawei.com,
rcu@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] linux-4.19/rcu-tasks: Eliminate deadlocks involving do_exit() and RCU tasks
Date: Sun, 25 Feb 2024 11:03:03 -0800 [thread overview]
Message-ID: <59861bc8-a651-4199-a60d-2cb39b3568a9@paulmck-laptop> (raw)
In-Reply-To: <2024022430-uninsured-zoom-f78c@gregkh>
On Sat, Feb 24, 2024 at 06:16:24AM +0100, Greg KH wrote:
> On Fri, Feb 23, 2024 at 11:48:49AM -0800, Paul E. McKenney wrote:
> > On Fri, Feb 23, 2024 at 02:15:30PM +0100, Greg KH wrote:
> > > On Wed, Feb 07, 2024 at 07:08:46PM +0800, Zqiang wrote:
> > > > From: Paul E. McKenney <paulmck@kernel.org>
> > > >
> > > > commit bc31e6cb27a9334140ff2f0a209d59b08bc0bc8c upstream.
> > >
> > > Again, not a valid commit id :(
> >
> > Apologies! With luck, there will be a valid ID next merge window.
> > This one does not backport cleanly, so we were trying to get ahead of
> > the game. Also, some of the people testing needed the backport due
> > to the usual issues. :-/
> >
> > Any advice to handle this better next time around? (Aside from us
> > avoiding CCing stable too soon...)
>
> You can just wait until it hits Linus's tree, otherwise we do get
> confused :)
>
> Or if you don't want to wait, put it in the notes section below the ---
> line and say "this isn't in Linus's tree yet, the git id mentioned is a
> lie!" or something like that. Give us a chance to figure it out
> please...
Thank you, and should this situation arise in the future, we will put
the disclaimer after the "---", avoid CCing -stable, or similar.
Again, apologies for the hassle!
Thanx, Paul
prev parent reply other threads:[~2024-02-25 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:08 [PATCH] linux-4.19/rcu-tasks: Eliminate deadlocks involving do_exit() and RCU tasks Zqiang
2024-02-12 20:53 ` Paul E. McKenney
2024-02-23 13:15 ` Greg KH
2024-02-23 19:48 ` Paul E. McKenney
2024-02-24 5:16 ` Greg KH
2024-02-24 12:05 ` Z qiang
2024-02-25 19:03 ` Paul E. McKenney [this message]
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=59861bc8-a651-4199-a60d-2cb39b3568a9@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.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).