public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jeremy Bongio <jbongio@google.com>
Cc: stable@vger.kernel.org, Li Nan <linan122@huawei.com>,
	Song Liu <song@kernel.org>
Subject: Re: [PATCH] md: fix kmemleak of rdev->serial
Date: Thu, 16 May 2024 08:54:31 +0200	[thread overview]
Message-ID: <2024051632-qualifier-delta-f626@gregkh> (raw)
In-Reply-To: <CAOvQCn5LEhFw8njxO7oa9Q_Ku3b7UEEmJUAqPw9aTO3Gu90kRg@mail.gmail.com>


A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, May 15, 2024 at 09:31:07AM -0700, Jeremy Bongio wrote:
> 5.4 doesn't have "mddev_destroy_serial_pool" ... More work would be
> needed to figure out if the vulnerability exists and how to fix it.

Can you do that please?  I know Google still cares about 5.4 kernel
trees :)

> The patch also applies to 5.15, but I haven't tested it.

I took it there as we can't take a patch for an older kernel and not a
newer one, as that would cause a regression when people upgrade.

thanks,

greg k-h

  reply	other threads:[~2024-05-16  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 23:30 [PATCH] md: fix kmemleak of rdev->serial Jeremy Bongio
2024-05-15  7:33 ` Greg KH
2024-05-15 16:31   ` Jeremy Bongio
2024-05-16  6:54     ` Greg KH [this message]
2024-05-20 22:18       ` Jeremy Bongio
  -- strict thread matches above, loose matches on Subject: below --
2024-05-13 21:39 Jeremy Bongio
2024-05-13 22:24 ` Greg KH
2024-05-13 23:31   ` Jeremy Bongio
2024-05-13 19:20 Jeremy Bongio
2024-05-13 20:53 ` Greg KH
2024-05-13 19:20 Jeremy Bongio
2024-05-13 20:53 ` Greg KH
2024-05-13 21:40   ` Jeremy Bongio
2024-05-13 20:53 ` 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=2024051632-qualifier-delta-f626@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jbongio@google.com \
    --cc=linan122@huawei.com \
    --cc=song@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox