All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	linux-kernel@vger.kernel.org,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Jun Nie <jun.nie@linaro.org>, Lee Jones <joneslee@google.com>,
	linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca
Subject: Re: [PATCH] ext4: fix another off-by-one fsmap error on 1k block filesystems
Date: Tue,  7 Mar 2023 23:33:21 -0500	[thread overview]
Message-ID: <167824999281.2129363.10471803960046031746.b4-ty@mit.edu> (raw)
In-Reply-To: <Y+58NPTH7VNGgzdd@magnolia>

On Thu, 16 Feb 2023 10:55:48 -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> Apparently syzbot figured out that issuing this FSMAP call:
> 
> struct fsmap_head cmd = {
> 	.fmh_count	= ...;
> 	.fmh_keys	= {
> 		{ .fmr_device = /* ext4 dev */, .fmr_physical = 0, },
> 		{ .fmr_device = /* ext4 dev */, .fmr_physical = 0, },
> 	},
> ...
> };
> ret = ioctl(fd, FS_IOC_GETFSMAP, &cmd);
> 
> [...]

Applied, thanks!

[1/1] ext4: fix another off-by-one fsmap error on 1k block filesystems
      commit: c993799baf9c5861f8df91beb80e1611b12efcbd

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>

      parent reply	other threads:[~2023-03-08  4:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 18:55 [PATCH] ext4: fix another off-by-one fsmap error on 1k block filesystems Darrick J. Wong
2023-02-16 19:07 ` Eric Biggers
2023-02-17  8:10 ` Tudor Ambarus
2023-02-17  8:37   ` Tudor Ambarus
2023-02-17  9:04     ` Tudor Ambarus
2023-02-22 15:29   ` Tudor Ambarus
2023-03-04  2:57 ` Darrick J. Wong
2023-03-08  4:33 ` Theodore Ts'o [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=167824999281.2129363.10471803960046031746.b4-ty@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=djwong@kernel.org \
    --cc=joneslee@google.com \
    --cc=jun.nie@linaro.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tudor.ambarus@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.