All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: [git pull] fix bitmap corruption on close_range(), take 2
Date: Mon, 12 Aug 2024 03:59:42 +0100	[thread overview]
Message-ID: <20240812025942.GG13701@ZenIV> (raw)

Variant that deals with that in copy_fd_bitmaps() rather than in dup_fd()
Sat in -next since last week...

The following changes since commit 8aa37bde1a7b645816cda8b80df4753ecf172bf1:

  protect the fetch of ->fd[fd] in do_dup2() from mispredictions (2024-08-01 15:51:57 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

for you to fetch changes up to 9a2fa1472083580b6c66bdaf291f591e1170123a:

  fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE (2024-08-05 19:23:11 -0400)

----------------------------------------------------------------
fix bitmap corruption on close_range(), take 2

----------------------------------------------------------------
Al Viro (1):
      fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE

 fs/file.c                                       | 30 +++++++++------------
 include/linux/bitmap.h                          | 12 +++++++++
 tools/testing/selftests/core/close_range_test.c | 35 +++++++++++++++++++++++++
 3 files changed, 60 insertions(+), 17 deletions(-)

             reply	other threads:[~2024-08-12  2:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  2:59 Al Viro [this message]
2024-08-12 15:27 ` [git pull] fix bitmap corruption on close_range(), take 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=20240812025942.GG13701@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.