linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Jiri Kosina <jkosina@suse.cz>,
	Dave Jones <davej@fedoraproject.org>
Subject: [GIT PULL] fanotify use-after-free fixes
Date: Wed, 29 Jan 2014 14:12:04 +0100	[thread overview]
Message-ID: <20140129131204.GC8749@quack.suse.cz> (raw)

  Hello Linus,

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus

The pull contains three fixes for the fanotify use after free problems guys
were reporting. I have ended up with different lifetime rules for struct
fanotify_event_info depending on whether it is for permission event or
normal event which isn't ideal. My plan is to split these into two
different structures (as permission events need larger struct anyway) which
will make the rules trivial again. But that can wait for later I guess (but
I can add the patch to the pile if you want), now I wanted to make -rc1
boot for these guys.

Top of the tree is 85816794240b. The full shortlog is:

Jan Kara (3):
      fanotify: Fix use after free in mask checking
      fsnotify: Do not return merged event from fsnotify_add_notify_event()
      fanotify: Fix use after free for permission events

The diffstat is

 fs/notify/fanotify/fanotify.c        | 40 ++++++++++++++++++------------------
 fs/notify/fanotify/fanotify.h        |  7 +++++++
 fs/notify/fanotify/fanotify_user.c   |  7 ++++++-
 fs/notify/inotify/inotify_fsnotify.c | 19 +++++++----------
 fs/notify/notification.c             | 24 +++++++++++-----------
 include/linux/fsnotify_backend.h     |  8 ++++----
 6 files changed, 56 insertions(+), 49 deletions(-)

							Thanks
								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

                 reply	other threads:[~2014-01-29 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140129131204.GC8749@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=davej@fedoraproject.org \
    --cc=jkosina@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).