All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Panait, Dragos Marian" <dragos.panait@windriver.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Ruihan Li <lrh2000@pku.edu.cn>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6.1 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
Date: Thu, 1 Jun 2023 10:14:00 +0100	[thread overview]
Message-ID: <2023060116-brush-entail-0d8c@gregkh> (raw)
In-Reply-To: <PH0PR11MB495229C3DABA728EE5C8A19EFA489@PH0PR11MB4952.namprd11.prod.outlook.com>

On Wed, May 31, 2023 at 10:06:11AM +0000, Panait, Dragos Marian wrote:
> Done! (without the cover letter for newer kernels :))

All now queued up, thanks.

You could have just send a one sentance email saying "Please apply
commit XYZ to all stable kernels please" which would have been much
simpler and easier for you :)

thanks,

greg k-h

  parent reply	other threads:[~2023-06-01  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 12:26 [PATCH 6.1 0/1] Hardening against CVE-2023-2002 Dragos-Marian Panait
2023-05-30 12:26 ` [PATCH 6.1 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Dragos-Marian Panait
2023-05-30 12:52   ` Greg KH
     [not found]     ` <PH0PR11MB495229C3DABA728EE5C8A19EFA489@PH0PR11MB4952.namprd11.prod.outlook.com>
2023-06-01  9:14       ` Greg KH [this message]
2023-05-30 12:55   ` Hardening against CVE-2023-2002 bluez.test.bot
  -- strict thread matches above, loose matches on Subject: below --
2023-05-30 12:39 [PATCH 5.15 0/1] " Dragos-Marian Panait
2023-05-30 12:39 ` [PATCH 5.15 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Dragos-Marian Panait
2023-05-30 12:55   ` Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002 bluez.test.bot
2023-05-30 12:42 [PATCH 5.10 0/1] " Dragos-Marian Panait
2023-05-30 12:42 ` [PATCH 5.10 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Dragos-Marian Panait
2023-05-30 12:55   ` Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002 bluez.test.bot
2023-05-30 12:47 [PATCH 5.4 0/1] " Dragos-Marian Panait
2023-05-30 12:47 ` [PATCH 5.4 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Dragos-Marian Panait
2023-05-30 12:55   ` Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002, RE: Hardening against CVE-2023-2002 bluez.test.bot

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=2023060116-brush-entail-0d8c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=dragos.panait@windriver.com \
    --cc=edumazet@google.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrh2000@pku.edu.cn \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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.