From: Amon Ott <ao@rsbac.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel file offset pointer races
Date: Sat, 7 Aug 2004 18:02:09 +0200 [thread overview]
Message-ID: <200408071802.15226.ao@rsbac.org> (raw)
In-Reply-To: <20040807131825.GE12308@parcelfarce.linux.theplanet.co.uk>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Samstag, 7. August 2004 15:18, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Sat, Aug 07, 2004 at 02:38:12PM +0200, Amon Ott wrote:
> > Would it not be useful to have per-process or per-thread offsets? Do
> > parallel processes really need to share the offset?
> >
> > E.g., the struct file could (optionally) be copied on fork with
> > copy-on-write to avoid extra memory consumption.
>
> (cat a; cat b) > /tmp/foo
Right, the process running (...) would not know what offset to give "cat b"
as a start, because it cannot see "cat a"'s final offset. It could seek to
the end of /tmp/foo before starting "cat b", but this requirement would
break existing shells. Bad luck.
As there are probably more examples why it does not work, there will
probably have to be a macro for all offset changes, which checks for
overruns.
Amon.
--
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-07 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0408041220550.26961-100000@isec.pl>
2004-08-04 20:36 ` Linux kernel file offset pointer races Pavel Kankovsky
2004-08-06 12:56 ` Alan Cox
2004-08-07 12:38 ` Amon Ott
2004-08-07 13:18 ` viro
2004-08-07 16:02 ` Amon Ott [this message]
2004-08-12 21:38 ` Pavel Kankovsky
2004-08-12 21:12 ` Alan Cox
2004-08-18 11:03 ` Pavel Kankovsky
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=200408071802.15226.ao@rsbac.org \
--to=ao@rsbac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox