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: <CAMZfGtUr6V5pTrPhZukD2_KbB7BLPoKvF6H63HP4pykY36Ou9A@mail.gmail.com>
 <0000000000009901d505dafc07b3@google.com>
In-Reply-To: <0000000000009901d505dafc07b3@google.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 24 Mar 2022 12:45:00 -0700
Message-ID: <CAHk-=whxaFX4nqnE-SLHTGKyqejvbrhYx5sagcxWd+UWCMf8dg@mail.gmail.com>
Subject: Re: [syzbot] general protection fault in list_lru_add
To:     syzbot <syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Dmitry Vyukov <dvyukov@google.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux-MM <linux-mm@kvack.org>,
        Muchun Song <songmuchun@bytedance.com>,
        syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Mar 24, 2022 at 12:41 PM syzbot
<syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com> wrote:
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Heh, well that's unfortunate.

I think the issue is that it triggered a new BUG() that didn't match
the previous NULL pointer dereference, so it thinks things are
"fixed".

             Linus