linux-kernel - [GIT PULL] please pull file-locking related change for v4.0 (#3)

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>] [day] [month] [year] [list]

Message-ID: <20150306071511.485e1861@tlielax.poochiereds.net>
Date:	Fri, 6 Mar 2015 07:15:11 -0500
From:	Jeff Layton <jlayton@...chiereds.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Daniel Wagner <daniel.wagner@...-carit.de>
Subject: [GIT PULL] please pull file-locking related change for v4.0 (#3)

Hi Linus,

The following changes since commit 6587457b4b3d663b237a0f95ddf6e67d1828c8ea:

  Merge tag 'dma-buf-for-4.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/sumits/dma-buf (2015-03-04 09:59:51 -0800)

are available in the git repository at:

  git://git.samba.org/jlayton/linux.git tags/locks-v4.0-3

for you to fetch changes up to 0164bf0239777811bdc3e01f45501174dc6db19d:

  locks: fix fasync_struct memory leak in lease upgrade/downgrade handling (2015-03-04 17:34:32 -0500)

----------------------------------------------------------------
File locking related fix for v4.0 (#3)

Just a single patch to fix a memory leak that Daniel Wagner discovered
while doing some testing with leases.

----------------------------------------------------------------
Jeff Layton (1):
      locks: fix fasync_struct memory leak in lease upgrade/downgrade handling

 fs/locks.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


-- 
Jeff Layton <jlayton@...chiereds.net>
--
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/