From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Josh Elsasser <jelsasser@appneta.com>
Cc: Sasha Levin <sashal@kernel.org>, Matteo Croce <mcroce@redhat.com>,
stable@vger.kernel.org, netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: net: check before dereferencing netdev_ops during busy poll
Date: Sat, 29 Jun 2019 09:45:53 +0200 [thread overview]
Message-ID: <20190629074553.GA28708@kroah.com> (raw)
In-Reply-To: <1560226F-F2C0-440D-9C58-D664DE3C7322@appneta.com>
On Fri, Jun 28, 2019 at 07:03:01PM -0700, Josh Elsasser wrote:
> On Jun 28, 2019, at 3:55 PM, Sasha Levin <sashal@kernel.org> wrote:
>
> > What's the upstream commit id?
>
> The commit wasn't needed upstream, as I only sent the original patch after
> 79e7fff47b7b ("net: remove support for per driver ndo_busy_poll()") had
> made the fix unnecessary in Linus' tree.
>
> May've gotten lost in the shuffle due to my poor Fixes tags. The patch in
> question applied only on top of the 4.9 stable release at the time, but the
> actual NPE had been around in some form since 3.11 / 0602129286705 ("net: add
> low latency socket poll").
Ok, can people then resend this and be very explicit as to why this is
needed only in a stable kernel tree and get reviews from people agreeing
that this really is the correct fix?
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-29 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 16:34 net: check before dereferencing netdev_ops during busy poll Matteo Croce
2019-06-28 22:55 ` Sasha Levin
2019-06-29 2:03 ` Josh Elsasser
2019-06-29 7:45 ` Greg Kroah-Hartman [this message]
2019-06-29 19:39 ` Matteo Croce
2019-07-01 17:52 ` Greg Kroah-Hartman
2019-07-01 18:03 ` Matteo Croce
2019-07-01 23:52 ` Josh Elsasser
2019-07-01 17:52 ` Greg Kroah-Hartman
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=20190629074553.GA28708@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=jelsasser@appneta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sashal@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;
as well as URLs for NNTP newsgroup(s).