From: Oliver Neukum <oliver@neukum.org>
To: linux-kernel@vger.kernel.org
Subject: doubts on file_pos_write()
Date: Tue, 2 Jan 2007 09:17:12 +0100 [thread overview]
Message-ID: <200701020917.12896.oliver@neukum.org> (raw)
Hi,
as loff_t is a 64 bit value, it seems to me to a simple assignment
in file_pos_write() means that the offset can be turned into garbage
doing concurrent reads with shared fds around the 4GB limit on 32 bit
architectures.
Comments?
Regards
Oliver
reply other threads:[~2007-01-02 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200701020917.12896.oliver@neukum.org \
--to=oliver@neukum.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
all inboxes | Powered by JetHome®