mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: FW: Linux kernel file offset pointer races
Date: Mon, 9 Aug 2004 10:24:50 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408091020440.1832@ppc970.osdl.org> (raw)
In-Reply-To: <20040809165012.25562.qmail@lwn.net>



On Mon, 9 Aug 2004, Jonathan Corbet wrote:
> 
> This (along with the bits which have just gone into BK) hints at a
> driver API change.  Inquiring minds are *very* curious about such things
> at the moment...  will there be a file_operations method prototype
> change associated with the file offset fixes?

No, it's all just building up to the kernel internally always using a 
pread/pwrite-like thing to the drivers, and then maintaining f_pos 
entirely in the VFS layer. All the VFS interfaces do this already (since 
that is how the user-visible pread/pwrite works).

But a few drivers are buggy (they access f_pos directly even if it was a
user-level pread/pwrite), and in particular the /proc sysctl interface was
totally broken this way.

So I've fixed the sysctl code - that _did_ require a prototype change, but 
wasn't horribly painful, and am going through drivers..

		Linus

  reply	other threads:[~2004-08-09 17:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  8:42 Giuliano Pochini
2004-08-05 10:30 ` Jirka Kosina
2004-08-07 17:15   ` Marcelo Tosatti
2004-08-11 14:26     ` Andrey Savochkin
2004-08-11 21:14       ` Marcelo Tosatti
2004-08-12  7:55         ` Andrey Savochkin
2004-08-12 13:53           ` Marcelo Tosatti
2004-08-09  8:33   ` Frank Steiner
2004-08-09 14:45     ` Alan Cox
2004-08-09 16:50       ` Jonathan Corbet
2004-08-09 17:24         ` Linus Torvalds [this message]
2004-08-10  6:08       ` Frank Steiner
2004-08-05 20:34 ` Alan Cox

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=Pine.LNX.4.58.0408091020440.1832@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®