From: Mohammed Gamal <mgamal@redhat•com>
To: Haiyang Zhang <haiyangz@microsoft•com>,
Stephen Hemminger <sthemmin@microsoft•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Cc: "otubo@redhat•com" <otubo@redhat•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"devel@linuxdriverproject•org" <devel@linuxdriverproject•org>,
vkuznets <vkuznets@redhat•com>
Subject: Re: [PATCH] hv_netvsc: Make sure out channel is fully opened on send
Date: Thu, 27 Sep 2018 10:57:05 +0200 [thread overview]
Message-ID: <1538038625.19334.2.camel@redhat.com> (raw)
In-Reply-To: <BN6PR21MB01612C60B5421AF2BB09742CCA150@BN6PR21MB0161.namprd21.prod.outlook.com>
On Wed, 2018-09-26 at 17:13 +0000, Haiyang Zhang wrote:
> > -----Original Message-----
> > From: Mohammed Gamal <mgamal@redhat•com>
> > Sent: Wednesday, September 26, 2018 12:34 PM
> > To: Stephen Hemminger <sthemmin@microsoft•com>; netdev@vger•kernel.
> > org
> > Cc: KY Srinivasan <kys@microsoft•com>; Haiyang Zhang
> > <haiyangz@microsoft•com>; vkuznets <vkuznets@redhat•com>;
> > otubo@redhat•com; cavery <cavery@redhat•com>; linux-
> > kernel@vger•kernel.org; devel@linuxdriverproject•org; Mohammed
> > Gamal
> > <mgamal@redhat•com>
> > Subject: [PATCH] hv_netvsc: Make sure out channel is fully opened
> > on send
> >
> > Dring high network traffic changes to network interface parameters
> > such as
> > number of channels or MTU can cause a kernel panic with a NULL
> > pointer
> > dereference. This is due to netvsc_device_remove() being called and
> > deallocating the channel ring buffers, which can then be accessed
> > by
> > netvsc_send_pkt() before they're allocated on calling
> > netvsc_device_add()
> >
> > The patch fixes this problem by checking the channel state and
> > returning
> > ENODEV if not yet opened. We also move the call to
> > hv_ringbuf_avail_percent()
> > which may access the uninitialized ring buffer.
> >
> > Signed-off-by: Mohammed Gamal <mgamal@redhat•com>
> > ---
> > drivers/net/hyperv/netvsc.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/hyperv/netvsc.c
> > b/drivers/net/hyperv/netvsc.c index
> > fe01e14..75f1b31 100644
> > --- a/drivers/net/hyperv/netvsc.c
> > +++ b/drivers/net/hyperv/netvsc.c
> > @@ -825,7 +825,12 @@ static inline int netvsc_send_pkt(
> > struct netdev_queue *txq = netdev_get_tx_queue(ndev,
> > packet->q_idx);
> > u64 req_id;
> > int ret;
> > - u32 ring_avail =
> > hv_get_avail_to_write_percent(&out_channel-
> > > outbound);
> >
> > + u32 ring_avail;
> > +
> > + if (out_channel->state != CHANNEL_OPENED_STATE)
> > + return -ENODEV;
> > +
> > + ring_avail = hv_get_avail_to_write_percent(&out_channel-
> > >outbound);
>
> When you reproducing the NULL ptr panic, does your kernel include the
> following patch?
> hv_netvsc: common detach logic
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/c
> ommit/?id=7b2ee50c0cd513a176a26a71f2989facdd75bfea
>
Yes it is included. And the commit did reduce the occurrence of this
race condition, but it still nevertheless occurs albeit rarely.
> We call netif_tx_disable(ndev) and netif_device_detach(ndev) before
> doing the changes
> on MTU or #channels. So there should be no call to start_xmit() when
> channel is not ready.
>
> If you see the check for CHANNEL_OPENED_STATE is still necessary on
> upstream kernel (including
> the patch " common detach logic "), we should debug further on the
> code and find out the
> root cause.
>
> Thanks,
> - Haiyang
>
_______________________________________________
devel mailing list
devel@linuxdriverproject•org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-09-27 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 16:34 [PATCH] hv_netvsc: Make sure out channel is fully opened on send Mohammed Gamal
2018-09-26 17:13 ` Haiyang Zhang
2018-09-27 8:57 ` Mohammed Gamal [this message]
2018-09-27 10:23 ` Stephen Hemminger
2018-09-27 10:31 ` Mohammed Gamal
-- strict thread matches above, loose matches on Subject: below --
2018-03-13 19:06 Mohammed Gamal
2018-03-13 19:35 ` Stephen Hemminger
2018-03-14 9:22 ` Mohammed Gamal
2018-03-15 16:24 ` Mohammed Gamal
2018-03-15 17:40 ` Stephen Hemminger
2018-03-14 8:27 ` Dan Carpenter
2018-03-16 14:16 ` David Miller
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=1538038625.19334.2.camel@redhat.com \
--to=mgamal@redhat$(echo .)com \
--cc=devel@linuxdriverproject$(echo .)org \
--cc=haiyangz@microsoft$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=otubo@redhat$(echo .)com \
--cc=sthemmin@microsoft$(echo .)com \
--cc=vkuznets@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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