From: Carlos Llamas <cmllamas@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, boqun.feng@gmail.com, bvanassche@acm.org,
gregkh@linuxfoundation.org, longman@redhat.com,
paulmck@kernel.org, xuewen.yan@unisoc.com, zhiguo.niu@unisoc.com,
kernel-team@android.com, penguin-kernel@i-love.sakura.ne.jp,
peterz@infradead.org
Subject: Re: [PATCH 5.4.y 0/4] lockdep: deadlock fix and dependencies
Date: Sun, 13 Oct 2024 15:29:34 +0000 [thread overview]
Message-ID: <ZwvnXnLRLCiNhfmk@google.com> (raw)
In-Reply-To: <ZwvX3kxg6OoarzW9@sashalap>
On Sun, Oct 13, 2024 at 10:23:26AM -0400, Sasha Levin wrote:
> On Sat, Oct 12, 2024 at 11:22:40PM +0000, Carlos Llamas wrote:
> > This patchset adds the dependencies to apply commit a6f88ac32c6e
> > ("lockdep: fix deadlock issue between lockdep and rcu") to the
> > 5.4-stable tree. See the "FAILED" report at [1].
> >
> > Note the dependencies actually fix a UAF and a bad recursion pattern.
> > Thus it makes sense to also backport them.
>
> Hm, it does not seem to apply on 5.4 for me. Could you please take a
> look?
I'm not sure where the disconnect is, I am able to do ...
$ git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.4.y
$ git fetch FETCH_HEAD
$ b4 shazam https://lore.kernel.org/all/20241012232244.2768048-1-cmllamas@google.com/
... with no issues. I don't have anything on my gitconfig that would
change the default behavior of `git am` or `git cherry-pick` either.
Anything else I should try or look into?
--
Carlos Llamas
next prev parent reply other threads:[~2024-10-13 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 23:22 [PATCH 5.4.y 0/4] lockdep: deadlock fix and dependencies Carlos Llamas
2024-10-12 23:22 ` [PATCH 5.4.y 1/4] locking/lockdep: Fix bad recursion pattern Carlos Llamas
2024-10-12 23:22 ` [PATCH 5.4.y 2/4] locking/lockdep: Rework lockdep_lock Carlos Llamas
2024-10-12 23:22 ` [PATCH 5.4.y 3/4] locking/lockdep: Avoid potential access of invalid memory in lock_class Carlos Llamas
2024-10-12 23:22 ` [PATCH 5.4.y 4/4] lockdep: fix deadlock issue between lockdep and rcu Carlos Llamas
2024-10-13 14:23 ` [PATCH 5.4.y 0/4] lockdep: deadlock fix and dependencies Sasha Levin
2024-10-13 15:29 ` Carlos Llamas [this message]
2024-10-14 4:12 ` Sasha Levin
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=ZwvnXnLRLCiNhfmk@google.com \
--to=cmllamas@google.com \
--cc=boqun.feng@gmail.com \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=longman@redhat.com \
--cc=paulmck@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.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