[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wikzU4402P-FpJRK_QwfVOS+t-3p1Wx5awGHTvr-s_0Ew@mail.gmail.com>
Date: Sun, 14 Aug 2022 20:18:44 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andres Freund <andres@...razel.de>
Cc: Jens Axboe <axboe@...nel.dk>,
James Bottomley <James.Bottomley@...senpartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Guenter Roeck <linux@...ck-us.net>,
linux-kernel@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
"Michael S. Tsirkin" <mst@...hat.com>
Subject: Re: upstream kernel crashes
On Sun, Aug 14, 2022 at 6:36 PM Andres Freund <andres@...razel.de> wrote:
>
> Some of the symptoms could be related to the issue in this thread, hence
> listing them here
Smells like slab corruption to me, and the problems may end up being
then largely random just depending on who ends up using the allocation
that gets trampled on.
I wouldn't be surprised if it's all the same thing - including your
network issue.
Both you and Guenter seem to be seeing this on that google cloud VM
setup, which may or may not be related. I haven't seen any reports
from anybody else, but that might still be just coincidence.
But it makes me go back to your original report, where you suspected
the virtio pull.
Looking at that original report, and doing
gitk 7ebfc85e2cd7..69dac8e431af
nothing else looks all that relevant, although obviously any random
error path could end up doing a double free and messing up the slab
cache that way. But a lot of the non-virtio stuff there is things like
RISC-V and devicetree that definitely shouldn't have any effect.
Adding Michael Tsirkin to this thread too, just so he knows.
Linus
Powered by blists - more mailing lists