From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Jens Axboe <axboe@kernel.dk>, Jan Kara <jack@suse.cz>,
linux-block <linux-block@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Brian Foster <bfoster@redhat.com>,
Damien Le Moal <dlemoal@kernel.org>,
Hillf Danton <hdanton@sina.com>,
Markus Elfring <Markus.Elfring@web.de>,
Ming Lei <tom.leiming@gmail.com>, Qu Wenruo <wqu@suse.com>,
Tao Cui <cui.tao@linux.dev>, kernel test robot <lkp@intel.com>,
rust-for-linux@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Nilay Shroff <nilay@linux.ibm.com>
Subject: Re: [PATCH v5 1/2] block: Add post_release() operation
Date: Mon, 5 Oct 2026 14:07:39 -0700 [thread overview]
Message-ID: <0ca00d02-9abf-4740-9dcc-05a85d88df02@acm.org> (raw)
In-Reply-To: <20261005084521.GA8879@lst.de>
On 10/5/26 1:45 AM, Christoph Hellwig wrote:
> No, adding magic out of lock extra ops is a no-go, and we've been
> through that before.
Thanks Christoph for having provided feedback. Christoph and Tetsuo,
please help with reviewing the just posted version six of this patch.
Bart.
prev parent reply other threads:[~2026-10-05 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 5:09 [PATCH v5 1/2] block: Add post_release() operation Tetsuo Handa
2026-09-23 5:10 ` [PATCH v5 2/2] loop: Perform __loop_clr_fd() from post_release callback Tetsuo Handa
2026-09-23 17:16 ` Bart Van Assche
2026-09-23 17:14 ` [PATCH v5 1/2] block: Add post_release() operation Bart Van Assche
2026-09-23 18:38 ` Gary Guo
2026-09-24 13:46 ` Tetsuo Handa
2026-09-28 17:29 ` Bart Van Assche
2026-10-05 8:45 ` Christoph Hellwig
2026-10-05 14:23 ` Tetsuo Handa
2026-10-05 21:07 ` Bart Van Assche [this message]
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=0ca00d02-9abf-4740-9dcc-05a85d88df02@acm.org \
--to=bvanassche@acm.org \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=cui.tao@linux.dev \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nilay@linux.ibm.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rust-for-linux@vger.kernel.org \
--cc=tom.leiming@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox