mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	Taotao Chen <chentaotao@didiglobal.com>,
	Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
	NeilBrown <neil@brown.name>
Subject: Re: [PATCH 0/3] Fix two syzbot corruption bugs in minix filesystem
Date: Wed,  5 Nov 2025 13:45:54 +0100	[thread overview]
Message-ID: <20251105-postfach-ortung-24f951c72583@brauner> (raw)
In-Reply-To: <20251104143005.3283980-1-jkoolstra@xs4all.nl>

On Tue, 04 Nov 2025 15:30:02 +0100, Jori Koolstra wrote:
> Syzbot fuzzes /fs by trying to mount and manipulate deliberately
> corrupted filesystems. This should not lead to BUG_ONs and WARN_ONs for
> easy to detect corruptions. This series adds code to be able to report
> such corruptions and fixes two syzbot bugs on this kind.
> 
> Jori Koolstra (3):
>   Add error handling to minix filesystem for inode corruption detection
>   Fix a drop_nlink warning in minix_rmdir
>   Fix a drop_nlink warning in minix_rename
> 
> [...]

Applied to the vfs-6.19.minix branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.minix branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.19.minix

[1/3] Add error handling to minix filesystem for inode corruption detection
      https://git.kernel.org/vfs/vfs/c/21215ce7a95a
[2/3] Fix a drop_nlink warning in minix_rmdir
      https://git.kernel.org/vfs/vfs/c/d3e0e8661ceb
[3/3] Fix a drop_nlink warning in minix_rename
      https://git.kernel.org/vfs/vfs/c/009a2ba40303

      parent reply	other threads:[~2025-11-05 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 14:30 Jori Koolstra
2025-11-04 14:30 ` [PATCH 1/3] Add error handling to minix filesystem for inode corruption detection Jori Koolstra
2025-11-04 14:30 ` [PATCH 2/3] Fix a drop_nlink warning in minix_rmdir Jori Koolstra
2025-11-04 14:30 ` [PATCH 3/3] Fix a drop_nlink warning in minix_rename Jori Koolstra
2025-11-04 14:50 ` [PATCH 0/3] Fix two syzbot corruption bugs in minix filesystem Jan Kara
2025-11-05 12:45 ` Christian Brauner [this message]

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=20251105-postfach-ortung-24f951c72583@brauner \
    --to=brauner@kernel.org \
    --cc=chentaotao@didiglobal.com \
    --cc=jack@suse.cz \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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®