[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091118.095526.43570583.davem@davemloft.net>
Date: Wed, 18 Nov 2009 09:55:26 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: jslaby@...ell.com
Cc: jirislaby@...il.com, mingo@...e.hu, nhorman@...driver.com,
sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, marcin.slusarz@...il.com,
tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
torvalds@...ux-foundation.org, jmorris@...ei.org,
heiko.carstens@...ibm.com, sparclinux@...r.kernel.org
Subject: Re: [PATCH 06/16] SPARC: use ACCESS_ONCE for rlimits
From: Jiri Slaby <jslaby@...ell.com>
Date: Wed, 18 Nov 2009 15:51:52 +0100
> Make sure compiler won't do weird things with limits. E.g. fetching
> them twice may return 2 different values after writable limits are
> implemented.
>
> Signed-off-by: Jiri Slaby <jslaby@...ell.com>
Acked-by: David S. Miller <davem@...emloft.net>
But I wonder have we really seen the compiler create this
kind of situation? Or is this patch series based upon the
fact that it "could happen"?
--
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/
Powered by blists - more mailing lists