regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: virtio-net: kernel panic in virtio_net.c
Date: Tue, 12 Oct 2021 14:44:50 +0200	[thread overview]
Message-ID: <e2d474a4-c307-9f8e-d896-48d8d3acc9cb@leemhuis.info> (raw)
In-Reply-To: <ae2879df-64b8-0258-e4ee-59d7c279676f@leemhuis.info>



On 08.10.21 09:59, Thorsten Leemhuis wrote:
> On 07.10.21 14:04, Corentin Noël wrote:
>> I've been experiencing crashes with 5.14-rc1 and above that do not
>> occur with 5.13,
> 
> Feel free to ignore this message. I write it to make regzbot track above
> issue. Regzbot is the regression tracking bot I'm working on. It's still
> in the early stages and this is still one of the first few regression I
> make it track to get started and things tested in the field. That also
> why I'm sending the mail just to the regressions list (it will do its
> full magic nevertheless). For details see:
> https://linux-regtracking.leemhuis.info/post/inital-regzbot-running/
> https://linux-regtracking.leemhuis.info/post/regzbot-approach/
> 
> #regzbot ^introduced v5.13..v5.14-rc1
> #regzbot link
> https://lore.kernel.org/regressions/1633623446.6192446-1-xuanzhuo@linux.alibaba.com/
> Looks like a fix for this somehow fall through the cracks
> #regzbot ignore-activitiy
> 
> BTW, in case anyone is reading this: the regzbot's webinterface that
> gives insights into what is tracked can be found here:
> 
> https://linux-regtracking.leemhuis.info/regzbot/mainline.html
> 
> Ciao, Thorsten

#regzbot fixed-by: 732b74d647048668f0f8dc0c848f0746c69e2e2f


  reply	other threads:[~2021-10-12 12:44 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
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 [this message]
  -- 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=e2d474a4-c307-9f8e-d896-48d8d3acc9cb@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).