linux-kernel - Re: [PATCH] [fuse] Add lock annotations to request_end and fuse_read

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: <E1G5J4W-0002CO-00@dorka.pomaz.szeredi.hu>
Date:	Tue, 25 Jul 2006 11:19:24 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	josht@...ibm.com
CC:	linux-kernel@...r.kernel.org, akpm@...l.org,
	fuse-devel@...ts.sourceforge.net
Subject: Re: [PATCH] [fuse] Add lock annotations to request_end and
	fuse_read_interrupt

> request_end and fuse_read_interrupt release fc->lock.  Add lock annotations to
> these two functions so that sparse can check callers for lock pairing, and so
> that sparse will not complain about these functions since they intentionally
> use locks in this manner.
> 
> Signed-off-by: Josh Triplett <josh@...edesktop.org>

Acked-by: Miklos Szeredi <miklos@...redi.hu>

Thanks,
Miklos
-
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/