All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	david@fromorbit.com, linux-kernel@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] vfs: fixes for 5.18-rc1
Date: Fri, 1 Apr 2022 18:03:38 -0700	[thread overview]
Message-ID: <20220402010338.GP27690@magnolia> (raw)

Hi Linus,

Please pull this branch of VFS bugfixes for 5.18-rc1.  The erofs
developers felt that FIEMAP should handle ranged requests starting at
s_maxbytes by returning EFBIG instead of passing the filesystem
implementation a nonsense 0-byte request.

Not sure why they keep tagging this 'iomap', but the VFS shouldn't be
asking for information about ranges of a file that the filesystem
already declared that it does not support.

As usual, I did a test-merge with upstream master as of a few minutes
ago, and didn't see any conflicts.  Please let me know if you encounter
any problems.

--D

The following changes since commit 7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3:

  Linux 5.17-rc6 (2022-02-27 14:36:33 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/vfs-5.18-merge-1

for you to fetch changes up to 49df34221804cfd6384135b28b03c9461a31d024:

  fs: fix an infinite loop in iomap_fiemap (2022-03-30 09:49:28 -0700)

----------------------------------------------------------------
Fixes for 5.18-rc1:
 - Fix a potential infinite loop in FIEMAP by fixing an off by one error
   when comparing the requested range against s_maxbytes.

----------------------------------------------------------------
Guo Xuenan (1):
      fs: fix an infinite loop in iomap_fiemap

 fs/ioctl.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2022-04-02  1:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  1:03 Darrick J. Wong [this message]
2022-04-02  3:07 ` pr-tracker-bot

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=20220402010338.GP27690@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] vfs: fixes for 5.18-rc1' \
    /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

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.