From: Andrew Morton <akpm@linux-foundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org, htejun@gmail.com,
neilb@suse.de
Subject: Re: [RFC PATCH] sysfs: refill attribute buffer when reading from offset 0
Date: Sat, 5 Apr 2008 23:29:59 -0700 [thread overview]
Message-ID: <20080405232959.c6504be8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080405184122.2816.35845.stgit@dwillia2-linux.ch.intel.com>
On Sat, 05 Apr 2008 11:41:22 -0700 Dan Williams <dan.j.williams@intel.com> wrote:
> Requiring userspace to close and re-open sysfs attributes has been the
> policy since before 2.6.12. It allows userspace to get a consistent
> snapshot of kernel state and consume it with incremental reads and seeks.
>
> Now, if the file position is zero the kernel assumes userspace wants to see
> the new value.
This does sound a sensible change.
> The application for this change is to allow a userspace
> RAID metadata handler to check the state of an array without causing any
> memory allocations. Thus not causing writeback to a raid array that might
> be blocked waiting for userspace to take action.
Although that sounds like a rather, umm, optimistic application. I guess
if everything's mlocked you might get lucky.
> Cc: NeilBrown <neilb@suse.de>
> Cc: Tejun Heo <htejun@gmail.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
>
> fs/sysfs/file.c | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
>
> diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c
> index baa663e..0a26ba8 100644
> --- a/fs/sysfs/file.c
> +++ b/fs/sysfs/file.c
> @@ -128,7 +128,7 @@ sysfs_read_file(struct file *file, char __user *buf, size_t count, loff_t *ppos)
> ssize_t retval = 0;
>
> mutex_lock(&buffer->mutex);
> - if (buffer->needs_read_fill) {
> + if (buffer->needs_read_fill || *ppos == 0) {
> retval = fill_read_buffer(file->f_path.dentry,buffer);
> if (retval)
> goto out;
> @@ -409,8 +409,7 @@ static int sysfs_release(struct inode *inode, struct file *filp)
> * return POLLERR|POLLPRI, and select will return the fd whether
> * it is waiting for read, write, or exceptions.
> * Once poll/select indicates that the value has changed, you
> - * need to close and re-open the file, as simply seeking and reading
> - * again will not get new data, or reset the state of 'poll'.
> + * need to close and re-open the file, or seek to 0 and read again.
> * Reminder: this only works for attributes which actively support
> * it, and it is not possible to test an attribute from userspace
> * to see if it supports poll (Neither 'poll' nor 'select' return
>
Has this been tested with pread()? That should work - doing an lseek+read
is plain dopey.
Can we now remove need_read_fill? Not if we want to support
open+lseek+read, I guess - this initial read might not be at offset
zero.
next prev parent reply other threads:[~2008-04-06 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 18:41 [RFC PATCH] sysfs: refill attribute buffer when reading from offset 0 Dan Williams
2008-04-06 6:29 ` Andrew Morton [this message]
2008-04-07 12:43 ` Tejun Heo
2008-04-07 22:35 ` Dan Williams
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=20080405232959.c6504be8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.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 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.