All of lore.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 updates for 2.6.34-rcX
Date: Fri, 14 May 2010 12:36:20 -0400	[thread overview]
Message-ID: <1273854980.2826.28.camel@localhost> (raw)

This branch holds a couple of bug fixes (two of which are actually
stable material).  A pathological race which would put us in a use after
free / double free situation when one thread attempts to delete an
inotify watch while another thread is still adding that watch.  A memory
leak and a Kconfig issue.

Thanks
-Eric

The following changes since commit 6a251b0ab67989f468f4cb65179e0cf40cf8c295:
  Linus Torvalds (1):
        Merge branch 'for-linus' of git://git.kernel.org/.../sameo/mfd-2.6

are available in the git repository at:

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

Eric Paris (2):
      inotify: clean up the inotify_add_watch out path
      inotify: race use after free/double free in inotify inode marks

Pavel Emelyanov (1):
      inotify: don't leak user struct on inotify release

Russell King (1):
      Inotify: undefined reference to `anon_inode_getfd'

 fs/notify/inotify/Kconfig            |    1 +
 fs/notify/inotify/inotify_fsnotify.c |    2 ++
 fs/notify/inotify/inotify_user.c     |   16 ++++++++--------
 3 files changed, 11 insertions(+), 8 deletions(-)


             reply	other threads:[~2010-05-14 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 16:36 Eric Paris [this message]
2010-05-14 18:53 ` [GIT PULL] notification updates for 2.6.34-rcX Linus Torvalds
2010-05-14 18:59   ` Eric Paris

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=1273854980.2826.28.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.