linux-kernel - Re: [PATCH] Pass sparse the lock expression given to lock annotations

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: <20060824210531.6264f285.akpm@osdl.org>
Date:	Thu, 24 Aug 2006 21:05:31 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Josh Triplett <josht@...ibm.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Pass sparse the lock expression given to lock
 annotations

On Thu, 24 Aug 2006 17:48:56 -0700
Josh Triplett <josht@...ibm.com> wrote:

> The lock annotation macros __acquires, __releases, __acquire, and __release
> all currently throw the lock expression passed as an argument.  Now that
> sparse can parse __context__ and __attribute__((context)) with a context
> expression, pass the lock expression down to sparse as the context expression.

What is the dependency relationship between your kernel changes and your
proposed change to sparse?

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