From: Dave Jones <davej@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 0/3] Fix fanotify regression
Date: Tue, 28 Jan 2014 17:59:32 -0500 [thread overview]
Message-ID: <20140128225932.GA14891@redhat.com> (raw)
In-Reply-To: <1390948320-5683-1-git-send-email-jack@suse.cz>
On Tue, Jan 28, 2014 at 11:31:57PM +0100, Jan Kara wrote:
>
> Hello,
>
> as Dave and Jiri noticed my latest changes to notification framework
> caused some use-after-free issues with fanotify (I've been too eager to
> remove the use count in the event without realizing all the implications
> with permission events). These three patches fix the issues. Dave, Jiri,
> can you give a final testing round to this cleaned up set of patches?
Looks good to me!
Tested-by: Dave Jones <davej@fedoraproject.org>
next prev parent reply other threads:[~2014-01-28 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 22:31 [PATCH 0/3] Fix fanotify regression Jan Kara
2014-01-28 22:31 ` [PATCH 1/3] fanotify: Fix use after free in mask checking Jan Kara
2014-01-28 22:31 ` [PATCH 2/3] fsnotify: Do not return merged event from fsnotify_add_notify_event() Jan Kara
2014-01-28 22:32 ` [PATCH 3/3] fanotify: Fix use after free for permission events Jan Kara
2014-01-28 22:59 ` Dave Jones [this message]
2014-01-29 12:00 ` [PATCH 0/3] Fix fanotify regression Jiri Kosina
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=20140128225932.GA14891@redhat.com \
--to=davej@redhat.com \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--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).