From: Greg KH <gregkh@linuxfoundation.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: harperchen1110@gmail.com, mkl@pengutronix.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] can: af_can: fix NULL pointer dereference in can_rcv_filter" failed to apply to 4.19-stable tree
Date: Mon, 12 Dec 2022 12:55:32 +0100 [thread overview]
Message-ID: <Y5cWtLwRyrnOPG0I@kroah.com> (raw)
In-Reply-To: <e3b578a6-450b-11d6-caf9-33af7ad3cc3a@hartkopp.net>
On Mon, Dec 12, 2022 at 11:15:58AM +0100, Oliver Hartkopp wrote:
> Just FYI
>
> The longterm kernels before Linux 5.4 (4.9/4.14/4.19) are not affected by
> this issue as the netdev->ml_priv pointer is assigned within a netdev
> notifier for ARPHRD_CAN interfaces and this always assigns the data
> structure properly.
>
> I tested the crash reproducer from the syzbot bug report which did not have
> any bad effect (as expected).
Wonderful, thanks for letting us know.
greg k-h
prev parent reply other threads:[~2022-12-12 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 9:53 FAILED: patch "[PATCH] can: af_can: fix NULL pointer dereference in can_rcv_filter" failed to apply to 4.19-stable tree gregkh
2022-12-12 10:15 ` Oliver Hartkopp
2022-12-12 11:55 ` Greg KH [this message]
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=Y5cWtLwRyrnOPG0I@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=harperchen1110@gmail.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--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