linux-kernel - Re: [PATCH] rose_node_list_lock was not released before returning to user space

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: <20080419.184010.113401925.davem@davemloft.net>
Date:	Sat, 19 Apr 2008 18:40:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	pidoux@....jussieu.fr
Cc:	ralf@...ux-mips.org, linux-kernel@...r.kernel.org,
	linux-hams@...r.kernel.org
Subject: Re: [PATCH] rose_node_list_lock was not released before returning
 to user space

From: Bernard Pidoux <pidoux@....jussieu.fr>
Date: Sat, 19 Apr 2008 23:12:20 +0200

> Subject: [PATCH] rose_node_list_lock was not released before returning to user space

BTW, I had to fix the commit message because it's not the
rose_node_list_lock that isn't being released, it's the socket lock.
--
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/