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 <[email protected]>

Acked-by: Jan Harkes <[email protected]>

---

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] [coda] Remove incorrect unlock_kernel from allocation failure path in coda_open
    • From: Josh Triplett <[email protected]>

• Prev by Date: Re: softmac possible null deref [was: Complete report of Null dereference errors in kernel 2.6.17.1]
• Next by Date: Re: softmac possible null deref [was: Complete report of Null dereference errors in kernel 2.6.17.1]
• Previous by thread: [PATCH] [coda] Remove incorrect unlock_kernel from allocation failure path in coda_open
• Next by thread: [PATCH] [efs] Remove incorrect unlock_kernel from failure path in efs_symlink_readpage
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]