From: Lennart Poettering <mzxreary@0pointer.de>
To: Matteo Croce <mcroce@linux.microsoft.com>
Cc: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Luca Boccassi <bluca@debian.org>,
Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/5] block: add a sequence number to disks
Date: Mon, 8 Feb 2021 21:55:14 +0100 [thread overview]
Message-ID: <20210208205514.GA46668@gardel-login> (raw)
In-Reply-To: <20210206000903.215028-1-mcroce@linux.microsoft.com>
On Sa, 06.02.21 01:08, Matteo Croce (mcroce@linux.microsoft.com) wrote:
> From: Matteo Croce <mcroce@microsoft.com>
>
> With this series a monotonically increasing number is added to disks,
> precisely in the genhd struct, and it's exported in sysfs and uevent.
>
> This helps the userspace correlate events for devices that reuse the
> same device, like loop.
>
> The first patch is the core one, the 2..4 expose the information in
> different ways, while the last one increase the sequence number for
> loop devices at every attach.
Patch set looks excellent to me. This would be great to have for the
systems project, as it would allow us to fix some major races around
loop device allocation, that are relatively easily triggered on loaded
systems.
Lennart
next prev parent reply other threads:[~2021-02-08 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 0:08 [PATCH 0/5] block: add a sequence number to disks Matteo Croce
2021-02-06 0:08 ` [PATCH 1/5] block: add disk sequence number Matteo Croce
2021-02-06 0:09 ` [PATCH 2/5] block: add ioctl to read the " Matteo Croce
2021-02-06 0:09 ` [PATCH 3/5] block: refactor sysfs code Matteo Croce
2021-02-06 0:09 ` [PATCH 4/5] block: export diskseq in sysfs Matteo Croce
2021-02-06 0:09 ` [PATCH 5/5] loop: increment sequence number Matteo Croce
2021-02-08 20:55 ` Lennart Poettering [this message]
2021-02-23 15:46 ` [PATCH 0/5] block: add a sequence number to disks Matteo Croce
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=20210208205514.GA46668@gardel-login \
--to=mzxreary@0pointer.de \
--cc=axboe@kernel.dk \
--cc=bluca@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@linux.microsoft.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).