On Sat, Oct 27, 2007 at 08:08:14AM +0200, Kay Sievers wrote:
> On Fri, 2007-10-26 at 19:36 -0700, Greg KH wrote:
> > On Fri, Oct 26, 2007 at 08:07:44PM +0200, Kay Sievers wrote:
> > > On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
> > > > On my openSUSE 10.3 x86_64 system running v2.6.24-rc
On Fri, 2007-10-26 at 19:36 -0700, Greg KH wrote:
> On Fri, Oct 26, 2007 at 08:07:44PM +0200, Kay Sievers wrote:
> > On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
> > > On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1,
> > > I get the sysfs rename messages.
> >
> > Care
On Fri, Oct 26, 2007 at 08:07:44PM +0200, Kay Sievers wrote:
> On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
> > On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1,
> > I get the sysfs rename messages.
>
> Care to try this? Seems like a silly bug in the core if
> SYSFS_DEP
Kay Sievers wrote:
> On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
>> On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1,
>> I get the sysfs rename messages.
>
> Care to try this? Seems like a silly bug in the core if
> SYSFS_DEPRECATED=y. That's why we didn't catch this e
On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
> On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1,
> I get the sysfs rename messages.
Care to try this? Seems like a silly bug in the core if
SYSFS_DEPRECATED=y. That's why we didn't catch this earlier, sorry.
Thanks a lot
On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1, I get the
sysfs rename messages.
Using Greg's patch, nothing changed. The log results are:
sysfs: duplicate filename 'eth1' can not be created
WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
Call Trace:
[] sysfs_add_one+0x5c/0x
On Wed, 2007-10-24 at 16:52 -0700, Greg KH wrote:
> On Wed, Oct 24, 2007 at 04:43:48PM -0700, Greg KH wrote:
> > On Wed, Oct 17, 2007 at 12:16:54PM +0200, Kay Sievers wrote:
> > > On Tue, 2007-10-16 at 16:23 -0700, Greg KH wrote:
> > > > On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote
On Wed, Oct 24, 2007 at 04:43:48PM -0700, Greg KH wrote:
> On Wed, Oct 17, 2007 at 12:16:54PM +0200, Kay Sievers wrote:
> > On Tue, 2007-10-16 at 16:23 -0700, Greg KH wrote:
> > > On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote:
> > > > From: Greg KH <[EMAIL PROTECTED]>
> > > > Date: T
On Wed, Oct 17, 2007 at 12:16:54PM +0200, Kay Sievers wrote:
> On Tue, 2007-10-16 at 16:23 -0700, Greg KH wrote:
> > On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote:
> > > From: Greg KH <[EMAIL PROTECTED]>
> > > Date: Tue, 16 Oct 2007 14:37:30 -0700
> > >
> > > > Kay, are we doing som
* Mel Gorman <[EMAIL PROTECTED]> wrote:
> Subject: Document profile=sleep requiring CONFIG_SCHEDSTATS
>
> profile=sleep only works if CONFIG_SCHEDSTATS is set. This patch notes
> the limitation in Documentation/kernel-parameters.txt and prints a
> warning at boot-time if profile=sleep is used
On Wednesday, 17 October 2007 12:17, Kay Sievers wrote:
> On 10/17/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > On Tuesday, 16 October 2007 23:36, Greg KH wrote:
> > > On Tue, Oct 16, 2007 at 11:13:19PM +0200, Rafael J. Wysocki wrote:
> > > > On Tuesday, 16 October 2007 22:50, Jens Axboe wr
On Wed, Oct 17 2007, Jens Axboe wrote:
> On Wed, Oct 17 2007, Kay Sievers wrote:
> > On 10/16/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
> > > On Tue, Oct 16 2007, Greg KH wrote:
> > > > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > > > On Tuesday, 16 October 2007 06:50, G
On Wed, Oct 17 2007, Kay Sievers wrote:
> On 10/16/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
> > On Tue, Oct 16 2007, Greg KH wrote:
> > > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > > > > On Sat, Oct 13, 2007 at 0
On 10/16/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 16 2007, Greg KH wrote:
> > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > > > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > > >
On 10/17/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> On Tuesday, 16 October 2007 23:36, Greg KH wrote:
> > On Tue, Oct 16, 2007 at 11:13:19PM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, 16 October 2007 22:50, Jens Axboe wrote:
> > > > On Tue, Oct 16 2007, Greg KH wrote:
> > > > > On Tu
On Tue, 2007-10-16 at 16:23 -0700, Greg KH wrote:
> On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote:
> > From: Greg KH <[EMAIL PROTECTED]>
> > Date: Tue, 16 Oct 2007 14:37:30 -0700
> >
> > > Kay, are we doing something wrong in userspace when renaming wireless
> > > devices such that
On Tuesday, 16 October 2007 23:36, Greg KH wrote:
> On Tue, Oct 16, 2007 at 11:13:19PM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, 16 October 2007 22:50, Jens Axboe wrote:
> > > On Tue, Oct 16 2007, Greg KH wrote:
> > > > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > >
On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote:
> From: Greg KH <[EMAIL PROTECTED]>
> Date: Tue, 16 Oct 2007 14:37:30 -0700
>
> > Kay, are we doing something wrong in userspace when renaming wireless
> > devices such that we can overlap names?
>
> It does it for all network devices,
From: Greg KH <[EMAIL PROTECTED]>
Date: Tue, 16 Oct 2007 14:37:30 -0700
> Kay, are we doing something wrong in userspace when renaming wireless
> devices such that we can overlap names?
It does it for all network devices, I see this ugly message on every
single system I have from Fedora foo to RH
On Tue, Oct 16, 2007 at 10:50:54PM +0200, Jens Axboe wrote:
> On Tue, Oct 16 2007, Greg KH wrote:
> > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > > > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
On Tue, Oct 16, 2007 at 11:13:19PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, 16 October 2007 22:50, Jens Axboe wrote:
> > On Tue, Oct 16 2007, Greg KH wrote:
> > > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > >
On Tuesday, 16 October 2007 22:50, Jens Axboe wrote:
> On Tue, Oct 16 2007, Greg KH wrote:
> > On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > > > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > >
On Tue, Oct 16 2007, Greg KH wrote:
> On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > There are many traces like this in my
On Tue, Oct 16 2007, Rafael J. Wysocki wrote:
> On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> > > appear for vanilla 2.6.23):
On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> > > appear
On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > Hi,
> >
> > There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> > appear for vanilla 2.6.23):
> >
> > <4>sysfs: duplicate filename 'ethxx1' can not be
On 10/14/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> I didn't notice that qemu was involved. Does qemu have an emulator for the
> gdth hardware?
>
I think no, the kernel just probe exist or not hardware, and hangs after that.
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> Hi,
>
> There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> appear for vanilla 2.6.23):
>
> <4>sysfs: duplicate filename 'ethxx1' can not be created
> WARNING: at /home/rafael/src/linux-2.6/fs/sysfs/dir.c:
On Sun, 2007-10-14 at 12:21 -0700, Andrew Morton wrote:
> On Sun, 14 Oct 2007 22:45:47 +0400 "Dave Milter" <[EMAIL PROTECTED]> wrote:
>
> > I build linux-2.6.23-mm1 and try to boot it using qemu,
> > and it crashed with trace like this:
> > do_page_fault
> > error_code
> > lock_acquire
> > _spin_l
Hi and thanks for your reply :)
On Friday 12 October 2007, you wrote:
> i have no quick ideas - the behavior you are seeing is quite unexpected.
> Could you try the current sched-devel code:
>
>
> http://redhat.com/~mingo/cfs-scheduler/devel/sched-devel-combo-v2.6.23.patc
>h
Maybe I messed somet
(please don't top-post! edited...)
On Sun, 14 Oct 2007 23:24:39 +0400 "Dave Milter" <[EMAIL PROTECTED]> wrote:
> On 10/14/07, Dave Milter <[EMAIL PROTECTED]> wrote:
> > I build linux-2.6.23-mm1 and try to boot it using qemu,
> > and it crashed with trace like this:
> > do_page_fault
> > error_c
By the way, because of oops happens on early stage of boot,
you not need any image to reproduce this bug:
something like this will be enough:
1)cd /tmp/ && qemu-img create hda.img 10M
2)cd linux/mm/source/code
3)qemu -kernel arch/i386/boot/bzImage -hda /tmp/hda.img
if you add "-s" to qemu options
On Sun, 14 Oct 2007 22:45:47 +0400 "Dave Milter" <[EMAIL PROTECTED]> wrote:
> I build linux-2.6.23-mm1 and try to boot it using qemu,
> and it crashed with trace like this:
> do_page_fault
> error_code
> lock_acquire
> _spin_lock_irqsave
> gdth_timeout
> run_timer_softirq
> __do_softirq
> do_softi
Ingo Molnar wrote:
* Nick Piggin <[EMAIL PROTECTED]> wrote:
;) I think you snipped the important bit:
"the peak is terrible but it has virtually no dropoff and performs
better under load than the default 2.6.21 scheduler." (verbatim)
hm, i understood that peak remark to be in reference to F
On Friday 12 October 2007 15:46, Ingo Molnar wrote:
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
> > ;) I think you snipped the important bit:
> >
> > "the peak is terrible but it has virtually no dropoff and performs
> > better under load than the default 2.6.21 scheduler." (verbatim)
>
> hm, i unde
* poison <[EMAIL PROTECTED]> wrote:
> Also the transfer rate didn't degrade too much for copying directly
> from reiserfs to reiserfs and not using encfs:
>
> dd if=/mnt/.backup/2CpGkrxvz6wgA0b0xloz8PavzMLrMymOgi9 of=/mnt/.tdata/test
> 1033+0 records in
> 1033+0 records out
> 1083179008 bytes (
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> ;) I think you snipped the important bit:
>
> "the peak is terrible but it has virtually no dropoff and performs
> better under load than the default 2.6.21 scheduler." (verbatim)
hm, i understood that peak remark to be in reference to FreeBSD's
sche
On Wednesday 10 October 2007 20:14, Ingo Molnar wrote:
> * Nicholas Miell <[EMAIL PROTECTED]> wrote:
> > Does CFS still generate the following sysbench graphs with 2.6.23, or
> > did that get fixed?
> >
> > http://people.freebsd.org/~kris/scaling/linux-pgsql.png
> > http://people.freebsd.org/~kris/
Hi =)
On Thursday 11 October 2007, Helmut Toplizer wrote:
> Hi!
>
> I had similar behavior in the kernel releases since I can think of.
It doesn't happen before 2.6.23.
> (You may find some reports about at
> http://marc.info/?a=11350857446&r=1&w=2)
>
> Maybe your problem is similar.
>
> Here
* Zhang, Yanmin <[EMAIL PROTECTED]> wrote:
> > ( Config is at http://redhat.com/~mingo/misc/config, system is Core2Duo
> > 1.83 GHz, mysql-5.0.45, glibc-2.6. Nothing fancy either in the config
> > nor in the setup - everything is pretty close to the defaults. )
>
> I used FedoraCore 8 Test2 d
Hi!
I had similar behavior in the kernel releases since I can think of.
(You may find some reports about at
http://marc.info/?a=11350857446&r=1&w=2)
Maybe your problem is similar.
Here's what have been found out:
Plugin of ehci devices causes some strange DMA thing
which causes delays becaus
On Wed, 2007-10-10 at 12:14 +0200, Ingo Molnar wrote:
> * Nicholas Miell <[EMAIL PROTECTED]> wrote:
>
> > Does CFS still generate the following sysbench graphs with 2.6.23, or
> > did that get fixed?
> >
> > http://people.freebsd.org/~kris/scaling/linux-pgsql.png
> > http://people.freebsd.org/~k
On Wed, 2007-10-10 at 12:14 +0200, Ingo Molnar wrote:
> * Nicholas Miell <[EMAIL PROTECTED]> wrote:
>
> > Does CFS still generate the following sysbench graphs with 2.6.23, or
> > did that get fixed?
> >
> > http://people.freebsd.org/~kris/scaling/linux-pgsql.png
> > http://people.freebsd.org/~k
Ingo Molnar <[EMAIL PROTECTED]> writes:
> - an uncommon embedded config combinatio: if CONFIG_EMBEDDED=y and
> CONFIG_BLOCK is unset. (a normally useless combination)
Uncommon but far from useless - may be pure initramfs-based.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line
Ingo Molnar <[EMAIL PROTECTED]> writes:
> your superblock build failure would be a new and so far unknown build
> breakage variant - please send the .config you used, and double-check
> that it's indeed a vanilla 2.6.23 tree.
It is not -- my 2.6.23 tree doesn't have the prototype that broke
th
Ingo Molnar wrote:
> * René Rebe <[EMAIL PROTECTED]> wrote:
>
>> Hi Linus et al.,
>>
>> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
[]
> your superblock build failure would be a new and so far unknown build
> breakage variant - please send the .config you used, and double
* René Rebe <[EMAIL PROTECTED]> wrote:
> Hi Linus et al.,
>
> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
i know about 4 (low-impact, cornercase) build breakages for 2.6.23-final
on x86:
- an uncommon embedded config combinatio: if CONFIG_EMBEDDED=y and
CONFIG_BLOCK
Jan Engelhardt wrote:
> On Oct 10 2007 14:36, Alexey Dobriyan wrote:
> --- linux-2.6.23/include/linux/mm.h.vanilla
> +++ linux-2.6.23/include/linux/mm.h
> +struct super_block;
> extern void drop_pagecache_sb(struct super_block *);
> void drop_pagecache(void);
> void drop_
On Oct 10 2007 14:36, Alexey Dobriyan wrote:
>> >> --- linux-2.6.23/include/linux/mm.h.vanilla
>> >> +++ linux-2.6.23/include/linux/mm.h
>> >
>> >> +struct super_block;
>> >> extern void drop_pagecache_sb(struct super_block *);
>> >> void drop_pagecache(void);
>> >> void drop_slab(void);
>> >>
On 10/10/07, Michael Tokarev <[EMAIL PROTECTED]> wrote:
> Alexey Dobriyan wrote:
> > On 10/10/07, René Rebe <[EMAIL PROTECTED]> wrote:
> >> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
> >>
> >> In file included from fs/drop_caches.c:8:
> >> include/linux/mm.h:1210: warning:
* Nicholas Miell <[EMAIL PROTECTED]> wrote:
> Does CFS still generate the following sysbench graphs with 2.6.23, or
> did that get fixed?
>
> http://people.freebsd.org/~kris/scaling/linux-pgsql.png
> http://people.freebsd.org/~kris/scaling/linux-mysql.png
as far as my testsystem goes, v2.6.23
Alexey Dobriyan wrote:
> On 10/10/07, René Rebe <[EMAIL PROTECTED]> wrote:
>> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
>>
>> In file included from fs/drop_caches.c:8:
>> include/linux/mm.h:1210: warning: 'struct super_block' declared inside
>> parameter list
>
>> --- li
On 10/10/07, René Rebe <[EMAIL PROTECTED]> wrote:
> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
>
> In file included from fs/drop_caches.c:8:
> include/linux/mm.h:1210: warning: 'struct super_block' declared inside
> parameter list
> --- linux-2.6.23/include/linux/mm.h.van
Hi Linus et al.,
2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
In file included from fs/drop_caches.c:8:
include/linux/mm.h:1210: warning: 'struct super_block' declared inside
parameter list
nclude/linux/mm.h:1210: warning: its scope is only this definition or
declaration
On Tue, 2007-10-09 at 13:54 -0700, Linus Torvalds wrote:
> Finally.
>
> Yeah, it got delayed, not because of any huge issues, but because of
> various bugfixes trickling in and causing me to reset my "release clock"
> all the time. But it's out there now, and hopefully better for the wait.
>
>
On Friday 05 October 2007 09:32:40 you wrote:
> On Fri, 5 Oct 2007, Sam Ravnborg wrote:
> > > > cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
> > > >
> > > > Obviously, this file has moved to arch/x86/boot, but it seems like
> > > > possibly unnecessary breakage. I've been c
On Fri, 5 Oct 2007, Sam Ravnborg wrote:
> > > cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
> > >
> > > Obviously, this file has moved to arch/x86/boot, but it seems like
> > > possibly unnecessary breakage. I've been copying bzImage for years
> > > from arch/x86_64/boot,
> > cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
> >
> > Obviously, this file has moved to arch/x86/boot, but it seems like
> > possibly unnecessary breakage. I've been copying bzImage for years
> > from arch/x86_64/boot, and I'm sure there's a handful of scripts
> > (o
* Glauber de Oliveira Costa <[EMAIL PROTECTED]> wrote:
> On 10/2/07, Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > This is certainly a tool issue, but if I use Debian's kernel-image
> > "make-kpkg"
> > wrapper around the kernel build system, it fails with:
> >
> > cp: cannot stat `arch/x
* Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> On Tuesday 02 October 2007 04:41:49 Linus Torvalds wrote:
> [snip]
> > In other words, people who know they may be affected and would want to
> > prepare can look at (for example)
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tglx/
On 10/4/07, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 03, 2007 at 08:11:05AM -0700, Linus Torvalds wrote:
> >...
> > and btw, there is no question what-so-ever about whether your compiler
> > might be doing a legal optimization - the compiler really is wrong, and is
> > total shit. You n
On Wed, Oct 03, 2007 at 08:11:05AM -0700, Linus Torvalds wrote:
>...
> and btw, there is no question what-so-ever about whether your compiler
> might be doing a legal optimization - the compiler really is wrong, and is
> total shit. You need to make a gcc bug-report.
>...
Ingo can't send a gcc b
On Wed, 3 Oct 2007, Jeff Garzik wrote:
>
> I'm a bit confused... you typed 2.6.24-rc4; I'm guessing you meant
> 2.6.24-rc1, but did you mean
No, I just meant "2.6.24 merge window", so:
> "x86 merge as soon as 2.6.23 is released" (merge window opens)
is the correct interpretation.
It w
Linus Torvalds wrote:
Doing it as early as possible in the 2.6.24-rc4 series (basically I'll do
it first thing) will mean that we'll have the maximum amount of time to
sort out any issues, and the thing is, Thomas and Ingo already have a tree
ready to go, so people can check their work against
On Wed, 3 Oct 2007, Jan Engelhardt wrote:
>
> >When I'm ruler of the universe, it *will* be illegal. I'm just getting a
> >bit ahead of myself.
>
> Any time frame when that will happen?
I'm working on it, I'm working on it. I'm just as frustrated as you are.
It turns out to be a non-trivial p
On Oct 3 2007 09:09, Linus Torvalds wrote:
>On Wed, 3 Oct 2007, Alan Cox wrote:
>>
>> > and btw, there is no question what-so-ever about whether your compiler
>> > might be doing a legal optimization - the compiler really is wrong, and is
>>
>> Pedant: valid. Almost all optimizations are legal,
On Wed, 3 Oct 2007, Alan Cox wrote:
>
> > and btw, there is no question what-so-ever about whether your compiler
> > might be doing a legal optimization - the compiler really is wrong, and is
>
> Pedant: valid. Almost all optimizations are legal, nobody has yet written
> laws about compilers.
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> > Your compiler generates
> >
> > movl-16(%ebp),%edx
> > movl(%edx),%edi /* this is _totally_ bogus! */
> > incl%edx
> > movl%edx,-16(%ebp)
> > movl%
On Wed, 3 Oct 2007, Ingo Molnar wrote:
>
> > - and as a result you get an exception on the *next* page:
> >
> > BUG: unable to handle kernel paging request at virtual address f2a4
>
> Hm, are you sure? This is a CONFIG_DEBUG_PAGEALLOC=y kernel, so even a
> slight overrun of a non-NIL
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Your compiler generates
>
> movl-16(%ebp),%edx
> movl(%edx),%edi /* this is _totally_ bogus! */
> incl%edx
> movl%edx,-16(%ebp)
> movl%edi,%ecx
> testb %cl,%cl
> je ...
On Wed, 3 Oct 2007, Linus Torvalds wrote:
>
> - the bug happens on this:
>
> char c = *p++;
>
> - which has been compiled into
>
> 8b 3a mov(%edx),%edi
Btw, this definitely doesn't happen for me, either on x86-64 or plain x86.
The x86 thing I tested was Fedora 8
> and btw, there is no question what-so-ever about whether your compiler
> might be doing a legal optimization - the compiler really is wrong, and is
Pedant: valid. Almost all optimizations are legal, nobody has yet written
laws about compilers. Sorry but I'm forever fixing misuse of the word
"i
El Tue, 2 Oct 2007 16:32:00 -0700 (PDT), Linus Torvalds <[EMAIL PROTECTED]>
escribió:
> Heh. The "remove sk98lin driver" bullet is sadly wrong. We had to
> reinstate it because it supported some cards that the skge driver doesn't
> handle.
Thanks, fixed
-
To unsubscribe from this list: send th
On Wed, 3 Oct 2007 15:26:01 +0100
Al Viro <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 03, 2007 at 04:08:42PM +0200, Ingo Molnar wrote:
> > > Charming... So we get d_path() either returning junk or we get
> > > something that isn't NUL-terminated. Which one it is? I.e. what
> > > does p look like
On Wed, 3 Oct 2007, Ingo Molnar wrote:
>
> hm, i just triggered the procfs crash below with -rc9 on a testbox.
You have a terminally buggy piece of shit compiler.
Lookie here:
- the bug happens on this:
char c = *p++;
- which has been compiled into
8b 3a mov
On Wed, Oct 03, 2007 at 04:08:42PM +0200, Ingo Molnar wrote:
> > Charming... So we get d_path() either returning junk or we get
> > something that isn't NUL-terminated. Which one it is? I.e. what does
> > p look like and what's in s?
>
> could be use-after-free as well, as CONFIG_PAGEALLOC wa
On Mon, 1 Oct 2007, Linus Torvalds wrote:
> So there's a final -rc out there, and right now my plan is to make this
> series really short, and release 2.6.23 in a few days. So please do give
> it a last good testing, and holler about any issues you find!
The r8169 nic performance regression is
* Al Viro <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 03, 2007 at 10:46:07AM +0200, Ingo Molnar wrote:
> >
> > hm, i just triggered the procfs crash below with -rc9 on a testbox.
> > Config attached. It's easy to reproduce it via 'service sshd restart'.
> > The crash site is:
> >
> > (gdb) list
On Wed, Oct 03, 2007 at 10:46:07AM +0200, Ingo Molnar wrote:
>
> hm, i just triggered the procfs crash below with -rc9 on a testbox.
> Config attached. It's easy to reproduce it via 'service sshd restart'.
> The crash site is:
>
> (gdb) list *0xc017599d
> 0xc017599d is in seq_path (fs/seq_fil
On (03/10/07 10:21), Ingo Molnar didst pronounce:
>
> * Mel Gorman <[EMAIL PROTECTED]> wrote:
>
> > > > Nice one Ingo - got it first try. The problem commit was
> > > > dd41f596cda0d7d6e4a8b139ffdfabcefdd46528 and it's clear that the
> > > > code removed in this commit is put back by this lates
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> -CONFIG_MAC80211_DEBUGFS=y
it's CONFIG_MAC80211_DEBUGFS=y causing the crash.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> nodev /debug debugfs rw 0 0
> ) = 290
> read(3, "", 4096) = 0
> close(3)= 0
>
> there's nothing particularly interesting in it. (perhaps debugfs)
disabling debugfs makes the crash go away so it'
update: occasionally the reading of /proc/mounts succeeds, and it's:
open("/proc/mounts", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "rootfs / rootfs rw 0 0\n/dev/root"..., 4096) = 290
write(1, "rootfs / rootfs rw 0 0\n/dev/root"..., 290rootfs / r
hm, i just triggered the procfs crash below with -rc9 on a testbox.
Config attached. It's easy to reproduce it via 'service sshd restart'.
The crash site is:
(gdb) list *0xc017599d
0xc017599d is in seq_path (fs/seq_file.c:354).
349 if (m->count < m->size) {
350
* Mel Gorman <[EMAIL PROTECTED]> wrote:
> > > Nice one Ingo - got it first try. The problem commit was
> > > dd41f596cda0d7d6e4a8b139ffdfabcefdd46528 and it's clear that the
> > > code removed in this commit is put back by this latest patch.
> > > When applied, profile=sleep works as long as
* Mel Gorman <[EMAIL PROTECTED]> wrote:
> On (02/10/07 14:15), Ingo Molnar didst pronounce:
> >
> > * Mel Gorman <[EMAIL PROTECTED]> wrote:
> >
> > > Dirt. Booting with "profile=sleep,2" is broken in 2.6.23-rc9 and
> > > 2.6.23-rc8 but working in 2.6.22. I was checking it out as part of a
> >
On Tue, 2007-10-02 at 11:17 +0200, Thomas Gleixner wrote:
[...]
> I have uploaded an update of the arch/x86 tree based on -rc9 to
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
>
[...]
> If there is anything we can help with the transition, please do not
>
On Tue, 2007-10-02 at 18:09 -0400, Bill Davidsen wrote:
> Mel Gorman wrote:
> > On (02/10/07 14:15), Ingo Molnar didst pronounce:
> >> * Mel Gorman <[EMAIL PROTECTED]> wrote:
> >>
> >>> Dirt. Booting with "profile=sleep,2" is broken in 2.6.23-rc9 and
> >>> 2.6.23-rc8 but working in 2.6.22. I was c
On Wed, 3 Oct 2007, Diego Calleja wrote:
>
> Also...if someone dislikes something in http://kernelnewbies.org/Linux_2_6_23
> ,
> or wants to fix my english, do it soon :)
Heh. The "remove sk98lin driver" bullet is sadly wrong. We had to
reinstate it because it supported some cards that the sk
El Mon, 1 Oct 2007 20:41:49 -0700 (PDT), Linus Torvalds <[EMAIL PROTECTED]>
escribió:
> So there's a final -rc out there, and right now my plan is to make this
> series really short, and release 2.6.23 in a few days. So please do give
> it a last good testing, and holler about any issues you fi
On 10/2/07, Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> This is certainly a tool issue, but if I use Debian's kernel-image "make-kpkg"
> wrapper around the kernel build system, it fails with:
>
> cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
>
> Obviously, this file
On Tuesday 02 October 2007 04:41:49 Linus Torvalds wrote:
[snip]
> In other words, people who know they may be affected and would want to
> prepare can look at (for example)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
>
> and generally get ready for the switch
On Mon, Oct 01, 2007 at 08:41:49PM -0700, Linus Torvalds wrote:
>
> I said I was hoping that -rc8 was the last -rc, and I hate doing this, but
> we've had more changes since -rc8 than we had in -rc8. And while most of
> them are pretty trivial, I really couldn't face doing a 2.6.23 release and
John Stoffel wrote:
Linus> I said I was hoping that -rc8 was the last -rc, and I hate
Linus> doing this, but we've had more changes since -rc8 than we had
Linus> in -rc8. And while most of them are pretty trivial, I really
Linus> couldn't face doing a 2.6.23 release and take the risk of some
Linu
Mel Gorman wrote:
On (02/10/07 14:15), Ingo Molnar didst pronounce:
* Mel Gorman <[EMAIL PROTECTED]> wrote:
Dirt. Booting with "profile=sleep,2" is broken in 2.6.23-rc9 and
2.6.23-rc8 but working in 2.6.22. I was checking it out as part of a
discussion in another thread and noticed it broken
> The one problem with this is that I will have trouble repulling and remerging
> the 81 subsystem tree which are part of -mm until their owners have fixed
> everything up - I'll either need to temporarily drop them or will need to
> fix them up with Thomas's script each time I fetch them.
FWI
On Tuesday, 2 October 2007 22:11, Andrew Morton wrote:
> On Tue, 2 Oct 2007 22:12:13 +0200
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > > Usage: x86-fixup-patches.py sourcepatch destpatch
> > >
> > > source and dest can be the same.
> > >
> > > A helper script to convert complete quilt
On Tue, 2 Oct 2007 22:12:13 +0200
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> > Usage: x86-fixup-patches.py sourcepatch destpatch
> >
> > source and dest can be the same.
> >
> > A helper script to convert complete quilt series is here:
> > http://userweb.kernel.org/~tglx/x86/fixupserie
On Tuesday, 2 October 2007 11:17, Thomas Gleixner wrote:
> On Mon, 1 Oct 2007, Linus Torvalds wrote:
> > This is also a good time to warn about the fact that we're doing the x86
> > merge very soon (as in the next day or two) after 2.6.23 is out, so if you
> > have pending patches for the next se
On (02/10/07 14:15), Ingo Molnar didst pronounce:
>
> * Mel Gorman <[EMAIL PROTECTED]> wrote:
>
> > Dirt. Booting with "profile=sleep,2" is broken in 2.6.23-rc9 and
> > 2.6.23-rc8 but working in 2.6.22. I was checking it out as part of a
> > discussion in another thread and noticed it broken in
1 - 100 of 215 matches
Mail list logo
