linux-kernel - Re: [RFC][PATCH v4] readahead: introduce O_RANDOM for POSIX_FADV

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 Jan 2010 10:26:50 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Quentin Barnes <qbarnes+nfs@...oo-inc.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	Nick Piggin <npiggin@...e.de>,
	Steven Whitehouse <swhiteho@...hat.com>,
	David Howells <dhowells@...hat.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Jonathan Corbet <corbet@....net>
Subject: Re: [RFC][PATCH v4] readahead: introduce O_RANDOM for
	POSIX_FADV_RANDOM

On Tue, Jan 05, 2010 at 10:03:22AM +0800, Stephen Rothwell wrote:
> On Mon, 4 Jan 2010 20:56:20 +0800 Wu Fengguang <fengguang.wu@...el.com> wrote:
> >
> > For now I'll use bit 040000000, which happen to equal to
> > FMODE_NONOTIFY and will be masked out by __dentry_open()
> > in the very beginning.
> 
> But also clashes with __O_SYNC on sparc, sorry.  I am not sure how we are
> meant to reasonably choose these values any more ...

Where is it? I cannot grep find one in arch/.
There is one defined in include/asm-generic/fcntl.h:

#ifndef O_SYNC
#define __O_SYNC        04000000
#define O_SYNC          (__O_SYNC|O_DSYNC)
#endif

However it has one less '0' :)

Thanks,
Fengguang
--
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/