public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Petr Mladek <pmladek@suse.com>
Cc: stable@vger.kernel.org, akpm@linux-foundation.org,
	jenhaochen@google.com, liumartin@google.com, minchan@google.com,
	nathan@kernel.org, ndesaulniers@google.com, oleg@redhat.com,
	tj@kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH 0/2] kthread_worker: Fix race between kthread_mod_delayed_work()
Date: Mon, 5 Jul 2021 09:10:58 +0200	[thread overview]
Message-ID: <YOKwgmjdIF0Eunaq@kroah.com> (raw)
In-Reply-To: <YNxWIb1GBU0hOE8B@alley>

On Wed, Jun 30, 2021 at 01:31:45PM +0200, Petr Mladek wrote:
> On Wed 2021-06-30 13:06:39, Greg KH wrote:
> > On Wed, Jun 30, 2021 at 01:01:47PM +0200, Petr Mladek wrote:
> > > This is backport of the series for the following stable trees:
> > > 
> > >    + 4.9
> > >    + 4.14
> > >    + 4.19
> > > 
> > > The orignal series did not apply because of a conflict with the commit
> > > ("kthread: Convert worker lock to raw spinlock").
> > > 
> > > Petr Mladek (2):
> > >   kthread_worker: split code for canceling the delayed work timer
> > >   kthread: prevent deadlock when kthread_mod_delayed_work() races with
> > >     kthread_cancel_delayed_work_sync()
> > > 
> > >  kernel/kthread.c | 77 ++++++++++++++++++++++++++++++++----------------
> > >  1 file changed, 51 insertions(+), 26 deletions(-)
> > > 
> > > -- 
> > > 2.26.2
> > > 
> > 
> > What is the original git commit ids of these patches in Linus's tree?
> 
> commit 34b3d5344719d14fd2185b2d9459b3abcb8cf9d8 ("kthread_worker: split code for canceling the delayed work timer")
> commit 5fa54346caf67b4b1b10b1f390316ae466da4d53 ("kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync())"
> 
> The original commits have already been taken for the newer stable trees.
> 
> I am sorry for the inconvenience.

What about backports for 5.4, 5.10, and 5.12?  We can not take patches
only for older kernels, otherwise people upgrading to newer ones would
have a regression.  Please can you submit these patches for those trees
too?  Until that, I can not take these.

thanks,

greg k-h

  reply	other threads:[~2021-07-05  7:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 14:23 FAILED: patch "[PATCH] kthread_worker: split code for canceling the delayed work" failed to apply to 4.19-stable tree gregkh
2021-06-30 11:01 ` [PATCH 0/2] kthread_worker: Fix race between kthread_mod_delayed_work() Petr Mladek
2021-06-30 11:01   ` [PATCH 1/2] kthread_worker: split code for canceling the delayed work timer Petr Mladek
2021-06-30 11:01   ` [PATCH 2/2] kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync() Petr Mladek
2021-06-30 11:06   ` [PATCH 0/2] kthread_worker: Fix race between kthread_mod_delayed_work() Greg KH
2021-06-30 11:31     ` Petr Mladek
2021-07-05  7:10       ` Greg KH [this message]
2021-07-07 10:55         ` Petr Mladek
2021-07-08 18:23           ` Greg KH

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=YOKwgmjdIF0Eunaq@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jenhaochen@google.com \
    --cc=liumartin@google.com \
    --cc=minchan@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=oleg@redhat.com \
    --cc=pmladek@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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