From: "Corentin Noël" <corentin.noel@collabora.com>
To: Greg KH <gregkh@linuxfoundation.org>
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>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: virtio-net: kernel panic in virtio_net.c
Date: Tue, 01 Jun 2021 19:09:16 +0200 [thread overview]
Message-ID: <5744b89e9a500a8c2aa97cbad850bc4797fa7115.camel@collabora.com> (raw)
In-Reply-To: <YLZpVGDz4TVEdaK0@kroah.com>
Le mardi 01 juin 2021 à 19:07 +0200, Greg KH a écrit :
> On Tue, Jun 01, 2021 at 06:06:50PM +0200, Corentin Noël wrote:
> > I've been experiencing crashes with 5.13 that do not occur with
> > 5.12,
> > here is the crash trace:
> >
> > [ 47.713713] skbuff: skb_over_panic: text:ffffffffb73a8354
> > len:3762
> > put:3762 head:ffff9e1e1e48e000 data:ffff9e1e1e48e010 tail:0xec2
> > end:0xec0 dev:<NULL>
> > [ 47.716267] kernel BUG at net/core/skbuff.c:110!
> > [ 47.717197] invalid opcode: 0000 [#1] SMP PTI
> > [ 47.718049] CPU: 2 PID: 730 Comm: llvmpipe-0 Not tainted 5.13.0-
> > rc3linux-v5.13-rc3-for-mesa-ci-87614d7f3282.tar.bz2 #1
> > [ 47.719739] Hardware name: ChromiumOS crosvm, BIOS 0
> > [ 47.720656] RIP: 0010:skb_panic+0x43/0x45
> > [ 47.721426] Code: 4f 70 50 8b 87 bc 00 00 00 50 8b 87 b8 00 00
> > 00 50
> > ff b7 c8 00 00 00 4c 8b 8f c0 00 00 00 48 c7 c7 78 ae ef b7 e8 7f
> > 4c fb
> > ff <0f> 0b 48 8b 14 24 48 c7 c1 a0 22 d1 b7 e8 ab ff ff ff 48 c7 c6
> > e0
> > [ 47.725944] RSP: 0000:ffffacec01347c20 EFLAGS: 00010246
> > [ 47.726735] RAX: 000000000000008b RBX: 0000000000000010 RCX:
> > 00000000ffffdfff
> > [ 47.727820] RDX: 0000000000000000 RSI: 00000000ffffffea RDI:
> > 0000000000000000
> > [ 47.729096] RBP: ffffeb2700792380 R08: ffffffffb8144b08 R09:
> > 0000000000009ffb
> > [ 47.730260] R10: 00000000ffffe000 R11: 3fffffffffffffff R12:
> > ffff9e1e1e95b300
> > [ 47.731411] R13: 0000000000000000 R14: ffff9e1e1e48e000 R15:
> > 0000000000000eb2
> > [ 47.732541] FS: 00007f3a82b53700(0000)
> > GS:ffff9e1f2bd00000(0000)
> > knlGS:0000000000000000
> > [ 47.733858] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 47.734813] CR2: 00000000010d24f8 CR3: 0000000012d6e004 CR4:
> > 0000000000370ee0
> > [ 47.735968] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> > 0000000000000000
> > [ 47.737091] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> > 0000000000000400
> > [ 47.738318] Call Trace:
> > [ 47.738812] skb_put.cold+0x10/0x10
> > [ 47.739450] page_to_skb+0xe4/0x400
> > [ 47.740072] receive_buf+0x86/0x1660
> > [ 47.740693] ? inet_gro_receive+0x54/0x2c0
> > [ 47.741279] ? dev_gro_receive+0x194/0x6a0
> > [ 47.741846] virtnet_poll+0x2b8/0x3c0
> > [ 47.742357] __napi_poll+0x25/0x150
> > [ 47.742844] net_rx_action+0x22f/0x280
> > [ 47.743388] __do_softirq+0xba/0x264
> > [ 47.743947] irq_exit_rcu+0x90/0xb0
> > [ 47.744435] common_interrupt+0x40/0xa0
> > [ 47.744978] ? asm_common_interrupt+0x8/0x40
> > [ 47.745582] asm_common_interrupt+0x1e/0x40
> > [ 47.746182] RIP: 0033:0x7f3a7a276ed4
> > [ 47.746708] Code: a0 03 00 00 c5 fc 29 84 24 40 0f 00 00 c5 bc
> > 54 c8
> > c5 7c 28 84 24 80 01 00 00 c5 bc 59 e9 c5 fe 5b ed c5 fd 76 c0 c5
> > d5 fa
> > c0 <c5> fd db ec c5 fd 7f 84 24 20 0f 00 00 c5 fc 5b ed c4 e2 55 b8
> > cb
> > [ 47.749292] RSP: 002b:00007f3a82b4dba0 EFLAGS: 00000212
> > [ 47.750006] RAX: 00007f3a8c210324 RBX: ffffffffffffffff RCX:
> > ffffffffffffffff
> > [ 47.750964] RDX: 00007f3a8c210348 RSI: 00007f3a8c21034c RDI:
> > 00007f3a7c0575a0
> > [ 47.752049] RBP: 00007f3a82b52ca0 R08: 00007f3a8c210350 R09:
> > 00007f3a8c210354
> > [ 47.753161] R10: 00007f3a8c210358 R11: 000000000000ffef R12:
> > 00007f3a8c210340
> > [ 47.754260] R13: 00007f3a8c210344 R14: 00007f3a7c057580 R15:
> > 00007f3a8c21033c
> > [ 47.755354] Modules linked in:
> > [ 47.755871] ---[ end trace a8b692ea99c9cd9e ]---
> > [ 47.756606] RIP: 0010:skb_panic+0x43/0x45
> > [ 47.757297] Code: 4f 70 50 8b 87 bc 00 00 00 50 8b 87 b8 00 00
> > 00 50
> > ff b7 c8 00 00 00 4c 8b 8f c0 00 00 00 48 c7 c7 78 ae ef b7 e8 7f
> > 4c fb
> > ff <0f> 0b 48 8b 14 24 48 c7 c1 a0 22 d1 b7 e8 ab ff ff ff 48 c7 c6
> > e0
> > [ 47.760168] RSP: 0000:ffffacec01347c20 EFLAGS: 00010246
> > [ 47.760896] RAX: 000000000000008b RBX: 0000000000000010 RCX:
> > 00000000ffffdfff
> > [ 47.761903] RDX: 0000000000000000 RSI: 00000000ffffffea RDI:
> > 0000000000000000
> > [ 47.762945] RBP: ffffeb2700792380 R08: ffffffffb8144b08 R09:
> > 0000000000009ffb
> > [ 47.764059] R10: 00000000ffffe000 R11: 3fffffffffffffff R12:
> > ffff9e1e1e95b300
> > [ 47.765169] R13: 0000000000000000 R14: ffff9e1e1e48e000 R15:
> > 0000000000000eb2
> > [ 47.766261] FS: 00007f3a82b53700(0000)
> > GS:ffff9e1f2bd00000(0000)
> > knlGS:0000000000000000
> > [ 47.767512] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 47.768389] CR2: 00000000010d24f8 CR3: 0000000012d6e004 CR4:
> > 0000000000370ee0
> > [ 47.769381] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> > 0000000000000000
> > [ 47.770362] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> > 0000000000000400
> > [ 47.771339] Kernel panic - not syncing: Fatal exception in
> > interrupt
> > [ 47.772814] Kernel Offset: 0x35c00000 from 0xffffffff81000000
> > (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> >
> > I've been able to bisect the issue a little bit and the issue
> > disappeared after reverting the 4 following commits:
> > * fb32856b16ad9d5bcd75b76a274e2c515ac7b9d7
> > * af39c8f72301b268ad8b04bae646b6025918b82b
> > * f5d7872a8b8a3176e65dc6f7f0705ce7e9a699e6
> > * f80bd740cb7c954791279590b2e810ba6c214e52
> >
> > Here is my kernel config:
> > https://gitlab.freedesktop.org/tintou/mesa/-/blob/e5d6c56bfae8522e924217883d2c6a6bfc1b332b/.gitlab-ci/container/x86_64.config
>
> Do you have the same problem with 5.13-rc4?
>
> thanks,
>
> greg k-h
Yes I tried with rc2, rc3 and rc4 resulting to the same panic.
Thanks,
Corentin
next prev parent reply other threads:[~2021-06-01 17:09 UTC|newest]
Thread overview: 33+ 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:09 ` Corentin Noël [this message]
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
2021-10-07 12:04 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
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
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=5744b89e9a500a8c2aa97cbad850bc4797fa7115.camel@collabora.com \
--to=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 \
--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 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).