mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, LinoSanfilippo@gmx.de,
	alexey.zaytsev@gmail.com, agruen@linbit.com
Subject: [GIT PULL] notification bug fixes
Date: Wed, 15 Dec 2010 14:17:27 -0500	[thread overview]
Message-ID: <1292440647.3042.8.camel@localhost.localdomain> (raw)

The notable fixes in this pull request include a potential deadlock when
fanotify listeners exit, an unpriv user kernel memory DoS in inotify,
and an API (although not ABI) change in fanotify's userspace message to
support expansion in the next release.

-Eric

--------
The following changes since commit e8a7e48bb248a1196484d3f8afa53bded2b24e71:

  Linux 2.6.37-rc4 (2010-11-29 20:42:04 -0800)

are available in the git repository at:
  git://git.infradead.org/users/eparis/notify.git for-linus

Alexey Zaytsev (1):
      fanotify: split version into version and metadata_len

Eric Paris (5):
      fanotify: deny permissions when no event was sent
      fanotify: remove packed from access response message
      inotify: stop kernel memory leak on file creation failure
      fanotify: do not leak user reference on allocation failure
      fanotify: fill in the metadata_len field on struct fanotify_event_metadata

Lino Sanfilippo (6):
      fanotify: if set by user unset FMODE_NONOTIFY before fsnotify_perm() is called
      fanotify: correct broken ref counting in case adding a mark failed
      fanotify: Dont allow a mask of 0 if setting or removing a mark
      fanotify: on group destroy allow all waiters to bypass permission check
      fanotify: Introduce FAN_NOFD
      fanotify: Dont try to open a file descriptor for the overflow event

 fs/namei.c                         |    3 +
 fs/notify/fanotify/fanotify.c      |    6 ++-
 fs/notify/fanotify/fanotify_user.c |   81 ++++++++++++++++++++++-------------
 fs/notify/inotify/inotify_user.c   |    1 +
 include/linux/fanotify.h           |   10 +++-
 include/linux/fsnotify.h           |    3 -
 include/linux/fsnotify_backend.h   |    2 +-
 7 files changed, 68 insertions(+), 38 deletions(-)


             reply	other threads:[~2010-12-16 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 19:17 Eric Paris [this message]
2010-12-21 10:10 ` Tvrtko Ursulin

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=1292440647.3042.8.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=LinoSanfilippo@gmx.de \
    --cc=agruen@linbit.com \
    --cc=alexey.zaytsev@gmail.com \
    --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

Powered by JetHome