linux-kernel - Re: [stable] [2.6.22.y] {13/14} - NFSv2/v3: Fix a memory leak when using -onolock

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

Message-ID: <20080222201413.GA12330@kroah.com>
Date:	Fri, 22 Feb 2008 12:14:13 -0800
From:	Greg KH <greg@...ah.com>
To:	Oliver Pinter <oliver.pntr@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>, stable@...nel.org,
	stable-commits@...r.kernel.org
Subject: Re: [stable] [2.6.22.y] {13/14} - NFSv2/v3: Fix a memory leak when
	using -onolock - on top of 2.6.22.17

On Thu, Feb 07, 2008 at 09:03:52PM +0100, Oliver Pinter wrote:
> aka: nfs-unmount-leak.patch
> 
> From: Trond Myklebust <Trond.Myklebust@...app.com>
> Date: Tue Dec 11 11:05:19 2007 -0500
> Subject: NFSv2/v3: Fix a memory leak when using -onolock
> Patch-mainline: 2.6.24
> References: 336253
> 
> mainline: 13ef7b69b54aa8ae4ed264d0bf41339737f8543a

No, that's the wrong commit id.  Please be more careful next time, it's
no fun having to verify every id to make sure that I can trust these
patches...

It's 5cef338b30c110daf547fb13d99f0c77f2a79fbc just for future reference.

thanks,

greg k-h
--
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/