linux-kernel - [GIT PULL] please pull file-locking related bugfix for v3.19 (and v3.18 stable)

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]

Message-ID: <20150114074620.0f80880b@tlielax.poochiereds.net>
Date:	Wed, 14 Jan 2015 07:46:20 -0500
From:	Jeff Layton <jlayton@...chiereds.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linda Walsh <suse@...nx.org>
Cc:	NeilBrown <neilb@...e.de>
Subject: [GIT PULL] please pull file-locking related bugfix for v3.19 (and
 v3.18 stable)

The following changes since commit 971780b701946be0d6e34b4abf6eec1ab05ec0c8:

  Merge tag 'gpio-v3.19-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio (2015-01-13 15:29:42 +1300)

are available in the git repository at:

  git://git.samba.org/jlayton/linux.git 52d304eb4eaced9ad04b64ba7cd6ceb5153bbf18

for you to fetch changes up to 52d304eb4eaced9ad04b64ba7cd6ceb5153bbf18:

  locks: fix NULL-deref in generic_delete_lease (2015-01-13 07:00:55 -0500)

----------------------------------------------------------------

Just a simple bugfix for a regression that I introduced into v3.18 with
the internal lease API overhaul -- mea culpa. Kudos to Linda and Neil
for tracking this down and fixing it.

----------------------------------------------------------------
NeilBrown (1):
      locks: fix NULL-deref in generic_delete_lease

 fs/locks.c | 2 +-
 1 file changed, 1 insertion(+), 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/