From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 2/3] sysfs: sysfs_attr_get_value() writes to a buffer
Date: Wed, 10 Sep 2008 11:09:18 +0000 [thread overview]
Message-ID: <1221044958.7529.6.camel@lgn.site> (raw)
In-Reply-To: <48BFEEF4.8040000@tuffmail.co.uk>
On Wed, 2008-09-10 at 11:21 +0100, Alan Jenkins wrote:
> Alan Jenkins wrote:
> > This avoids lifetime issues with the returned string, for subsequent changes
> > to caching in sysfs. All callers are changed accordingly. Many callers
> > copied the result to a buffer already, so this actually simplifies some code.
> >
>
> Sorry, my re-implementation of sysfs_attr_get_value() was defective. It
> didn't return cached values correctly.
>
> I suggest you drop these two patches. I'll fix the bug and update them
> to apply on top of the recent libudev/logging changes.
I didn't apply them, as I was busy with other stuff in libudev. We
should move the "sysfs cache" to the lib, hanging off of the the
udev_device, I guess. For this we will need to add parent device
relations in the udev_device. The current global device and attribute
cache will just go away then.
We will get there after the current work on the lib, which means
converting more stuff to libudev, and use it in the udev code.
We will also soon get rid of all dependencies on udev code in libudev,
which will remove the current udev sysfs code from libudev.
Thanks,
Kay
next prev parent reply other threads:[~2008-09-10 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 14:21 [PATCH 2/3] sysfs: sysfs_attr_get_value() writes to a buffer instead Alan Jenkins
2008-09-10 10:21 ` [PATCH 2/3] sysfs: sysfs_attr_get_value() writes to a buffer Alan Jenkins
2008-09-10 11:09 ` Kay Sievers [this message]
2008-09-15 18:32 ` [PATCH 2/3] sysfs: sysfs_attr_get_value() writes to a buffer instead of returning a string 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=1221044958.7529.6.camel@lgn.site \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).