linux-kernel - Re: ipc/msg.c "cleanup" breaks fakeroot on Alpha

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: <20061104172954.GA3668@elte.hu>
Date:	Sat, 4 Nov 2006 18:29:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Falk Hueffner <falk@...ian.org>
Cc:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: ipc/msg.c "cleanup" breaks fakeroot on Alpha


* Falk Hueffner <falk@...ian.org> wrote:

> -	struct msg_msg* volatile r_msg;
> +	volatile struct msg_msg	*r_msg;
>  };
>  
> breaks fakeroot on Alpha (variously hangs or oopses). Backing it out 
> of 2.6.19-rc4 fixes the issue. Is it possible that this change (which 
> clearly does change semantics) was made in error?

correct, it was an error, lets back it out.

Another interesting question is: what in the IPC code relies on the 
volatility of this field, and shouldnt it be converted to explicit 
barriers instead?

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