linux-kernel - Re: [PATCH] [coda] Remove incorrect unlock_kernel from allocation failure path in coda

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

Message-ID: <20060725000812.GJ26153@delft.aura.cs.cmu.edu>
Date:	Mon, 24 Jul 2006 20:08:12 -0400
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	Josh Triplett <josht@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] [coda] Remove incorrect unlock_kernel from allocation failure path in coda_open

On Mon, Jul 24, 2006 at 07:29:24PM -0400, Josh Triplett wrote:
> Commit 398c53a757702e1e3a7a2c24860c7ad26acb53ed (in the historical GIT tree)
> moved the lock_kernel() in coda_open after the allocation of a coda_file_info
> struct, but left an unlock_kernel() in the allocation failure error path;
> remove it.
> 
> Signed-off-by: Josh Triplett <josh@...edesktop.org>

Acked-by: Jan Harkes <jaharkes@...cmu.edu>

---

Totally correct fix, I actually thought I already sent a patch for the
same problem upstream. I should dig through my local trees to check if
anything else fell through the cracks.

Jan
-
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/