mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CJ <firefly0158@163.com>
To: aivazian.tigran@gmail.com
Cc: linux-kernel@vger.kernel.org,
	syzbot+5b2e10c67416270b15c0@syzkaller.appspotmail.com
Subject: [BUG] bfs: WARNING in mark_buffer_dirty from bfs_get_block
Date: Thu, 3 Sep 2026 15:06:34 +0800 (CST)	[thread overview]
Message-ID: <7bd0e4e9.56b2.1a066173def.Coremail.firefly0158@163.com> (raw)




Hi,


I am reporting that WARNING in mark_buffer_dirty remains reproducible with a
migrated syzkaller reproducer on Linux 7.2-rc3. The tested HEAD commit is
a13c140cc289c0b7b3770bce5b3ad42ab35074aa.


The reproducer writes to a file on a crafted BFS filesystem and enters
bfs_get_block() through the buffered write path.


bfs_get_block() reaches mark_buffer_dirty(), which warns about the state of
the metadata buffer while servicing the write.


This looks like BFS marks a metadata buffer dirty before its state has been
validated or initialized correctly for the malformed filesystem image.


This issue was previously reported at:


https://syzkaller.appspot.com/bug?extid=5b2e10c67416270b15c0


Reproducer:


syz reproducer: https://pastebin.com/raw/VUbaJzLB


console output: https://pastebin.com/raw/sFnagzbT
kernel config: https://pastebin.com/raw/B0f3dC7H


Kernel:


HEAD commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
git tree: torvalds/linux
kernel version: 7.2.0-rc3 #1 PREEMPT(full)
tested tag: v7.2-rc3


Let me know if you need more details or testing.


Best regards


                 reply	other threads:[~2026-09-03  7:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7bd0e4e9.56b2.1a066173def.Coremail.firefly0158@163.com \
    --to=firefly0158@163.com \
    --cc=aivazian.tigran@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+5b2e10c67416270b15c0@syzkaller.appspotmail.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

all inboxes | Powered by JetHome®