linux-kernel - RE: [PATCH] acpi: Add lock annotations to acpi_os_acquire_lock andacpi_os_release

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

Message-ID: <CFF307C98FEABE47A452B27C06B85BB601168989@hdsmsx411.amr.corp.intel.com>
Date:	Thu, 27 Jul 2006 16:59:21 -0400
From:	"Brown, Len" <len.brown@...el.com>
To:	"Josh Triplett" <josht@...ibm.com>, <linux-kernel@...r.kernel.org>
Cc:	"Andrew Morton" <akpm@...l.org>, <linux-acpi@...r.kernel.org>
Subject: RE: [PATCH] acpi: Add lock annotations to acpi_os_acquire_lock andacpi_os_release_lock

Josh,
if __acquires() and __releases() are always handled in a
Linux kernel build, then we don't need the bit in actypes.h.
Linux specific changes for sparse will never be used
in upstream ACPICA -- Linux can just diverge on these bits,
like we do for other annotations, like asmlinkage.

thanks,
-Len
-
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/