public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
	Brian Foster <bfoster@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	Jan Kara <jack@suse.cz>, "Darrick J. Wong" <djwong@kernel.org>,
	Theodore Ts'o <tytso@mit.edu>,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Chandan Babu R <chandan.babu@oracle.com>
Subject: Re: [PATCH 1/6] block: remove checks for FALLOC_FL_NO_HIDE_STALE
Date: Wed, 28 Aug 2024 16:58:47 +0200	[thread overview]
Message-ID: <20240828-bauen-leben-c8bb953a9fae@brauner> (raw)
In-Reply-To: <20240827065123.1762168-2-hch@lst.de>

On Tue, 27 Aug 2024 08:50:45 +0200, Christoph Hellwig wrote:
> While the FALLOC_FL_NO_HIDE_STALE value has been registered, it has
> always been rejected by vfs_fallocate before making it into
> blkdev_fallocate because it isn't in the supported mask.
> 
> 

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

[1/6] block: remove checks for FALLOC_FL_NO_HIDE_STALE
      https://git.kernel.org/vfs/vfs/c/a24dfa515642
[2/6] ext4: remove tracing for FALLOC_FL_NO_HIDE_STALE
      https://git.kernel.org/vfs/vfs/c/c5a8e5423301
[3/6] fs: sort out the fallocate mode vs flag mess
      https://git.kernel.org/vfs/vfs/c/2f6369068139
[4/6] xfs: call xfs_flush_unmap_range from xfs_free_file_space
      https://git.kernel.org/vfs/vfs/c/2764727be269
[5/6] xfs: move the xfs_is_always_cow_inode check into xfs_alloc_file_space
      https://git.kernel.org/vfs/vfs/c/12206b1c423b
[6/6] xfs: refactor xfs_file_fallocate
      https://git.kernel.org/vfs/vfs/c/a0c3802f87a2

  parent reply	other threads:[~2024-08-28 14:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  6:50 sort out the fallocate mode mess v2 Christoph Hellwig
2024-08-27  6:50 ` [PATCH 1/6] block: remove checks for FALLOC_FL_NO_HIDE_STALE Christoph Hellwig
2024-08-27 14:55   ` Darrick J. Wong
2024-08-28 14:58   ` Christian Brauner [this message]
2024-08-28 15:31   ` Jan Kara
2024-08-27  6:50 ` [PATCH 2/6] ext4: remove tracing " Christoph Hellwig
2024-08-27 14:56   ` Darrick J. Wong
2024-08-28  4:04     ` Christoph Hellwig
2024-08-28 15:31   ` Jan Kara
2024-08-27  6:50 ` [PATCH 3/6] fs: sort out the fallocate mode vs flag mess Christoph Hellwig
2024-08-27 14:55   ` Darrick J. Wong
2024-08-28  4:05     ` Christoph Hellwig
2024-08-28 15:34   ` Jan Kara
2024-08-27  6:50 ` [PATCH 4/6] xfs: call xfs_flush_unmap_range from xfs_free_file_space Christoph Hellwig
2024-08-27 16:03   ` Darrick J. Wong
2024-08-28  4:06     ` Christoph Hellwig
2024-08-29  3:03   ` Dave Chinner
2024-08-29  3:54     ` Christoph Hellwig
2024-08-27  6:50 ` [PATCH 5/6] xfs: move the xfs_is_always_cow_inode check into xfs_alloc_file_space Christoph Hellwig
2024-08-27 16:03   ` Darrick J. Wong
2024-08-27  6:50 ` [PATCH 6/6] xfs: refactor xfs_file_fallocate Christoph Hellwig
2024-08-27 16:07   ` Darrick J. Wong
2024-08-28  4:07     ` Christoph Hellwig
2024-08-29  3:11   ` Dave Chinner
2024-08-29  3:56     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2024-08-21  6:30 sort out the fallocate mode mess Christoph Hellwig
2024-08-21  6:30 ` [PATCH 1/6] block: remove checks for FALLOC_FL_NO_HIDE_STALE Christoph Hellwig

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=20240828-bauen-leben-c8bb953a9fae@brauner \
    --to=brauner@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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