From: Jan Kara <jack@suse.com>
To: linux-fsdevel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lino Sanfilippo <LinoSanfilippo@gmx.de>,
Eric Paris <eparis@parisplace.org>, Jan Kara <jack@suse.com>
Subject: [PATCH 0/3] fsnotify cleanups
Date: Mon, 27 Jul 2015 20:45:24 +0200 [thread overview]
Message-ID: <1438022727-10348-1-git-send-email-jack@suse.com> (raw)
Hello,
after understanding some of the fsnotify mark handling code when fixing
the last race I've decided to use that knowledge to improve the documentation
and somewhat cleanup the code.
The first patch in the series documents locking rules for fsnotify marks.
The second patch gets rid of special purpose free_list list head in the
fsnotify mark structure and the third patch splits the
fsnotify_destroy_mark_locked() function so that it doesn't have the awkward
property of temporarily dropping mark_mutex which can cause unexpected issues
in the caller.
All the patches have survived beating with LTP inotify and fanotify tests
(including the test excercising inode & group destruction races).
Honza
next reply other threads:[~2015-07-27 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 18:45 Jan Kara [this message]
2015-07-27 18:45 ` [PATCH 1/3] fsnotify: Document mark locking Jan Kara
2015-07-27 18:45 ` [PATCH 2/3] fsnotify: Remove mark->free_list Jan Kara
2015-07-27 18:45 ` [PATCH 3/3] fsnotify: Get rid of fsnotify_destroy_mark_locked() Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2014-11-06 13:03 [PATCH 0/3] fsnotify: Cleanups Jan Kara
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=1438022727-10348-1-git-send-email-jack@suse.com \
--to=jack@suse.com \
--cc=LinoSanfilippo@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).