From: syzbot <syzbot+2403e3909382fbdeaf6c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hdanton@sina.com,
kent.overstreet@linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
tangyouling@kylinos.cn
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in list_lru_add
Date: Wed, 21 Aug 2024 18:51:03 -0700 [thread overview]
Message-ID: <000000000000294a7f06203be41c@google.com> (raw)
In-Reply-To: <0000000000006d415806048a9aee@google.com>
syzbot suspects this issue was fixed by commit:
commit aacd897d4d75adaae3becc2b00d8cdc9a56928d1
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri Jul 12 00:01:31 2024 +0000
Revert "bcachefs: Mark bch_inode_info as SLAB_ACCOUNT"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=150bcf6b980000
start commit: 43db1e03c086 Merge tag 'for-6.10/dm-fixes-2' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=42a432cfd0e579e0
dashboard link: https://syzkaller.appspot.com/bug?extid=2403e3909382fbdeaf6c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10401f71980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f1ae49980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Revert "bcachefs: Mark bch_inode_info as SLAB_ACCOUNT"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-22 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 16:00 [syzbot] [mm?] BUG: unable to handle kernel paging request in list_lru_add syzbot
2023-12-27 15:50 ` syzbot
2024-07-12 17:11 ` syzbot
2024-07-13 1:48 ` Hillf Danton
2024-07-13 2:15 ` syzbot
2024-07-13 9:05 ` Hillf Danton
2024-07-13 9:35 ` syzbot
2024-07-13 1:14 ` syzbot
2024-08-22 1:51 ` syzbot [this message]
2024-08-22 1:54 ` Kent Overstreet
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=000000000000294a7f06203be41c@google.com \
--to=syzbot+2403e3909382fbdeaf6c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tangyouling@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.