[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080414175452.27c3652d@core>
Date: Mon, 14 Apr 2008 17:54:52 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Jan Kara <jack@...e.cz>
Cc: Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Bodo Eggert <7eggert@....de>,
Diego Calleja <diegocg@...il.com>,
Jiri Kosina <jkosina@...e.cz>, Michal Hocko <mhocko@...e.cz>,
Meelis Roos <mroos@...ux.ee>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org
Subject: Re: file offset corruption on 32-bit machines?
> Well, but imagine you have a file /proc/my_secret_file from which you
> are able to read from position A:a and B:b but not from position
> A:b. Concievably, checks for the file position could be bypassed because of
> this race... I know this is kind of dumb example but I can imagine someone
Unlikely as the ppos passed to the driver is a private copy and the user
could equally use pread/pwrite to specify that offset.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists