public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, chandanbabu@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/6] xfs: fix direction in XFS_IOC_EXCHANGE_RANGE
Date: Thu, 20 Jun 2024 21:32:40 -0700	[thread overview]
Message-ID: <ZnUCaCOJA5WMIsZN@infradead.org> (raw)
In-Reply-To: <171892459317.3192151.14305994848485102437.stgit@frogsfrogsfrogs>

On Thu, Jun 20, 2024 at 04:14:42PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> The kernel reads userspace's buffer but does not write it back.
> Therefore this is really an _IOW ioctl.  Change this before 6.10 final
> releases.

Eww, yes:

Reviewed-by: Christoph Hellwig <hch@lst.de>


  reply	other threads:[~2024-06-21  4:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 23:13 [PATCHSET v2] xfs: random fixes for 6.10 Darrick J. Wong
2024-06-20 23:13 ` [PATCH 1/6] xfs: fix freeing speculative preallocations for preallocated files Darrick J. Wong
2024-06-20 23:13 ` [PATCH 2/6] xfs: restrict when we try to align cow fork delalloc to cowextsz hints Darrick J. Wong
2024-06-21  4:32   ` Christoph Hellwig
2024-06-20 23:14 ` [PATCH 3/6] xfs: allow unlinked symlinks and dirs with zero size Darrick J. Wong
2024-06-20 23:14 ` [PATCH 4/6] xfs: verify buffer, inode, and dquot items every tx commit Darrick J. Wong
2024-06-20 23:14 ` [PATCH 5/6] xfs: fix direction in XFS_IOC_EXCHANGE_RANGE Darrick J. Wong
2024-06-21  4:32   ` Christoph Hellwig [this message]
2024-06-20 23:14 ` [PATCH 6/6] xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs Darrick J. Wong
2024-06-21  4:34   ` 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=ZnUCaCOJA5WMIsZN@infradead.org \
    --to=hch@infradead.org \
    --cc=chandanbabu@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox