Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs@vger.kernel.org,
	syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com,
	syzbot+d98fd19acd08b36ff422@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] nilfs2: protect busy buffer heads from being force-cleared
Date: Wed,  8 Jan 2025 05:00:45 +0900	[thread overview]
Message-ID: <20250107200202.6432-1-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <670ea678.050a0220.d5849.000b.GAE@google.com>

Hi Andrew, please queue this series for the next cycle.

This series fixes the buffer head state inconsistency issues reported by
syzbot that occurs when the filesystem is corrupted and falls back to
read-only, and the associated buffer head use-after-free issue.

Thanks,
Ryusuke Konishi

Ryusuke Konishi (2):
  nilfs2: do not force clear folio if buffer is referenced
  nilfs2: protect access to buffers with no active references

 fs/nilfs2/page.c    | 31 +++++++++++++++++++++++++++----
 fs/nilfs2/segment.c |  4 +++-
 2 files changed, 30 insertions(+), 5 deletions(-)

-- 
2.43.0


  reply	other threads:[~2025-01-07 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 17:29 [syzbot] [nilfs?] WARNING in nilfs_btree_propagate (2) syzbot
2025-01-07 20:00 ` Ryusuke Konishi [this message]
2025-01-07 20:00   ` [PATCH 1/2] nilfs2: do not force clear folio if buffer is referenced Ryusuke Konishi
2025-01-07 20:00   ` [PATCH 2/2] nilfs2: protect access to buffers with no active references Ryusuke Konishi

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=20250107200202.6432-1-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com \
    --cc=syzbot+d98fd19acd08b36ff422@syzkaller.appspotmail.com \
    --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