linux-fsdevel.vger.kernel.org archive mirror
 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] xfs: legacy Irix ioctl housecleaning for 5.17-rc1, part 2
Date: Thu, 20 Jan 2022 10:59:20 -0800	[thread overview]
Message-ID: <20220120185920.GP13540@magnolia> (raw)

Hi Linus,

This is the third and final of a series of small pull requests that
perform some long overdue housecleaning of XFS ioctls.  This time, we're
withdrawing all variants of the ALLOCSP and FREESP ioctls from XFS'
userspace API.  This might be a little premature since we've only just
removed the functionality, but as I pointed out in the last pull
request, nobody (including fstests) noticed that it was broken for 20
years.

In response to the patch, we received a single comment from someone who
stated that they 'augment' the ioctl for their own purposes, but
otherwise acquiesced to the withdrawal.  I still want to try to clobber
these old ioctl definitions in 5.17, but if you decide that we should
wait longer, I can work with that.

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 4d1b97f9ce7c0d2af2bb85b12d48e6902172a28e:

  xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls (2022-01-17 09:16:41 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.17-merge-6

for you to fetch changes up to b3bb9413e717b44e4aea833d07f14e90fb91cf97:

  xfs: remove the XFS_IOC_{ALLOC,FREE}SP* definitions (2022-01-17 09:17:11 -0800)

----------------------------------------------------------------
Withdraw the XFS_IOC_ALLOCSP* and XFS_IOC_FREESP* ioctl definitions.

Remove the header definitions for these ioctls.  The just-removed
implementation has allowed callers to read stale disk contents for more
than **21 years** and nobody noticed or complained, which implies a lack
of users aside from exploit programs.

----------------------------------------------------------------
Darrick J. Wong (1):
      xfs: remove the XFS_IOC_{ALLOC,FREE}SP* definitions

 fs/xfs/libxfs/xfs_fs.h | 8 ++++----
 fs/xfs/xfs_ioctl.c     | 9 +++++++++
 fs/xfs/xfs_ioctl32.h   | 4 ----
 3 files changed, 13 insertions(+), 8 deletions(-)

             reply	other threads:[~2022-01-20 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 18:59 Darrick J. Wong [this message]
2022-01-21  6:56 ` [GIT PULL] xfs: legacy Irix ioctl housecleaning for 5.17-rc1, part 2 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=20220120185920.GP13540@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 \
    /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;
as well as URLs for NNTP newsgroup(s).