From: Karel Zak <kzak@redhat.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Milan Broz <mbroz@redhat.com>,
util-linux-ng@vger.kernel.org, linux-kernel@vger.kernel.org,
axboe@kernel.dk
Subject: Re: [PATCH] loop: add some basic read-only sysfs attributes
Date: Fri, 30 Jul 2010 09:37:04 +0200 [thread overview]
Message-ID: <20100730073704.GH1981@nb.net.home> (raw)
In-Reply-To: <AANLkTinq4TUobEwnfpMFAkCugTokSZ-8KQ-ryuv6jXCc@mail.gmail.com>
On Thu, Jul 29, 2010 at 06:07:31PM +0200, Kay Sievers wrote:
> Sure it does. Sysfs attributes need to be created _before_ uevents are
> sent out. The current behavior is that all blockdev attributes are
> safely created before the event is sent.
Hmm... I see that in add_disk(), the "queue" subdirectory is created
after disk registration (the register_disk() calls kobject_uevent()).
Is it true?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2010-07-30 7:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100722101541.GU15652@nb.net.home>
2010-07-29 13:33 ` [PATCH] loop: add some basic read-only sysfs attributes Milan Broz
2010-07-29 13:47 ` Kay Sievers
2010-07-29 14:06 ` Milan Broz
2010-07-29 14:22 ` Kay Sievers
2010-07-29 14:35 ` Milan Broz
2010-07-29 14:58 ` Karel Zak
2010-07-29 16:07 ` Kay Sievers
2010-07-29 19:56 ` Karel Zak
2010-07-29 20:06 ` Karel Zak
2010-07-29 20:24 ` Milan Broz
2010-07-30 4:36 ` Kay Sievers
2010-07-30 14:22 ` [PATCH v2] " Milan Broz
2010-07-30 14:34 ` Kay Sievers
2010-08-23 12:29 ` Karel Zak
2010-08-23 12:30 ` Jens Axboe
2010-07-30 7:37 ` Karel Zak [this message]
2010-07-30 7:43 ` [PATCH] " Kay Sievers
2010-07-30 8:01 ` Kay Sievers
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=20100730073704.GH1981@nb.net.home \
--to=kzak@redhat.com \
--cc=axboe@kernel.dk \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=util-linux-ng@vger.kernel.org \
/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