From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: eparis@redhat.com, viro@ZenIV.linux.org.uk,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/9] fsnotify: change locking order
Date: Tue, 27 Mar 2012 00:51:22 +0200 [thread overview]
Message-ID: <20120326225122.GA3296@Neptun> (raw)
In-Reply-To: <20120326152742.GA3124@zeus>
On Mon, Mar 26, 2012 at 04:27:42PM +0100, Luis Henriques wrote:
>
> No problem, and thank you for the update. I guess this is the sort of
> patches that actually requires a good amount of testing on -next, so
> it makes sense to wait for next window.
>
I totally agree. Better to have this in linux-next for a while and make
sure that no nasty side effects have been introduced.
prev parent reply other threads:[~2012-03-26 22:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 15:29 [PATCH 0/9] fsnotify: change locking order Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 1/9] inotify, fanotify: replace fsnotify_put_group() with fsnotify_destroy_group() Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 2/9] fsnotify: introduce fsnotify_get_group() Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 3/9] fsnotify: use reference counting for groups Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 4/9] fsnotify: take groups mark_lock before mark lock Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 5/9] fanotify: add an extra flag to mark_remove_from_mask that indicates wheather a mark should be destroyed Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 6/9] fsnotify: use a mutex instead of a spinlock to protect a groups mark list Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 7/9] fsnotify: pass group to fsnotify_destroy_mark() Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 8/9] fsnotify: introduce locked versions of fsnotify_add_mark() and fsnotify_remove_mark() Lino Sanfilippo
2011-06-14 15:29 ` [PATCH 9/9] fsnotify: dont put marks on temporary list when clearing marks by group Lino Sanfilippo
2011-08-01 20:38 ` [PATCH 0/9] fsnotify: change locking order Eric Paris
2011-08-11 23:13 ` Lino Sanfilippo
2012-03-20 18:49 ` Luis Henriques
2012-03-20 18:58 ` Eric Paris
2012-03-20 19:05 ` Luis Henriques
2012-03-22 22:14 ` Lino Sanfilippo
2012-03-26 11:27 ` Luis Henriques
2012-03-26 15:12 ` Eric Paris
2012-03-26 15:27 ` Luis Henriques
2012-03-26 22:51 ` Lino Sanfilippo [this message]
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=20120326225122.GA3296@Neptun \
--to=linosanfilippo@gmx.de \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).