All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: stable@vger.kernel.org, "Michael S.Tsirkin" <mst@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	virtualization@lists.linux-foundation.org,
	regressions@lists.linux.dev, "Eric Dumazet" <edumazet@google.com>,
	"Corentin Noël" <corentin.noel@collabora.com>
Subject: Re: virtio-net: kernel panic in virtio_net.c
Date: Wed, 9 Jun 2021 08:24:20 +0200	[thread overview]
Message-ID: <YMBelFMOAhEqWoc+@kroah.com> (raw)
In-Reply-To: <1623218897.4150124-1-xuanzhuo@linux.alibaba.com>

On Wed, Jun 09, 2021 at 02:08:17PM +0800, Xuan Zhuo wrote:
> On Wed, 9 Jun 2021 06:50:10 +0200, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Jun 09, 2021 at 09:48:33AM +0800, Xuan Zhuo wrote:
> > > > > With this patch and the latest net branch I no longer get crashes.
> > > >
> > > > Did this ever get properly submitted to the networking tree to get into
> > > > 5.13-final?
> > >
> > > The patch has been submitted.
> > >
> > > 	[PATCH net] virtio-net: fix for skb_over_panic inside big mode
> >
> > Submitted where?  Do you have a lore.kernel.org link somewhere?
> 
> 
> https://lore.kernel.org/netdev/20210603170901.66504-1-xuanzhuo@linux.alibaba.com/

So this is commit 1a8024239dac ("virtio-net: fix for skb_over_panic
inside big mode") in Linus's tree, right?

But why is that referencing:
	Fixes: fb32856b16ad ("virtio-net: page_to_skb() use build_skb when there's sufficient tailroom")

when this problem was seen in stable kernels that had a different commit
backported to it?

Is there nothing needed to be done for the stable kernel trees?

confused,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: regressions@lists.linux.dev, "Michael S.Tsirkin" <mst@redhat.com>,
	"Corentin Noël" <corentin.noel@collabora.com>,
	stable@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	"Eric Dumazet" <edumazet@google.com>
Subject: Re: virtio-net: kernel panic in virtio_net.c
Date: Wed, 9 Jun 2021 08:24:20 +0200	[thread overview]
Message-ID: <YMBelFMOAhEqWoc+@kroah.com> (raw)
In-Reply-To: <1623218897.4150124-1-xuanzhuo@linux.alibaba.com>

On Wed, Jun 09, 2021 at 02:08:17PM +0800, Xuan Zhuo wrote:
> On Wed, 9 Jun 2021 06:50:10 +0200, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Jun 09, 2021 at 09:48:33AM +0800, Xuan Zhuo wrote:
> > > > > With this patch and the latest net branch I no longer get crashes.
> > > >
> > > > Did this ever get properly submitted to the networking tree to get into
> > > > 5.13-final?
> > >
> > > The patch has been submitted.
> > >
> > > 	[PATCH net] virtio-net: fix for skb_over_panic inside big mode
> >
> > Submitted where?  Do you have a lore.kernel.org link somewhere?
> 
> 
> https://lore.kernel.org/netdev/20210603170901.66504-1-xuanzhuo@linux.alibaba.com/

So this is commit 1a8024239dac ("virtio-net: fix for skb_over_panic
inside big mode") in Linus's tree, right?

But why is that referencing:
	Fixes: fb32856b16ad ("virtio-net: page_to_skb() use build_skb when there's sufficient tailroom")

when this problem was seen in stable kernels that had a different commit
backported to it?

Is there nothing needed to be done for the stable kernel trees?

confused,

greg k-h
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2021-06-09  6:24 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 16:06 virtio-net: kernel panic in virtio_net.c Corentin Noël
2021-06-01 17:07 ` Greg KH
2021-06-01 17:07   ` Greg KH
2021-06-01 17:09   ` Corentin Noël
2021-06-01 17:47     ` Eric Dumazet
2021-06-02  2:01       ` Xuan Zhuo
2021-06-02  2:01         ` Xuan Zhuo
2021-06-02 17:56         ` Corentin Noël
2021-06-02 17:54       ` Corentin Noël
2021-06-03  2:44         ` Xuan Zhuo
2021-06-03  2:44           ` Xuan Zhuo
2021-06-03  8:57           ` Corentin Noël
2021-06-08 12:17             ` Greg KH
2021-06-08 12:17               ` Greg KH
2021-06-09  1:48               ` Xuan Zhuo
2021-06-09  1:48                 ` Xuan Zhuo
2021-06-09  4:50                 ` Greg KH
2021-06-09  4:50                   ` Greg KH
2021-06-09  6:08                   ` Xuan Zhuo
2021-06-09  6:08                     ` Xuan Zhuo
2021-06-09  6:24                     ` Greg KH [this message]
2021-06-09  6:24                       ` Greg KH
2021-06-09  7:51                       ` Xuan Zhuo
2021-06-09  7:51                         ` Xuan Zhuo
2021-06-09  8:03                         ` Greg KH
2021-06-09  8:03                           ` Greg KH
2021-06-09  8:08                           ` Xuan Zhuo
2021-06-09  8:08                             ` Xuan Zhuo
  -- strict thread matches above, loose matches on Subject: below --
2021-10-07 12:04 Corentin Noël
2021-10-07 13:10 ` Michael S. Tsirkin
2021-10-07 13:10   ` Michael S. Tsirkin
2021-10-07 13:51   ` Eric Dumazet
2021-10-07 14:02     ` Corentin Noël
2021-10-07 14:13       ` Greg KH
2021-10-07 14:13         ` Greg KH
2021-10-07 15:06 ` Xuan Zhuo
2021-10-07 15:06   ` Xuan Zhuo
2021-10-07 15:25   ` Greg KH
2021-10-07 15:25     ` Greg KH
2021-10-07 16:17     ` Xuan Zhuo
2021-10-07 16:17       ` Xuan Zhuo
2021-10-08  8:06       ` Greg KH
2021-10-08  8:06         ` Greg KH
2021-10-08 10:02         ` Michael S. Tsirkin
2021-10-08 10:02           ` Michael S. Tsirkin
2021-10-08 12:21           ` Corentin Noël
2021-10-08 16:27         ` Xuan Zhuo
2021-10-08 16:27           ` Xuan Zhuo
2021-10-09  5:19           ` Greg KH
2021-10-09  5:19             ` Greg KH
2021-10-09  9:31             ` Xuan Zhuo
2021-10-09  9:31               ` Xuan Zhuo
2021-10-08  7:59 ` Thorsten Leemhuis
2021-10-12 12:44   ` Thorsten Leemhuis

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=YMBelFMOAhEqWoc+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corentin.noel@collabora.com \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xuanzhuo@linux.alibaba.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.