From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Eric Paris <eparis@parisplace.org>,
Jan Kara <jack@suse.cz>
Subject: [PATCH 0/5 v2] Fanotify cleanups
Date: Mon, 3 Mar 2014 12:12:18 +0100 [thread overview]
Message-ID: <1393845143-28007-1-git-send-email-jack@suse.cz> (raw)
Hello,
when fixing use-after-free bug with fanotify introduced by my previous
cleanup patches (the fix is already merged by Linus), I have better understood
handling of permission events and found a couple of things that can be further
cleaned up. This patch series uses the notify structure itself for processing
response to permission event (patch 2/5) thus saving some space and allocation,
converts access_mutex to spinlock (patch 3/5) which should be faster, and moves
code around copy_event_to_user() to make code more readable (patch 4/5, 5/5).
The patches pass LTP fanotify tests. Andrew, can you please take the patches?
Changes since v1:
- rebased on top of latest fanotify fixes which went to Linus (3.13-rc5)
Honza
next reply other threads:[~2014-03-03 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 11:12 Jan Kara [this message]
2014-03-03 11:12 ` [PATCH 1/5] fanotify: Remove useless bypass_perm check Jan Kara
2014-03-03 11:12 ` [PATCH 2/5] fanotify: Use fanotify event structure for permission response processing Jan Kara
2014-03-03 11:12 ` [PATCH 3/5] fanotify: Convert access_mutex to spinlock Jan Kara
2014-03-03 11:12 ` [PATCH 4/5] fanotify: Reorganize loop in fanotify_read() Jan Kara
2014-03-03 11:12 ` [PATCH 5/5] fanotify: Move unrelated handling from copy_event_to_user() 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=1393845143-28007-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®