[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bc1358e8-438a-4385-8bde-8e6a785f6eeb@redhat.com>
Date: Fri, 11 Oct 2024 12:11:50 +0200
From: David Hildenbrand <david@...hat.com>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+619c487ed60780dab217@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-next@...r.kernel.org, sfr@...b.auug.org.au,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [mm?] linux-next test error: kernel BUG in
folio_add_new_anon_rmap
On 11.10.24 12:05, Aleksandr Nogikh wrote:
> Hi David,
>
> On Tue, Oct 8, 2024 at 3:11 PM David Hildenbrand <david@...hat.com> wrote:
>>
>> On 08.10.24 08:51, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
> < ... >
>>>
>>
>> #syz fix: mm-add-pageanonnotksm-fix
>
> Just curious: this is not the commit title that will be preserved when
> the commit reaches the torvalds tree, right?
No, the fixup patch is currently in mm-unstable and will be squashed
into the responsible commit once Andrew moves it to mm-stable. So
neither commit ID nor subject are final.
>
> Syzbot uses commit titles to track which fuzzed kernel trees have
> received each bug fix, so in this case the bot will become very
> confused. If the final title is known, it's better to use that in the
> syz fix command.
That's unfortunate, but that's the way linux-next works :/
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists