stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: gregkh@linuxfoundation.org, zhiguo.niu@unisoc.com,
	boqun.feng@gmail.com, bvanassche@acm.org, longman@redhat.com,
	paulmck@kernel.org, xuewen.yan@unisoc.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] lockdep: fix deadlock issue between lockdep and rcu" failed to apply to 5.4-stable tree
Date: Sat, 12 Oct 2024 23:25:28 +0000	[thread overview]
Message-ID: <ZwsFaPcHsXqxbL8V@google.com> (raw)
In-Reply-To: <Zwrkj6GC2wT11kb3@sashalap>

On Sat, Oct 12, 2024 at 05:05:19PM -0400, Sasha Levin wrote:
> On Thu, Oct 10, 2024 at 06:29:21PM +0000, Carlos Llamas wrote:
> > On Wed, Oct 02, 2024 at 12:07:26PM +0200, gregkh@linuxfoundation.org wrote:
> > > 
> > > The patch below does not apply to the 5.4-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> > > 
> > > To reproduce the conflict and resubmit, you may use the following commands:
> > > 
> > > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.4.y
> > > git checkout FETCH_HEAD
> > > git cherry-pick -x a6f88ac32c6e63e69c595bfae220d8641704c9b7
> > > # <resolve conflicts, build, test, etc.>
> > > git commit -s
> > > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024100226-unselfish-triangle-e5eb@gregkh' --subject-prefix 'PATCH 5.4.y' HEAD^..
> > > 
> > > Possible dependencies:
> > > 
> > > a6f88ac32c6e ("lockdep: fix deadlock issue between lockdep and rcu")
> > > 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class")
> > > 248efb2158f1 ("locking/lockdep: Rework lockdep_lock")
> > > 10476e630422 ("locking/lockdep: Fix bad recursion pattern")
> > > 25016bd7f4ca ("locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()")
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > These 3 commits are the actual dependencies:
> > 
> > [1] 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class")
> > [2] 248efb2158f1 ("locking/lockdep: Rework lockdep_lock")
> > [3] 10476e630422 ("locking/lockdep: Fix bad recursion pattern")
> > 
> > It seems to me that [1] and [3] are fixes we would also want in 5.4.
> > Possibly also [2] just to make the cherry-picks cleaner. If there are no
> > objections I can send a patchset for linux-5.4.y with all 4?
> 
> SGTM!

OK, I've sent the patches here:
https://lore.kernel.org/all/20241012232244.2768048-1-cmllamas@google.com/

Cheers,
Carlos Llamas

      reply	other threads:[~2024-10-12 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 10:07 FAILED: patch "[PATCH] lockdep: fix deadlock issue between lockdep and rcu" failed to apply to 5.4-stable tree gregkh
2024-10-10 18:29 ` Carlos Llamas
2024-10-12 21:05   ` Sasha Levin
2024-10-12 23:25     ` Carlos Llamas [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=ZwsFaPcHsXqxbL8V@google.com \
    --to=cmllamas@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=longman@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xuewen.yan@unisoc.com \
    --cc=zhiguo.niu@unisoc.com \
    /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 NNTP newsgroup(s).