All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
	Christian Brauner <christian@brauner.io>,
	Jens Axboe <axboe@kernel.dk>, Todd Kjos <tkjos@google.com>,
	Giuseppe Scrivano <gscrivan@redhat.com>
Subject: Re: [RFC] unify the file-closing stuff in fs/file.c
Date: Sat, 14 May 2022 23:33:01 +0000	[thread overview]
Message-ID: <YoA8LSXfYTITfnKm@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20220513105218.6feck5rqd7igipj2@wittgenstein>

On Fri, May 13, 2022 at 12:52:18PM +0200, Christian Brauner wrote:

> 	Context: Caller must hold files_lock.

Done and force-pushed to #work.fd
 
> Also, there's a bunch of regression tests I added in:
> 
> tools/testing/selftests/core/close_range_test.c
> 
> including various tests for issues reported by syzbot. Might be worth
> running to verify we didn't regress anything.

# PASSED: 7 / 7 tests passed.
# Totals: pass:7 fail:0 xfail:0 xpass:0 skip:0 error:0

  reply	other threads:[~2022-05-14 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 21:20 [RFC] unify the file-closing stuff in fs/file.c Al Viro
2022-05-12 23:26 ` [RFC][PATCH] get rid of the remnants of 'batched' fget/fput stuff Al Viro
2022-05-12 23:48   ` Jens Axboe
2022-05-13  0:48     ` Al Viro
2022-05-13 10:15   ` Christian Brauner
2022-05-12 23:48 ` [RFC] unify the file-closing stuff in fs/file.c Jens Axboe
2022-05-13  0:46   ` Todd Kjos
2022-05-13 10:52 ` Christian Brauner
2022-05-14 23:33   ` Al Viro [this message]
2022-05-16  8:04     ` Christian Brauner

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=YoA8LSXfYTITfnKm@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=christian@brauner.io \
    --cc=gscrivan@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tkjos@google.com \
    /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.