[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100114051308.GA14616@ZenIV.linux.org.uk>
Date: Thu, 14 Jan 2010 05:13:08 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: "Wu, Fengguang" <fengguang.wu@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Heiko Carstens <heiko.carstens@...ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Andi Kleen <andi@...stfloor.org>,
Nick Piggin <npiggin@...e.de>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Linux Memory Management List <linux-mm@...ck.org>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 1/8] vfs: fix too big f_pos handling
On Wed, Jan 13, 2010 at 10:09:56PM +0800, Wu, Fengguang wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
>
> Now, rw_verify_area() checsk f_pos is negative or not. And if
> negative, returns -EINVAL.
>
> But, some special files as /dev/(k)mem and /proc/<pid>/mem etc..
> has negative offsets. And we can't do any access via read/write
> to the file(device).
>
> This patch introduce a flag S_VERYBIG and allow negative file
> offsets.
Ehh... FMODE_NEG_OFFSET in file->f_mode, perhaps?
--
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