All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Cheng Jui Wang <cheng-jui.wang@mediatek.com>
Cc: stable@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Waiman Long <longman@redhat.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	linux-mediatek@lists.infradead.org,
	Eason-YH Lin <eason-yh.lin@mediatek.com>
Subject: Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
Date: Wed, 16 Mar 2022 15:26:31 +0100	[thread overview]
Message-ID: <YjHzl3Arey7KH0CB@kroah.com> (raw)
In-Reply-To: <6eb2052f463d323b0a82e795d765afb9d5925f6e.camel@mediatek.com>

On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
> Hi Reviewers,
> 
> This patch fixes a use-after-free error when /proc/lockdep is read by
> user after a lockdep splat.
> 
> I checked and I think this patch can be applied to stable-5.4 and
> later. 
> 
> commit: 61cc4534b6550997c97a03759ab46b29d44c0017
> Subject: locking/lockdep: Avoid potential access of invalid memory in
> lock_class

I do not see that commit id in Linus's tree, are you sure it is correct?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Cheng Jui Wang <cheng-jui.wang@mediatek.com>
Cc: stable@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Waiman Long <longman@redhat.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	linux-mediatek@lists.infradead.org,
	Eason-YH Lin <eason-yh.lin@mediatek.com>
Subject: Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
Date: Wed, 16 Mar 2022 15:26:31 +0100	[thread overview]
Message-ID: <YjHzl3Arey7KH0CB@kroah.com> (raw)
In-Reply-To: <6eb2052f463d323b0a82e795d765afb9d5925f6e.camel@mediatek.com>

On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
> Hi Reviewers,
> 
> This patch fixes a use-after-free error when /proc/lockdep is read by
> user after a lockdep splat.
> 
> I checked and I think this patch can be applied to stable-5.4 and
> later. 
> 
> commit: 61cc4534b6550997c97a03759ab46b29d44c0017
> Subject: locking/lockdep: Avoid potential access of invalid memory in
> lock_class

I do not see that commit id in Linus's tree, are you sure it is correct?

thanks,

greg k-h

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2022-03-16 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  6:01 apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable Cheng Jui Wang
2022-03-16  6:01 ` Cheng Jui Wang
2022-03-16 14:26 ` Greg KH [this message]
2022-03-16 14:26   ` Greg KH
2022-03-16 14:30   ` Tetsuo Handa
2022-03-16 14:30     ` Tetsuo Handa
2022-03-16 14:38   ` Waiman Long
2022-03-16 14:38     ` Waiman Long
2022-03-16 15:31     ` Greg KH
2022-03-16 15:31       ` 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=YjHzl3Arey7KH0CB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bvanassche@acm.org \
    --cc=cheng-jui.wang@mediatek.com \
    --cc=eason-yh.lin@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=longman@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.