From: Jens Axboe <axboe@kernel.dk>
To: "Martijn Coenen" <maco@android.com>, "Alyssa Ross" <hi@alyssa.is>,
"Christoph Hellwig" <hch@lst.de>, "Greg KH" <greg@kroah.com>,
"Jan Kara" <jack@suse.cz>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: John Ogness <john.ogness@linutronix.de>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] loop: properly send KOBJ_CHANGED uevent for disk device
Date: Tue, 15 Apr 2025 07:48:22 -0600 [thread overview]
Message-ID: <174472490268.143017.12721024881216566078.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250415-loop-uevent-changed-v2-1-0c4e6a923b2a@linutronix.de>
On Tue, 15 Apr 2025 10:51:47 +0200, Thomas Weißschuh wrote:
> The original commit message and the wording "uncork" in the code comment
> indicate that it is expected that the suppressed event instances are
> automatically sent after unsuppressing.
> This is not the case, instead they are discarded.
> In effect this means that no "changed" events are emitted on the device
> itself by default.
> While each discovered partition does trigger a changed event on the
> device, devices without partitions don't have any event emitted.
>
> [...]
Applied, thanks!
[1/1] loop: properly send KOBJ_CHANGED uevent for disk device
commit: 7ed2a771b5fb3edee9c4608181235c30b40bb042
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-04-15 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 8:51 Thomas Weißschuh
2025-04-15 10:18 ` Greg KH
2025-04-15 10:24 ` Jan Kara
2025-04-15 11:07 ` Thomas Weißschuh
2025-04-15 16:33 ` Jan Kara
2025-04-15 13:48 ` Jens Axboe [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=174472490268.143017.12721024881216566078.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=hi@alyssa.is \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=stable@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®