From: Christoph Hellwig <hch@lst.de>
To: Gulam Mohamed <gulam.mohamed@oracle.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai1@huaweicloud.com, hch@lst.de, axboe@kernel.dk
Subject: Re: [PATCH V5 for-6.11/block] loop: Fix a race between loop detach and loop open
Date: Sat, 15 Jun 2024 06:45:19 +0200 [thread overview]
Message-ID: <20240615044519.GA28679@lst.de> (raw)
In-Reply-To: <20240615012138.120364-1-gulam.mohamed@oracle.com>
Umm, so this is back to not just doing autoclear all the time?
What I suggested was to go to my RFC patch that still does the
unconditional autclear, but which sets rundown when there was
just a single opener.
next prev parent reply other threads:[~2024-06-15 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 1:21 [PATCH V5 for-6.11/block] loop: Fix a race between loop detach and loop open Gulam Mohamed
2024-06-15 4:45 ` Christoph Hellwig [this message]
2024-06-18 16:09 ` Gulam Mohamed
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=20240615044519.GA28679@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=gulam.mohamed@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yukuai1@huaweicloud.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