linux-kernel - [GIT PULL] notification updates for 2.6.34-rcX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 May 2010 12:36:20 -0400
From:	Eric Paris <eparis@...hat.com>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org
Subject: [GIT PULL] notification updates for 2.6.34-rcX

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(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/