From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>, Andres Freund <andres@anarazel.de>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: upstream kernel crashes
Date: Wed, 17 Aug 2022 10:12:18 -0700 [thread overview]
Message-ID: <CAHk-=wgsnBpMfUDgD=mxzEWhA6=ff3D3qssva0DFkE_55DXkLA@mail.gmail.com> (raw)
In-Reply-To: <20220814212610.GA3690074@roeck-us.net>
On Sun, Aug 14, 2022 at 2:26 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> syscaller reports lots of crashes with the mainline kernel. The latest
> I have seen, based on the current ToT, is attached. Backtraces are not
> always the same, but this one is typical.
Ok, I just pushed out the pull of the virtio fixes, so hopefully this
is all behind us.
Looking forward to (not really ;^) seeing what the google cloud
automation reports with this fixed.
Thanks,
Linus
next prev parent reply other threads:[~2022-08-17 17:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 21:26 upstream kernel crashes Guenter Roeck
2022-08-14 21:40 ` Linus Torvalds
2022-08-14 22:37 ` Andres Freund
2022-08-14 22:47 ` Linus Torvalds
2022-08-15 1:04 ` Jens Axboe
2022-08-15 1:36 ` Andres Freund
2022-08-15 3:18 ` Linus Torvalds
2022-08-15 7:11 ` Andres Freund
2022-08-15 7:29 ` Michael S. Tsirkin
2022-08-15 7:46 ` Andres Freund
2022-08-15 7:53 ` Michael S. Tsirkin
2022-08-15 8:02 ` Michael S. Tsirkin
2022-08-15 7:51 ` Michael S. Tsirkin
2022-08-15 8:15 ` Andres Freund
2022-08-15 8:28 ` Michael S. Tsirkin
2022-08-15 8:34 ` Andres Freund
2022-08-15 15:40 ` Michael S. Tsirkin
2022-08-15 16:45 ` Andres Freund
2022-08-15 16:50 ` Michael S. Tsirkin
2022-08-15 17:46 ` Andres Freund
2022-08-15 20:21 ` Michael S. Tsirkin
2022-08-15 20:53 ` Andres Freund
2022-08-15 21:04 ` Andres Freund
2022-08-15 21:10 ` Andres Freund
2022-08-15 21:32 ` Michael S. Tsirkin
2022-08-16 2:45 ` Xuan Zhuo
2022-08-17 6:13 ` Dmitry Vyukov
2022-08-17 6:36 ` Xuan Zhuo
2022-08-17 10:53 ` Michael S. Tsirkin
2022-08-17 15:58 ` Linus Torvalds
2022-08-18 1:55 ` Xuan Zhuo
2022-08-15 20:45 ` Guenter Roeck
2022-08-15 6:36 ` Michael S. Tsirkin
2022-08-15 7:17 ` Andres Freund
2022-08-15 7:43 ` Michael S. Tsirkin
2022-08-15 1:17 ` Guenter Roeck
2022-08-15 1:29 ` Jens Axboe
2022-08-15 9:43 ` Michael S. Tsirkin
2022-08-15 15:49 ` Guenter Roeck
2022-08-15 16:01 ` Michael S. Tsirkin
2022-08-15 18:22 ` Guenter Roeck
2022-08-15 18:37 ` Linus Torvalds
2022-08-15 20:38 ` Guenter Roeck
2022-08-17 17:12 ` Linus Torvalds [this message]
2022-08-18 1:08 ` Andres Freund
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='CAHk-=wgsnBpMfUDgD=mxzEWhA6=ff3D3qssva0DFkE_55DXkLA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).