Linux filesystem development
 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
Subject: [git pull] missed close_range() fix from back in August...
Date: Fri, 4 Oct 2024 05:56:56 +0100	[thread overview]
Message-ID: <20241004045656.GP4017910@ZenIV> (raw)

My apologies - I thought I'd sent it back in late August, but it had
fallen through the cracks ;-/  Sat in -next all along, rebased verbatim
to 6.12-rc1 and sat in -next in that form since Oct 1.

The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:

  Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)

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 678379e1d4f7443b170939525d3312cfc37bf86b:

  close_range(): fix the logics in descriptor table trimming (2024-09-29 21:52:29 -0400)

----------------------------------------------------------------
close_range(): fix the logics in descriptor table trimming

----------------------------------------------------------------
Al Viro (1):
      close_range(): fix the logics in descriptor table trimming

 fs/file.c               | 95 ++++++++++++++++++-------------------------------
 include/linux/fdtable.h |  8 ++---
 kernel/fork.c           | 32 ++++++++---------
 3 files changed, 52 insertions(+), 83 deletions(-)

             reply	other threads:[~2024-10-04  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04  4:56 Al Viro [this message]
2024-10-04 17:50 ` [git pull] missed close_range() fix from back in August 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=20241004045656.GP4017910@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox