mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>, Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Christian Brauner <brauner@kernel.org>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Taotao Chen <chentaotao@didiglobal.com>,
	linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
	syzbot+5ad0824204c7bf9b67f2@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] minix: Add required sanity checking to minix_check_superblock()
Date: Mon, 19 Jan 2026 12:16:21 +0100	[thread overview]
Message-ID: <20260119-karitativ-blumen-0fd134fe03fd@brauner> (raw)
In-Reply-To: <20251208153947.108343-1-jkoolstra@xs4all.nl>

On Mon, 08 Dec 2025 16:39:47 +0100, Jori Koolstra wrote:
> The fs/minix implementation of the minix filesystem does not currently
> support any other value for s_log_zone_size than 0. This is also the
> only value supported in util-linux; see mkfs.minix.c line 511. In
> addition, this patch adds some sanity checking for the other minix
> superblock fields, and moves the minix_blocks_needed() checks for the
> zmap and imap also to minix_check_super_block().
> 
> [...]

Applied to the vfs-7.0.minix branch of the vfs/vfs.git tree.
Patches in the vfs-7.0.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-7.0.minix

[1/1] minix: Add required sanity checking to minix_check_superblock()
      https://git.kernel.org/vfs/vfs/c/8c97a6ddc956

      parent reply	other threads:[~2026-01-19 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 15:39 Jori Koolstra
2025-12-09  8:48 ` Jan Kara
2025-12-20 19:20   ` Jori Koolstra
2026-01-17 19:50   ` Jori Koolstra
2026-01-19 11:16 ` 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=20260119-karitativ-blumen-0fd134fe03fd@brauner \
    --to=brauner@kernel.org \
    --cc=chentaotao@didiglobal.com \
    --cc=jack@suse.cz \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+5ad0824204c7bf9b67f2@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®