From: Greg KH <gregkh@linuxfoundation.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Ashwin Kamat <ashwin.kamat@broadcom.com>,
linux-kernel@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, ajay.kaher@broadcom.com,
vasavi.sirnapalli@broadcom.com, tapas.kundu@broadcom.com
Subject: Re: [PATCH v5.10 0/2] Fix for CVE-2024-36901
Date: Mon, 15 Jul 2024 13:47:50 +0200 [thread overview]
Message-ID: <2024071544-helper-bounce-9537@gregkh> (raw)
In-Reply-To: <eee4d558-51d5-4f84-8bc8-d01178f5a1e5@broadcom.com>
On Fri, Jul 12, 2024 at 02:19:37PM -0700, Florian Fainelli wrote:
> On 7/9/24 03:22, Ashwin Kamat wrote:
> > From: Ashwin Dayanand Kamat <ashwin.kamat@broadcom.com>
> >
> > net/ipv6: annotate data-races around cnf.disable_ipv6
> > disable_ipv6 is read locklessly, add appropriate READ_ONCE() and WRITE_ONCE() annotations.
> >
> > net/ipv6: prevent NULL dereference in ip6_output()
> > Fix for CVE-2024-36901
> >
> > Ashwin Dayanand Kamat (2):
> > net/ipv6: annotate data-races around cnf.disable_ipv6
> > net/ipv6: prevent NULL dereference in ip6_output()
>
> LGTM
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2024-07-15 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 10:22 [PATCH v5.10 0/2] Fix for CVE-2024-36901 Ashwin Kamat
2024-07-09 10:22 ` [PATCH v5.10 1/2] net/ipv6: annotate data-races around cnf.disable_ipv6 Ashwin Kamat
2024-07-09 10:22 ` [PATCH v5.10 2/2] net/ipv6: prevent NULL dereference in ip6_output() Ashwin Kamat
2024-07-12 21:19 ` [PATCH v5.10 0/2] Fix for CVE-2024-36901 Florian Fainelli
2024-07-15 11:47 ` Greg KH [this message]
2024-07-13 6:52 ` Greg KH
[not found] ` <CA+tTbbvb04ZuTY+5pH+Yf5-OKJnx5RqvyjxfDixWhinwvH_hFw@mail.gmail.com>
2024-07-13 11:05 ` 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=2024071544-helper-bounce-9537@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajay.kaher@broadcom.com \
--cc=ashwin.kamat@broadcom.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tapas.kundu@broadcom.com \
--cc=vasavi.sirnapalli@broadcom.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).