linux-kernel - Re: Shrink the held_lock struct by using bitfields.

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

Message-Id: <E1H1uI5-0000mn-0j@be1.lrz>
Date:	Wed, 03 Jan 2007 01:47:36 +0100
From:	Bodo Eggert <7eggert@....de>
To:	Dave Jones <davej@...hat.com>, mingo@...hat.com,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Shrink the held_lock struct by using bitfields.

Dave Jones <davej@...hat.com> wrote:

> Shrink the held_lock struct by using bitfields.
> This shrinks task_struct on lockdep enabled kernels by 480 bytes.

>  * The following field is used to detect when we cross into an
>  * interrupt context:
>  */
> -     int                             irq_context;
[...]
> +     unsigned char irq_context:1;
[...]

Can these fields be set by concurrent processes, e.g.:
CPU0        CPU1
load flags
            load flags
            flip bit
            store
flip bit
store

?
-- 
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html
-
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/