From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Chen <david.chen@nutanix.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"neeraju@codeaurora.org" <neeraju@codeaurora.org>
Subject: Re: Request for backport fd6bc19d7676 to 4.14 and 4.19 branch
Date: Mon, 16 Aug 2021 21:30:30 +0200 [thread overview]
Message-ID: <YRq81jcZIH5+/ZpB@kroah.com> (raw)
In-Reply-To: <CO1PR02MB8489A10983A22C72447EEB5C94FD9@CO1PR02MB8489.namprd02.prod.outlook.com>
On Mon, Aug 16, 2021 at 07:19:34PM +0000, David Chen wrote:
> Hi Greg,
>
> We recently hit a hung task timeout issue in synchronize_rcu_expedited on 4.14 branch.
> The issue seems to be identical to the one described in `fd6bc19d7676 rcu: Fix missed wakeup of exp_wq waiters`
> Can we backport it to 4.14 and 4.19 branch?
> The patch doesn't apply cleanly, but it should be trivial to resolve, just do this
>
> - wake_up_all(&rnp->exp_wq[rcu_seq_ctr(rsp->expedited_sequence) & 0x3]);
> + wake_up_all(&rnp->exp_wq[rcu_seq_ctr(s) & 0x3]);
>
> I don't know if we should do it for 4.9, because the handling of sequence number is a bit different.
Please provide a working backport, me hand-editing patches does not
scale, and this way you get the proper credit for backporting it (after
testing it).
You have tested, this, right?
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-16 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 19:19 Request for backport fd6bc19d7676 to 4.14 and 4.19 branch David Chen
2021-08-16 19:30 ` Greg Kroah-Hartman [this message]
2021-08-16 22:02 ` David Chen
2021-08-17 6:16 ` Greg Kroah-Hartman
2021-08-17 18:47 ` David Chen
2021-08-18 6:55 ` Greg Kroah-Hartman
2021-08-19 0:28 ` David Chen
2021-09-23 7:52 ` Greg Kroah-Hartman
2021-08-18 7:19 ` Neeraj Upadhyay
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=YRq81jcZIH5+/ZpB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david.chen@nutanix.com \
--cc=neeraju@codeaurora.org \
--cc=paulmck@linux.vnet.ibm.com \
--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