[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167824999281.2129363.10471803960046031746.b4-ty@mit.edu>
Date: Tue, 7 Mar 2023 23:33:21 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-kernel@...r.kernel.org,
Tudor Ambarus <tudor.ambarus@...aro.org>,
Jun Nie <jun.nie@...aro.org>, Lee Jones <joneslee@...gle.com>,
linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca
Subject: Re: [PATCH] ext4: fix another off-by-one fsmap error on 1k block filesystems
On Thu, 16 Feb 2023 10:55:48 -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@...nel.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@....edu>
Powered by blists - more mailing lists