All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: Hannes Reinecke <hare@suse.de>
Cc: dm-devel <dm-devel@redhat.com>, Kay Sievers <kay@vrfy.org>,
	Bart Van Assche <bvanassche@acm.org>,
	Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH] libmultipath/discovery: read sysfs files uncached
Date: Thu, 04 Apr 2013 12:47:26 +0200	[thread overview]
Message-ID: <515D5A3E.6000807@profitbricks.com> (raw)
In-Reply-To: <515D53FE.9050407@suse.de>

On 04.04.2013 12:20, Hannes Reinecke wrote:
> On 04/04/2013 12:00 PM, Kay Sievers wrote:
>> On Thu, Apr 4, 2013 at 8:43 AM, Hannes Reinecke <hare@suse.de> wrote:
>>>>> Unfortunately, libudev doesn't provide an uncached variant. This
>>>>> is why we have to reimplement the functionality and some libudev
>>>>> internal functions here.
>>
>> Hannes,
>>
>> didn't you intend to use udev_device_set_sysattr_value(..., attribute,
>> NULL); to clear the cached value?
>>
> 
> Yes, it should. Question remains, though, what happens to the actual
> sysfs attribute.
> Does it remain unchained? Will it be set to '0'?

I had a look at systemd-200.tar.xz. If the value is NULL, then only the
value length is set to zero. So the sysfs file is still opened and
write() gets zero length as argument. So the file remains unchanged.
Afterwards, NULL is stored in the cache as value. For me this isn't
implemented right as you are bugging the kernel with open() and close()
without a need. Furthermore, Debian Squeeze doesn't have that
"udev_device_set_sysattr_value()" function. So at least that
distribution could need a workaround.

Cheers,
Sebastian

  reply	other threads:[~2013-04-04 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 14:28 [PATCH] libmultipath/discovery: read sysfs files uncached Sebastian Riemer
2013-04-02 21:00 ` Christophe Varoqui
2013-04-04  6:43   ` Hannes Reinecke
2013-04-04  9:42     ` Sebastian Riemer
2013-04-04 10:00     ` Kay Sievers
2013-04-04 10:20       ` Hannes Reinecke
2013-04-04 10:47         ` Sebastian Riemer [this message]
2013-04-04 11:59         ` 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=515D5A3E.6000807@profitbricks.com \
    --to=sebastian.riemer@profitbricks.com \
    --cc=bvanassche@acm.org \
    --cc=christophe.varoqui@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --cc=kay@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.