From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Eric Paris <eparis@redhat.com>
Cc: Nick Piggin <npiggin@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/6] FMODE_NONOTIFY, FMODE_RANDOM and FMODE_NEG_OFFSET bits
Date: Fri, 15 Jan 2010 09:39:54 +0800 [thread overview]
Message-ID: <20100115013954.311049665@intel.com> (raw)
Andrew,
This collects my recent patches related to FMODE_* and O_*
discussed in LKML. They are mainly bug fixes.
O_* and FMODE_NONOTIFY collision fix/check
[PATCH 1/6] fanotify: fix FMODE_NONOTIFY bit number
[PATCH 2/6] bitops: compile time optimization for hweight_long(CONSTANT)
[PATCH 3/6] vfs: O_* bit numbers uniqueness check
POSIX_FADV_RANDOM misbehavior fix
[PATCH 4/6] vfs: take f_lock on modifying f_mode after open time
[PATCH 5/6] readahead: introduce FMODE_RANDOM for POSIX_FADV_RANDOM
allow negative f_pos for /dev/kmem
[PATCH 6/6] vfs: introduce FMODE_NEG_OFFSET for allowing negative f_pos
Thanks,
Fengguang
next reply other threads:[~2010-01-15 1:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 1:39 Wu Fengguang [this message]
2010-01-15 1:39 ` [PATCH 1/6] fanotify: fix FMODE_NONOTIFY bit number Wu Fengguang
2010-01-15 1:39 ` [PATCH 2/6] bitops: compile time optimization for hweight_long(CONSTANT) Wu Fengguang
2010-01-15 1:39 ` [PATCH 3/6] vfs: O_* bit numbers uniqueness check Wu Fengguang
2010-01-15 1:39 ` [PATCH 4/6] vfs: take f_lock on modifying f_mode after open time Wu Fengguang
2010-01-15 1:39 ` [PATCH 5/6] readahead: introduce FMODE_RANDOM for POSIX_FADV_RANDOM Wu Fengguang
2010-01-15 1:40 ` [PATCH 6/6] vfs: introduce FMODE_NEG_OFFSET for allowing negative f_pos Wu Fengguang
2010-01-16 12:54 ` OGAWA Hirofumi
2010-01-18 0:15 ` KAMEZAWA Hiroyuki
2010-01-18 1:17 ` OGAWA Hirofumi
2010-01-18 1:25 ` KAMEZAWA Hiroyuki
2010-01-18 1:38 ` OGAWA Hirofumi
2010-01-18 2:00 ` KAMEZAWA Hiroyuki
2010-01-18 2:13 ` OGAWA Hirofumi
2010-01-18 2:30 ` KAMEZAWA Hiroyuki
2010-01-18 3:15 ` Wu, Fengguang
2010-01-18 3:22 ` KAMEZAWA Hiroyuki
2010-01-18 5:26 ` Wu, Fengguang
2010-01-19 0:37 ` KAMEZAWA Hiroyuki
2010-01-18 1:32 ` OGAWA Hirofumi
2010-01-18 1:49 ` KAMEZAWA Hiroyuki
2010-01-18 1:59 ` OGAWA Hirofumi
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=20100115013954.311049665@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.