From: Greg KH <gregkh@linuxfoundation.org>
To: Jordan Rife <jrife@google.com>
Cc: stable@vger.kernel.org, dborkman@kernel.org
Subject: Re: [PATCH] net: Avoid address overwrite in kernel_connect
Date: Thu, 7 Sep 2023 12:27:15 +0100 [thread overview]
Message-ID: <2023090743-cheek-zebra-a175@gregkh> (raw)
In-Reply-To: <20230905235846.142217-1-jrife@google.com>
On Tue, Sep 05, 2023 at 06:58:46PM -0500, Jordan Rife wrote:
> commit 0bdf399 upstream.
Nit, next time use more sha1 characters, the kernel documentation shows
how many we usually rely on.
> This fix applies to all stable kernel versions 4.19+.
Why not also 4.14?
Anyway, now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-09-07 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 23:58 [PATCH] net: Avoid address overwrite in kernel_connect Jordan Rife
2023-09-07 11:27 ` Greg KH [this message]
2023-09-07 16:15 ` Jordan Rife
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=2023090743-cheek-zebra-a175@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dborkman@kernel.org \
--cc=jrife@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox