From: syzbot <syzbot+cf7b2215b5d70600ec00@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pz010001011111@proton.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text
Date: Sun, 29 Sep 2024 05:53:03 -0700 [thread overview]
Message-ID: <66f94daf.050a0220.6bad9.0012.GAE@google.com> (raw)
In-Reply-To: <xpml2-IAWMWixV5X5cC9OKV2DxavafGOxt8q-Eb4WHzCouS859S5es04-mWaB3XnS4EP1QA3p4h3bITh3KKaTJELJsUyN8uKYhaCcPoVdyk=@proton.me>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: Bad rss-counter state
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
BUG: Bad rss-counter state mm:ffff888011da8980 type:MM_SWAPENTS val:11
bcachefs (loop0): shutting down
bcachefs (loop0): going read-only
bcachefs (loop0): finished waiting for writes to stop
bcachefs (loop0): flushing journal and stopping allocators, journal seq 8
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
bcachefs (loop0): shutting down
bcachefs (loop0): going read-only
bcachefs (loop0): finished waiting for writes to stop
bcachefs (loop0): flushing journal and stopping allocators, journal seq 8
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
bcachefs (loop0): shutting down
bcachefs (loop0): going read-only
bcachefs (loop0): finished waiting for writes to stop
bcachefs (loop0): flushing journal and stopping allocators, journal seq 8
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
bcachefs (loop0): shutting down
bcachefs (loop0): going read-only
bcachefs (loop0): finished waiting for writes to stop
bcachefs (loop0): flushing journal and stopping allocators, journal seq 8
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
bcachefs (loop0): shutting down
bcachefs (loop0): going read-only
bcachefs (loop0): finished waiting for writes to stop
bcachefs (loop0): flushing journal and stopping allocators, journal seq 8
bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 8
bcachefs (loop0): unshutdown complete, journal seq 9
bcachefs (loop0): done going read-only, filesystem not clean
bcachefs (loop0): shutdown complete
Tested on:
commit: 3efc5736 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11360ea9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4fcb065287cdb84
dashboard link: https://syzkaller.appspot.com/bug?extid=cf7b2215b5d70600ec00
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17a03e80580000
next parent reply other threads:[~2024-09-29 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xpml2-IAWMWixV5X5cC9OKV2DxavafGOxt8q-Eb4WHzCouS859S5es04-mWaB3XnS4EP1QA3p4h3bITh3KKaTJELJsUyN8uKYhaCcPoVdyk=@proton.me>
2024-09-29 12:53 ` syzbot [this message]
[not found] <delA5FekzdAhhRtj07A23KOexGB1wt-QIIo3VwX-wUqS1_Hbhbg-TnqJ3ZXbi9DCGKL69lVLWKC3JoKYDYSWi6l63Irphq8zQqdBFcaOsv4=@proton.me>
2024-09-29 14:00 ` [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text syzbot
[not found] <6zTxrcjMccS8qnqdOfReGJXovRQL7OnpqATkXA7tlixHh8vAtpxiXhGmf_fvvKcXHMv9NcB7Y4CXl3XeR5ZS_3U5ghth7JmuiD43AdUa7DM=@proton.me>
2024-09-27 21:57 ` syzbot
2024-09-21 22:17 syzbot
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=66f94daf.050a0220.6bad9.0012.GAE@google.com \
--to=syzbot+cf7b2215b5d70600ec00@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pz010001011111@proton.me \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox