From: Stefani Seibold <stefani@seibold.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Fix proc_file_write missing ppos update
Date: Sun, 30 Aug 2009 21:10:43 +0200 [thread overview]
Message-ID: <1251659443.20987.23.camel@wall-e> (raw)
In-Reply-To: <20090830080937.GA13999@x200.localdomain>
Am Sonntag, den 30.08.2009, 12:09 +0400 schrieb Alexey Dobriyan:
> On Sat, Aug 29, 2009 at 07:16:50PM -0400, Christoph Hellwig wrote:
> > On Sat, Aug 29, 2009 at 06:38:12PM +0200, Stefani Seibold wrote:
> > > The following fix a long standing issue in the proc_file_write function,
> > > which doesn't update the ppos file position pointer.
> >
> > The right fix is to get rid of the last remaining
> > read_proc_t/write_proc_t instances and switch everyone to implement file
> > operations. Alexey has been working on this on and off for a while.
>
> Yes, please, ->write_proc is going to end very soon.
>
> As for prevoius arguments:
> - changing ->write_proc signature is _of course_ going to break
> out-of-tree stuff
No, it breaks nothing. You get only a warning. I think thats okay...
> - ->proc_fops worked since forever, and since it's struct file_operations,
> nobody prohibits implementing ->write with pos update and what not.
> - seq_file is not relevant to this issue because seq_file is for read path
> only.
>
> Back into SCSI pile of users.
next prev parent reply other threads:[~2009-08-30 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 16:38 [PATCH] Fix proc_file_write missing ppos update Stefani Seibold
2009-08-29 23:16 ` Christoph Hellwig
2009-08-30 8:09 ` Alexey Dobriyan
2009-08-30 19:10 ` Stefani Seibold [this message]
2009-08-30 19:05 ` Stefani Seibold
2009-08-31 6:33 ` Alexey Dobriyan
2009-08-31 15:44 ` Arnd Bergmann
2009-08-31 17:19 ` Alexey Dobriyan
2009-08-31 17:21 ` Christoph Hellwig
2009-08-31 20:19 ` Arnd Bergmann
2009-09-12 15:28 ` Al Viro
2009-09-12 15:57 ` Stefani Seibold
2009-09-12 20:51 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2009-08-07 20:27 Stefani Seibold
2009-08-07 20:58 ` Andrew Morton
2009-08-07 21:43 ` Stefani Seibold
2009-08-07 22:16 ` Andrew Morton
2009-08-08 6:59 ` Eric W. Biederman
2009-08-08 9:29 ` Stefani Seibold
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=1251659443.20987.23.camel@wall-e \
--to=stefani@seibold.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@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 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.