On Wed, 26 Feb 2014 15:31:47 -0800, "H. Peter Anvin" said:
> Yes... it looks like the 0.4.5-rc1 that shipped in Fedora is indeed out
> of date. With 0.5.0 I "only" see 8,207 messages, which means that at
> least the linux/err.h issue is gone.
Unfortunately, that's not true, at least with the
On Wed, 26 Feb 2014 15:31:47 -0800, H. Peter Anvin said:
Yes... it looks like the 0.4.5-rc1 that shipped in Fedora is indeed out
of date. With 0.5.0 I only see 8,207 messages, which means that at
least the linux/err.h issue is gone.
Unfortunately, that's not true, at least with the Fedora
* H. Peter Anvin (h...@zytor.com) wrote:
> The number of sparse errors in the current kernel is staggering, and it
> makes sparse a lot less valuable of a tool that it otherwise could be.
> On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
> Out of those, 12,358 come from
So getting this to the point where it is genuinely useful and can be
made a ubiquitous part of the Linux development process is going to take
more work and probably involve improvements to sparse so we can indicate
in the kernel sources when something is okay or removing completely
bogus
On Thu, Feb 27, 2014 at 2:52 AM, Peter Hurley wrote:
>> The bigger question, again, is what do we need to do to make this
>> happen, assuming it is worth doing? We certainly have had bugs,
>> including security holes, which sparse would have caught. At the same
>> time, this kind of work tends
Am 27.02.2014 00:25, schrieb Borislav Petkov:
> On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
>> What do we need to do to actually make our tools be able to do work
>> for us? Newbie projects to clean up?
>
> It certainly would be a much better way for newbies to get involved
Am 27.02.2014 00:25, schrieb Borislav Petkov:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
What do we need to do to actually make our tools be able to do work
for us? Newbie projects to clean up?
It certainly would be a much better way for newbies to get involved than
all
On Thu, Feb 27, 2014 at 2:52 AM, Peter Hurley pe...@hurleysoftware.com wrote:
The bigger question, again, is what do we need to do to make this
happen, assuming it is worth doing? We certainly have had bugs,
including security holes, which sparse would have caught. At the same
time, this
So getting this to the point where it is genuinely useful and can be
made a ubiquitous part of the Linux development process is going to take
more work and probably involve improvements to sparse so we can indicate
in the kernel sources when something is okay or removing completely
bogus
* H. Peter Anvin (h...@zytor.com) wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
Out of those, 12,358 come from
On Wed, Feb 26, 2014 at 10:15:08PM -0500, Dave Jones wrote:
> On Wed, Feb 26, 2014 at 05:34:24PM -0800, Greg KH wrote:
>
> > Yes, for some areas of the kernel it will take some work, but for
> > others, sparse works really well. As an example, building all of
> > drivers/usb/* with sparse
On Wed, Feb 26, 2014 at 08:19:23PM -0800, H. Peter Anvin wrote:
> On 02/26/2014 05:52 PM, Peter Hurley wrote:
> >
> > Well there was that "should we do a bug-fix-only 4.0 release?" message
> > from Linus back at the 3.12 release.
> >
>
> Sure... but will it actually happen?
I sure hope not,
On 02/26/2014 05:52 PM, Peter Hurley wrote:
>
> Well there was that "should we do a bug-fix-only 4.0 release?" message
> from Linus back at the 3.12 release.
>
Sure... but will it actually happen?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Wed, Feb 26, 2014 at 05:34:24PM -0800, Greg KH wrote:
> Yes, for some areas of the kernel it will take some work, but for
> others, sparse works really well. As an example, building all of
> drivers/usb/* with sparse only brings up 2 issues, both of which should
> probably be fixed (or
On Wed, 2014-02-26 at 17:34 -0800, Greg KH wrote:
> On Wed, Feb 26, 2014 at 04:11:30PM -0800, H. Peter Anvin wrote:
> > I have seen this phenomenon, too. I also see a bunch of sparse warnings
> > which are clearly bogus, for example complaining about sizeof(bool) when
> > in bits like:
> >
> >
On 02/26/2014 07:11 PM, H. Peter Anvin wrote:
On 02/26/2014 03:28 PM, Greg KH wrote:
What do we need to do to actually make our tools be able to do work for
us? Newbie projects to clean up? Trying to get the larger Linux
companies to put resources on it?
It's not the easiest "newbie"
On Wed, Feb 26, 2014 at 04:11:30PM -0800, H. Peter Anvin wrote:
> On 02/26/2014 03:28 PM, Greg KH wrote:
> >>
> >> What do we need to do to actually make our tools be able to do work for
> >> us? Newbie projects to clean up? Trying to get the larger Linux
> >> companies to put resources on it?
>
That would be good.
On February 26, 2014 5:19:51 PM PST, Josh Boyer
wrote:
>On Wed, Feb 26, 2014 at 6:37 PM, H. Peter Anvin wrote:
>> On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
>>> On 02/26/2014 03:29 PM, Greg KH wrote:
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
> On
On Wed, Feb 26, 2014 at 6:37 PM, H. Peter Anvin wrote:
> On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
>> On 02/26/2014 03:29 PM, Greg KH wrote:
>>> On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
> The number of
On Wed, 2014-02-26 at 16:51 -0800, H. Peter Anvin wrote:
> On 02/26/2014 04:48 PM, Joe Perches wrote:
> > err.h could also return bool instead of long for the
> > IS_ERR and IS_ERR_OR_NULL tests.
>
> This is definitely true... although we should check that that doesn't
> make the code worse as
On 02/26/2014 04:48 PM, Joe Perches wrote:
> err.h could also return bool instead of long for the
> IS_ERR and IS_ERR_OR_NULL tests.
This is definitely true... although we should check that that doesn't
make the code worse as this is used *all over* the kernel.
> Maybe something like this could
On Wed, 2014-02-26 at 14:49 -0800, H. Peter Anvin wrote:
> The number of sparse errors in the current kernel is staggering, and it
> makes sparse a lot less valuable of a tool that it otherwise could be.
> On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
> Out of those, 12,358
On 02/26/2014 03:28 PM, Greg KH wrote:
>>
>> What do we need to do to actually make our tools be able to do work for
>> us? Newbie projects to clean up? Trying to get the larger Linux
>> companies to put resources on it?
>
> It's not the easiest "newbie" project as usually the first reflex to
>
On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
> On 02/26/2014 03:29 PM, Greg KH wrote:
>> On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
>>> On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
On 02/26/2014 03:29 PM, Greg KH wrote:
> On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
>> On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
>>> The number of sparse errors in the current kernel is staggering, and it
>>> makes sparse a lot less valuable of a tool that it
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
> On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
> > The number of sparse errors in the current kernel is staggering, and it
> > makes sparse a lot less valuable of a tool that it otherwise could be.
> > On a build of x86-64
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
> The number of sparse errors in the current kernel is staggering, and it
> makes sparse a lot less valuable of a tool that it otherwise could be.
> On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
> Out of those,
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
> What do we need to do to actually make our tools be able to do work
> for us? Newbie projects to clean up?
It certainly would be a much better way for newbies to get involved than
all the useless OCD-jerking off that floats back
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
Out of those, 12,358 come from linux/err.h. Given that the latter
basically spams
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
Out of those, 12,358 come from linux/err.h. Given that the latter
basically spams
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
What do we need to do to actually make our tools be able to do work
for us? Newbie projects to clean up?
It certainly would be a much better way for newbies to get involved than
all the useless OCD-jerking off that floats back and
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
Out of those,
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64
On 02/26/2014 03:29 PM, Greg KH wrote:
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise
On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
On 02/26/2014 03:29 PM, Greg KH wrote:
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a
On 02/26/2014 03:28 PM, Greg KH wrote:
What do we need to do to actually make our tools be able to do work for
us? Newbie projects to clean up? Trying to get the larger Linux
companies to put resources on it?
It's not the easiest newbie project as usually the first reflex to
just cast it
On Wed, 2014-02-26 at 14:49 -0800, H. Peter Anvin wrote:
The number of sparse errors in the current kernel is staggering, and it
makes sparse a lot less valuable of a tool that it otherwise could be.
On a build of x86-64 allyesconfig I'm getting 20,676 sparse messages.
Out of those, 12,358
On 02/26/2014 04:48 PM, Joe Perches wrote:
err.h could also return bool instead of long for the
IS_ERR and IS_ERR_OR_NULL tests.
This is definitely true... although we should check that that doesn't
make the code worse as this is used *all over* the kernel.
Maybe something like this could be
On Wed, 2014-02-26 at 16:51 -0800, H. Peter Anvin wrote:
On 02/26/2014 04:48 PM, Joe Perches wrote:
err.h could also return bool instead of long for the
IS_ERR and IS_ERR_OR_NULL tests.
This is definitely true... although we should check that that doesn't
make the code worse as this is
On Wed, Feb 26, 2014 at 6:37 PM, H. Peter Anvin h...@zytor.com wrote:
On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
On 02/26/2014 03:29 PM, Greg KH wrote:
On Wed, Feb 26, 2014 at 03:28:59PM -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 02:49:26PM -0800, H. Peter Anvin wrote:
The number of
That would be good.
On February 26, 2014 5:19:51 PM PST, Josh Boyer jwbo...@fedoraproject.org
wrote:
On Wed, Feb 26, 2014 at 6:37 PM, H. Peter Anvin h...@zytor.com wrote:
On 02/26/2014 03:31 PM, H. Peter Anvin wrote:
On 02/26/2014 03:29 PM, Greg KH wrote:
On Wed, Feb 26, 2014 at 03:28:59PM
On Wed, Feb 26, 2014 at 04:11:30PM -0800, H. Peter Anvin wrote:
On 02/26/2014 03:28 PM, Greg KH wrote:
What do we need to do to actually make our tools be able to do work for
us? Newbie projects to clean up? Trying to get the larger Linux
companies to put resources on it?
It's not
On 02/26/2014 07:11 PM, H. Peter Anvin wrote:
On 02/26/2014 03:28 PM, Greg KH wrote:
What do we need to do to actually make our tools be able to do work for
us? Newbie projects to clean up? Trying to get the larger Linux
companies to put resources on it?
It's not the easiest newbie project
On Wed, 2014-02-26 at 17:34 -0800, Greg KH wrote:
On Wed, Feb 26, 2014 at 04:11:30PM -0800, H. Peter Anvin wrote:
I have seen this phenomenon, too. I also see a bunch of sparse warnings
which are clearly bogus, for example complaining about sizeof(bool) when
in bits like:
On Wed, Feb 26, 2014 at 05:34:24PM -0800, Greg KH wrote:
Yes, for some areas of the kernel it will take some work, but for
others, sparse works really well. As an example, building all of
drivers/usb/* with sparse only brings up 2 issues, both of which should
probably be fixed (or
On 02/26/2014 05:52 PM, Peter Hurley wrote:
Well there was that should we do a bug-fix-only 4.0 release? message
from Linus back at the 3.12 release.
Sure... but will it actually happen?
-hpa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Wed, Feb 26, 2014 at 08:19:23PM -0800, H. Peter Anvin wrote:
On 02/26/2014 05:52 PM, Peter Hurley wrote:
Well there was that should we do a bug-fix-only 4.0 release? message
from Linus back at the 3.12 release.
Sure... but will it actually happen?
I sure hope not, the backlog it
On Wed, Feb 26, 2014 at 10:15:08PM -0500, Dave Jones wrote:
On Wed, Feb 26, 2014 at 05:34:24PM -0800, Greg KH wrote:
Yes, for some areas of the kernel it will take some work, but for
others, sparse works really well. As an example, building all of
drivers/usb/* with sparse only brings
48 matches
Mail list logo
