regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Corentin Noël" <corentin.noel@collabora.com>,
	"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>,
	stable@vger.kernel.org
Subject: Re: virtio-net: kernel panic in virtio_net.c
Date: Fri, 08 Oct 2021 00:17:26 +0800	[thread overview]
Message-ID: <1633623446.6192446-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <YV8RTqGSTuVLMFOP@kroah.com>

On Thu, 7 Oct 2021 17:25:02 +0200, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Oct 07, 2021 at 11:06:12PM +0800, Xuan Zhuo wrote:
> > On Thu, 07 Oct 2021 14:04:22 +0200, Corentin Noël <corentin.noel@collabora.com> wrote:
> > > I've been experiencing crashes with 5.14-rc1 and above that do not
> > > occur with 5.13,
> >
> > I should have fixed this problem before. I don't know why, I just looked at the
> > latest net code, and this commit seems to be lost.
> >
> >      1a8024239dacf53fcf39c0f07fbf2712af22864f virtio-net: fix for skb_over_panic inside big mode
> >
> > Can you test this patch again?
>
> That commit showed up in 5.13-rc5, so 5.14-rc1 and 5.13 should have had
> it in it, right?
>

Yes, it may be lost due to conflicts during a certain merge.

Thanks.

> thanks,
>
> greg k-h

  reply	other threads:[~2021-10-07 16:18 UTC|newest]

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

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=1633623446.6192446-1-xuanzhuo@linux.alibaba.com \
    --to=xuanzhuo@linux.alibaba.com \
    --cc=corentin.noel@collabora.com \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).