Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220814212610.GA3690074@roeck-us.net> <20220815054117-mutt-send-email-mst@kernel.org>
 <20220815154920.GA4027315@roeck-us.net> <20220815120007-mutt-send-email-mst@kernel.org>
 <20220815182254.GA3241114@roeck-us.net>
In-Reply-To: <20220815182254.GA3241114@roeck-us.net>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 15 Aug 2022 11:37:54 -0700
Message-ID: <CAHk-=wjWN6Wh1t5g48=ue4Ti6ig2P7u5nXBcQjLf=oiAZibk6w@mail.gmail.com>
Subject: Re: upstream kernel crashes
To:     Guenter Roeck <linux@roeck-us.net>
Cc:     "Michael S. Tsirkin" <mst@redhat.com>,
        linux-kernel@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Aug 15, 2022 at 11:22 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> I ended up publishing several of the syzkaller reports because I could
> not figure out how to test the proposed patch otherwise. Sorry for the
> noise on the mailing lists, but I just could not figure out how to
> trigger test runs without making the reports public. Various test runs
> are now queued. Hopefully we should get results soon.

I actually think that the best "test" is to just test the revert and
see if the problems go away.

You may not have found a way to reliably trigger one particular
problem, but apparently you can easily enough trigger some random
issue with enough tests.

If it's some random memory corruption, there may simply not ba a great
reproducer, with the oopses just depending on random layout and
timing.

              Linus