From: Matteo Croce <mcroce@linux.microsoft.com>
To: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Lennart Poettering <lennart@poettering.net>,
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: Tue, 23 Feb 2021 16:46:51 +0100 [thread overview]
Message-ID: <CAFnufp1zuXTVcNvSX9eE9hekZ6h455JVve0q2=Ht+xd007CVdQ@mail.gmail.com> (raw)
In-Reply-To: <20210206000903.215028-1-mcroce@linux.microsoft.com>
On Sat, Feb 6, 2021 at 1:09 AM 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.
>
> # udevadm monitor -kp |grep -e ^DEVNAME -e ^DISKSEQ &
> [1] 523
> # losetup -fP 3part
> [ 3698.615848] loop0: detected capacity change from 16384 to 0
> DEVNAME=/dev/loop0
> DISKSEQ=13
> [ 3698.647189] loop0: p1 p2 p3
> DEVNAME=/dev/loop0
> DISKSEQ=13
> DEVNAME=/dev/loop0p1
> DISKSEQ=13
> DEVNAME=/dev/loop0p2
> DISKSEQ=13
> DEVNAME=/dev/loop0p3
> DISKSEQ=13
> # losetup -fP 2part
> [ 3705.170766] loop1: detected capacity change from 40960 to 0
> DEVNAME=/dev/loop1
> DISKSEQ=14
> [ 3705.247280] loop1: p1 p2
> DEVNAME=/dev/loop1
> DISKSEQ=14
> DEVNAME=/dev/loop1p1
> DISKSEQ=14
> DEVNAME=/dev/loop1p2
> DISKSEQ=14
> # ./getdiskseq /dev/loop*
> /dev/loop0: 13
> /dev/loop0p1: 13
> /dev/loop0p2: 13
> /dev/loop0p3: 13
> /dev/loop1: 14
> /dev/loop1p1: 14
> /dev/loop1p2: 14
> /dev/loop2: 5
> /dev/loop3: 6
> /dev/loop-control: Function not implemented
> # grep . /sys/class/block/*/diskseq
> /sys/class/block/loop0/diskseq:13
> /sys/class/block/loop1/diskseq:14
> /sys/class/block/loop2/diskseq:5
> /sys/class/block/loop3/diskseq:6
> /sys/class/block/ram0/diskseq:1
> /sys/class/block/ram1/diskseq:2
> /sys/class/block/vda/diskseq:7
>
> If merged, this feature will immediately used by the userspace:
> https://github.com/systemd/systemd/issues/17469#issuecomment-762919781
>
> Matteo Croce (5):
> block: add disk sequence number
> block: add ioctl to read the disk sequence number
> block: refactor sysfs code
> block: export diskseq in sysfs
> loop: increment sequence number
>
> Documentation/ABI/testing/sysfs-block | 12 ++++++++
> block/genhd.c | 43 ++++++++++++++++++++++++---
> block/ioctl.c | 2 ++
> drivers/block/loop.c | 3 ++
> include/linux/genhd.h | 2 ++
> include/uapi/linux/fs.h | 1 +
> 6 files changed, 59 insertions(+), 4 deletions(-)
>
> --
> 2.29.2
>
Hi,
Did anyone have a chance to look at this series?
Ideas or suggestions?
Regards,
--
per aspera ad upstream
prev parent reply other threads:[~2021-02-23 15:48 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 ` [PATCH 0/5] block: add a sequence number to disks Lennart Poettering
2021-02-23 15:46 ` Matteo Croce [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='CAFnufp1zuXTVcNvSX9eE9hekZ6h455JVve0q2=Ht+xd007CVdQ@mail.gmail.com' \
--to=mcroce@linux.microsoft.com \
--cc=axboe@kernel.dk \
--cc=bluca@debian.org \
--cc=lennart@poettering.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).