Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
> The DF issue may turn out to be harmless from a security standpoint,
> but it should not be assumed.
If so, then why is this subscriber-only content?
Posted Mar 7, 2008 22:07 UTC (Fri) by corbet (editor, #1)
By the time any distributor is carrying 4.3.x, the article will have long since become free...
Posted Mar 7, 2008 22:39 UTC (Fri) by JoeBuck (subscriber, #2330)
Posted Mar 8, 2008 13:59 UTC (Sat) by i3839 (guest, #31386)
No, I'm not. I just thought that 4.3.0 was released, and was already in use by distros, so
that the matter was more urgent than it is. 4.3.0 is the upcoming release and not yet
released, so ignore me.
To clarify, if it's an urgent case I would find it strange if there was a subscribers-only
article with background info, but not a generic article informing people about the problem.
I'm not saying LWN should notify people of every security event, nor open all security related
GCC 4.3.0 exposes a kernel bug
Posted Mar 8, 2008 12:00 UTC (Sat) by darwish07 (subscriber, #49520)
This is an __insult__ to the lovely LWN's extremely open way of news reporting with also
extremely low-cost subscription cost.
LWN is not a security advisory website!
Posted Mar 9, 2008 17:44 UTC (Sun) by Max.Hyre (subscriber, #1054)
Posted Mar 9, 2008 20:12 UTC (Sun) by i3839 (guest, #31386)
True, but keep in mind that this is an unusual case, as just upgrading gcc won't fix it. All
applications compiled with gcc 4.3.0 running on Linux or BSD are prone to this potential
problem, including those that are compiled by the users themselves.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds