public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] notification tree - numerous inotify fixes
Date: Tue, 21 Jul 2009 16:03:37 -0400	[thread overview]
Message-ID: <1248206617.2654.351.camel@localhost> (raw)

Linus please consider pulling from the notification tree.  They are all
bug fixes in either inotify or fsnotify which were introduced with the
fsnotify conversion.  We've got a DoS, OOM, deadlock, functionality
regression, and all sorts of fun.....

-Eric

The following changes since commit aea1f7964ae6cba5eb419a958956deb9016b3341:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../sam/kbuild-fixes

are available in the git repository at:

  git://git.infradead.org/users/eparis/notify.git for-linus

Eric Paris (7):
      inotify: drop user watch count when a watch is removed
      inotify: do not leak inode marks in inotify_add_watch
      inotify: fix error paths in inotify_update_watch
      fsnotify: use def_bool in kconfig instead of letting the user choose
      inotify: check filename before dropping repeat events
      fsnotify: fix inotify tail drop check with path entries
      inotify: use GFP_NOFS under potential memory pressure

 fs/notify/Kconfig                |   12 +----
 fs/notify/dnotify/Kconfig        |    2 +-
 fs/notify/fsnotify.c             |    4 +-
 fs/notify/inotify/Kconfig        |    2 +-
 fs/notify/inotify/inotify_user.c |  109 ++++++++++++++++++++++++-------------
 fs/notify/notification.c         |   19 +++++--
 include/linux/fsnotify_backend.h |    2 +-
 7 files changed, 91 insertions(+), 59 deletions(-)



                 reply	other threads:[~2009-07-21 20:03 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=1248206617.2654.351.camel@localhost \
    --to=eparis@redhat.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