Hi Andrew,
Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
Similar kernel Bug was reported for 2.6.23-rc2-mm1
at http://lkml.org/lkml/2007/8/10/20 and the
mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
And the same patch is in this -mm version, suspect whether is it
Paul, please apply.
On Sun, Sep 23, 2007 at 10:16:48PM +0200, Jochen Friedrich wrote:
> Here is a series fixing some bugs for 8xx powerpc CPUs.
>
> 1. [POWERPC] Fix copy'n'paste typo in commproc.c
> 2. [PPC] Fix cpm_dpram_addr returning phys mem instead of virt mem
> 3. [PPC] Compile fix for
On Mon, Sep 24, 2007 at 03:06:06PM +0200, Miklos Szeredi wrote:
> If a network filesystem protocol can't handle operations (be it data
> or metadata) on an unlinked file, we must do sillirenaming, so that
> the file is not actually unlinked.
Or not support such a broken protocol at all.
-
To
Please, try this:
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1373,11 +1373,6 @@ int generic_setlease(struct file *filp, long arg, struct
file_lock **flp)
if (new_fl == NULL)
goto out;
- error = -ENOMEM;
- new_fl = locks_alloc_lock();
- if (new_fl == NULL)
-
putting Vlad in Cc:
Cedric Le Goater wrote:
> Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
> from the #include pile but where ?
>
>
> > > and if that means adding silly rename support so be it.
> >
> > That's what is done currently.
> >
> > But it's has various dawbacks, like rmdir doesn't work if there are
> > open files within an otherwise empty directory.
> >
> > I'd happily accept suggestions on how to deal with this
On Mon, 2007-09-24 at 14:57 +0200, Rafael J. Wysocki wrote:
> > > http://tglx.de/projects/hrtimers/2.6.23-rc4/patch-2.6.23-rc4-hrt1.patches.tar.bz2
> > >
> > > applied. I also have the 2.6.23-rc6-mm1 dmesg output ready, but there's
> > > some
> > > -mm-specific noise in it. Please let me know
On Sep 24, 2007, at 01:35:08, [EMAIL PROTECTED] wrote:
On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
-static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
-{
- if (n != 0 && size > ULONG_MAX / n)
- return NULL;
- return __kmalloc(n * size, flags
On Mon, 24 Sep 2007 13:05:08 BST, Christoph Hellwig said:
> On Mon, Sep 24, 2007 at 06:35:50AM -0400, [EMAIL PROTECTED] wrote:
> > On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >
> > It
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
from the #include pile but where ?
/home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function
On Mon, Sep 24, 2007 at 02:48:08PM +0200, Miklos Szeredi wrote:
> > and if that means adding silly rename support so be it.
>
> That's what is done currently.
>
> But it's has various dawbacks, like rmdir doesn't work if there are
> open files within an otherwise empty directory.
>
> I'd
On Mon, 24 Sep 2007 18:18:30 +0530 Balbir Singh
<[EMAIL PROTECTED]> wrote:
> Peter Zijlstra wrote:
> >>> Only kswapd can do this, direct reclaim has deadlock potential.
> >> Yes, but not in all cases, do you want to add any gfp_mask
> >> based smartness for direct reclaim?
> >
> > gfp_mask
Hi Andrew,
Kernel oops over x86_64 (AMD Opteron(tm) Processor 844)
Unable to handle kernel NULL pointer dereference at 0070 RIP:
[] fasync_helper+0x6b/0xe4
PGD 181949067 PUD 182228067 PMD 0
Oops: [1] SMP
last sysfs file: /devices/system/node/possible
CPU 3
Modules linked
Hello.
Peer Chen wrote:
Code change, remove some Device IDs.
Signed-off-by: Peer Chen <[EMAIL PROTECTED]>
---
--- linux-2.6.23-rc7/drivers/ata/ahci.c.orig2007-09-20 11:01:55.0
-0400
+++ linux-2.6.23-rc7/drivers/ata/ahci.c 2007-09-24 10:08:03.0 -0400
@@ -472,6 +472,14 @@
Andy Whitcroft wrote:
> Getting compile errors on S390:
>
> CC arch/s390/mm/cmm.o
> arch/s390/mm/cmm.c: In function `cmm_init':
> arch/s390/mm/cmm.c:431: error: implicit declaration of function
> `register_oom_notifier'
> arch/s390/mm/cmm.c:443: error:
> On Mon, Sep 24, 2007 at 02:24:54PM +0200, Miklos Szeredi wrote:
> > Thanks to everyone for the feedback. Here's two of the VFS patches
> > reworked according to comments. I also plan to rework the setattr()
> > patch accordingly and perhaps the xattr patch, altough that is the
> > lowest
Peter Zijlstra wrote:
>>> Only kswapd can do this, direct reclaim has deadlock potential.
>> Yes, but not in all cases, do you want to add any gfp_mask
>> based smartness for direct reclaim?
>
> gfp_mask doesn't carry the needed information. It depends on whether
> the current context holds a
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c: In function
`dasd_eckd_build_cp':
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1181: error:
syntax
On Monday, 24 September 2007 10:07, Thomas Gleixner wrote:
> On Sun, 2007-09-23 at 22:52 +0200, Rafael J. Wysocki wrote:
> > > > Second, noacpitimer added to the command line makes all of the kernels,
> > > > up to
> > > > and including 2.6.23-rc6-mm1, boot (this seems to be 100% reproducible).
>
Once I quothed:
Make ide_rate_filter() also respect PIO/SWDMA/MWDMA mode masks. While
at it,
make the udma_filter() method calls take precedence over using the
mode masks.
This one not looking to pretty -- I've geve some thought on how to
beautify all these switch fallthoughs but
On 09/24/2007 11:52 AM, Antoine Zen-Ruffinen wrote:
> Hello,
>
> I tried to compile the kernel 2.6.9 because I want to use it with
> RTLinux and that the only 2.6.x kernel supported. I used gcc 2.95.3 as
> recommended.
> But I have an error by compilation of process.c :
>
> CC
On Mon, Sep 24, 2007 at 02:24:54PM +0200, Miklos Szeredi wrote:
> Thanks to everyone for the feedback. Here's two of the VFS patches
> reworked according to comments. I also plan to rework the setattr()
> patch accordingly and perhaps the xattr patch, altough that is the
> lowest priority.
>
>
On Mon, Sep 24, 2007 at 02:25:54PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <[EMAIL PROTECTED]>
>
> Add a new super block flag, that results in the VFS not checking if
> the current process has enough privileges to do an mknod().
>
> If this flag is set, all mounts for this super
Seeing the following from an older power LPAR, pretty sure we had
this in the previous -mm also:
Unable to handle kernel paging request for data at address 0x
Faulting instruction address: 0xc0047ac8
cpu 0x0: Vector: 300 (Data Access) at [c058f750]
pc:
On 09/24/2007 11:17 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
:00:1d.7 EHCI: BIOS
On Sep 23, 2007, at 02:22:12, Goswin von Brederlow wrote:
[EMAIL PROTECTED] (Mel Gorman) writes:
On (16/09/07 23:58), Goswin von Brederlow didst pronounce:
But when you already have say 10% of the ram in mixed groups then
it is a sign the external fragmentation happens and some time
should
Getting compile errors on S390:
CC arch/s390/mm/cmm.o
arch/s390/mm/cmm.c: In function `cmm_init':
arch/s390/mm/cmm.c:431: error: implicit declaration of function
`register_oom_notifier'
arch/s390/mm/cmm.c:443: error: implicit declaration of function
From: Miklos Szeredi <[EMAIL PROTECTED]>
Add a new super block flag, that results in the VFS not checking if
the current process has enough privileges to do an mknod().
If this flag is set, all mounts for this super block will have the
"nodev" flag implied.
This is needed on filesystems, where
Thanks to everyone for the feedback. Here's two of the VFS patches
reworked according to comments. I also plan to rework the setattr()
patch accordingly and perhaps the xattr patch, altough that is the
lowest priority.
Christoph, are these OK with you in this form?
From: Miklos Szeredi
Dear Sam,
On 9/24/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> > Hi all,
> >
> > 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> > compare to 2.6.10's autoconf.h .
> >
> > 2.6.22.7 totally changed the meaning of
On Mon, Sep 24, 2007 at 06:35:50AM -0400, [EMAIL PROTECTED] wrote:
> On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
>
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> It lived fast, it died young, it didn't leave a pretty corpse...
>
>
On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> Hi all,
>
> 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> compare to 2.6.10's autoconf.h .
>
> 2.6.22.7 totally changed the meaning of autoconf.h
autoconf.h has always been autogenerated. And autoconf.h has
On Mon, 24 Sep 2007 13:22:14 +0200 Mike Galbraith <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-09-24 at 12:42 +0200, Mike Galbraith wrote:
> > On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
> >
> > > how about something like:
> > >
> > > s64 delta = (s64)(vruntime - min_vruntime);
> > >
On Mon, Sep 24, 2007 at 04:41:54PM +0530, Jaswinder Singh wrote:
> Hi all,
>
> Can please someone let me know what is criteria for default kernel
> configuration .
>
> Is it based upon some survey or requested by Fedora or others.
>
> By default configuration size of vmlinux is 41 MB and it
Oliver Neukum wrote:
Am Freitag 21 September 2007 schrieb Jiri Kosina:
On Fri, 21 Sep 2007, Hans de Goede wrote:
Thats not what I had in mind, autosuspend doesn't work (presumably
because hal keeps polling for media change) maybe I should fix hal to
not keep polling for devices which don't
On Mon, 24 Sep 2007 16:52:15 +0530 Balbir Singh
<[EMAIL PROTECTED]> wrote:
> Peter Zijlstra wrote:
> > On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
> > <[EMAIL PROTECTED]> wrote:
> >
> >> Peter Zijlstra wrote:
> >>> Just an idea I had, it seems like a good idea to wait for RCU callbacks
> >>>
Hi all,
I want to check performance difference by using realtime preemption patch :
http://www.kernel.org/pub/linux/kernel/projects/rt/
Please let me know from where I can download samples to test realtime
preemption performance difference.
Can someone please share performance numbers for your
On Mon, 2007-09-24 at 13:08 +0200, Peter Zijlstra wrote:
> Its perfectly valid for min_vruntime to exist in 1ULL << 63.
But wrap backward timewarp is what's killing my box.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Andrew,
The kernel build fails with
CC arch/ia64/kernel/efi.o
arch/ia64/kernel/efi.c: In function 'efi_memmap_init':
arch/ia64/kernel/efi.c:1088: error: 'total_memory' undeclared (first use in
this function)
arch/ia64/kernel/efi.c:1088: error: (Each undeclared identifier is reported
On Fri, 21 Sep 2007, Andi Kleen wrote:
> > For the curious the details of all the hassle are reasonably well
> > described in the Intel's AP-578 application note.
>
> Thanks. Ok it has to stay for for i386 then; although it would be in theory
> possible to only reserve when the CPU is a real
This patch:
- makes hidp_setup_input() return int to indicate errors;
- checks its return value to handle errors.
And this time it is against -rc7-mm1 tree.
Thanks to roel and Marcel Holtmann for comments.
Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
---
net/bluetooth/hidp/core.c | 11
On Mon, 2007-09-24 at 12:42 +0200, Mike Galbraith wrote:
> On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
>
> > how about something like:
> >
> > s64 delta = (s64)(vruntime - min_vruntime);
> > if (delta > 0)
> > min_vruntime += delta;
> >
> > That would rid us of most of the
Peter Zijlstra wrote:
> On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
> <[EMAIL PROTECTED]> wrote:
>
>> Peter Zijlstra wrote:
>>> Just an idea I had, it seems like a good idea to wait for RCU callbacks
>>> in reclaim so that we won't get all of memory stuck there.
>>>
>>> If this location is
On (22/09/07 12:24), Satyam Sharma didst pronounce:
>
>
> On Thu, 20 Sep 2007, Satyam Sharma wrote:
> >
> > BTW ppc64_defconfig didn't quite like 2.6.23-rc6-mm1 either ...
> > IIRC I got build failures in:
>
> > drivers/net/spider_net.c
>
>
> [PATCH -mm] spider_net: Misc build fixes after
On (22/09/07 14:11), Satyam Sharma didst pronounce:
>
> > -static volatile int kgdb_hwbreak_sstep[NR_CPUS];
> > +volatile int kgdb_hwbreak_sstep[NR_CPUS];
>
> That looks fishy to me. Why is it volatile-qualified?
It turned out that it was unnecessary. A follow-up patch removed the volatile
and
Hi all,
Can please someone let me know what is criteria for default kernel
configuration .
Is it based upon some survey or requested by Fedora or others.
By default configuration size of vmlinux is 41 MB and it includes
approx 75% of useless stuff for me.
what is the idea behind 'default
On Mon, 24 Sep 2007 12:42:15 +0200 Mike Galbraith <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
>
> > how about something like:
> >
> > s64 delta = (s64)(vruntime - min_vruntime);
> > if (delta > 0)
> > min_vruntime += delta;
> >
> > That would rid
[EMAIL PROTECTED] wrote:
> On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> It lived fast, it died young, it didn't leave a pretty corpse...
>
> Something in the startup scripts did a 'touch',
On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
<[EMAIL PROTECTED]> wrote:
> Peter Zijlstra wrote:
> >
> > Just an idea I had, it seems like a good idea to wait for RCU callbacks
> > in reclaim so that we won't get all of memory stuck there.
> >
> > If this location is too aggressive we might
I can't see the reason ". = VDSO_PRELINK + 0x900;" was ever there in the
linker script for the x86_64 vDSO. I can't find anything that depends on
this magic offset, or that should care at all about the particular location
of of the .data section (all from vvar.c) in the vDSO image. If it is
This adds a const to the definitions vvar.c makes, so that the vdso_*
variables go into .rodata instead of .data. This is essentially a cosmetic
change, just giving the section headers in the vDSO file more pleasing flags.
These variables are read-only from the perspective of the vDSO itself and
On (22/09/07 08:20), Satyam Sharma didst pronounce:
> Hi,
>
>
> On Thu, 20 Sep 2007, Alan Cox wrote:
> >
> > On Thu, 20 Sep 2007 14:13:15 +0100
> > [EMAIL PROTECTED] (Mel Gorman) wrote:
> >
> > > PPC64 building allmodconfig fails to compile drivers/ata/pata_scc.c . It
> > > doesn't show up on
hello rday,
On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Sep 2007, Jaswinder Singh wrote:
>
> > hello rday,
> >
> > On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > > On Mon, 24 Sep 2007, Jaswinder Singh wrote:
> > >
> > > > hello rday,
> > > >
> > > > In my
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
> hello rday,
>
> On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > On Mon, 24 Sep 2007, Jaswinder Singh wrote:
> >
> > > hello rday,
> > >
> > > In my view autoconf.h is the index of kernel you are using. By
> > > reading autoconf.h you will
hello rday,
On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Sep 2007, Jaswinder Singh wrote:
>
> > hello rday,
> >
> > In my view autoconf.h is the index of kernel you are using. By
> > reading autoconf.h you will know what Architecture, drivers is
> > selected.
> >
> > For
Peter Zijlstra wrote:
>
> Just an idea I had, it seems like a good idea to wait for RCU callbacks
> in reclaim so that we won't get all of memory stuck there.
>
> If this location is too aggressive we might stick it next to
> disable_swap_token().
>
> ---
> Couple RCU and reclaim.
>
> There
On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
> how about something like:
>
> s64 delta = (s64)(vruntime - min_vruntime);
> if (delta > 0)
> min_vruntime += delta;
>
> That would rid us of most of the funny conditionals there.
That still left me with negative min_vruntimes. The
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
> hello rday,
>
> In my view autoconf.h is the index of kernel you are using. By
> reading autoconf.h you will know what Architecture, drivers is
> selected.
>
> For example, If we are using some ARM based board, If you give me
> your autoconf.h , I can
On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
It lived fast, it died young, it didn't leave a pretty corpse...
Something in the startup scripts did a 'touch', and ker-blam.
[ 15.668000] Unable
Am Freitag 21 September 2007 schrieb Jiri Kosina:
> On Fri, 21 Sep 2007, Hans de Goede wrote:
>
> > Thats not what I had in mind, autosuspend doesn't work (presumably
> > because hal keeps polling for media change) maybe I should fix hal to
> > not keep polling for devices which don't have
On Mon, 24 Sep 2007 10:58:08 +0200 (CEST)
"Rodolfo Giometti" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have an LCD panel on a custom PXA27x based board and it must be
> turned on/off by some special commands via a GPIO throught a I2C chip.
>
> I'd like some suggestion about I can easily manage
hello rday,
In my view autoconf.h is the index of kernel you are using. By reading
autoconf.h you will know what Architecture, drivers is selected.
For example, If we are using some ARM based board, If you give me your
autoconf.h , I can replicate same environment as yours. If it is not
properly
On Mon, 24 Sep 2007 12:10:09 +0200 Mike Galbraith <[EMAIL PROTECTED]> wrote:
> @@ -117,7 +117,7 @@ static inline struct task_struct *task_o
> static inline u64
> max_vruntime(u64 min_vruntime, u64 vruntime)
> {
> - if ((vruntime > min_vruntime) ||
> + if (((s64)vruntime >
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
> Hi all,
>
> 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> compare to 2.6.10's autoconf.h .
>
> 2.6.22.7 totally changed the meaning of autoconf.h
... snip ...
why do you care what autoconf.h looks like? it's automatically
Denys Vlasenko wrote:
> On Friday 31 August 2007 16:16, Denys Vlasenko wrote:
>> On Friday 31 August 2007 16:15, Denys Vlasenko wrote:
>>> On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
Attached are three patches which fix that:
textdata bss dec hex
Denys Vlasenko wrote:
> On Friday 31 August 2007 16:15, Denys Vlasenko wrote:
>> On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
>>> Attached are three patches which fix that:
>>>
>>>textdata bss dec hex filename
>>> 261433 500181172 312623 4c52f
>>>
Hi all,
2.6.22.7's include/linux/autoconf.h is completely screwed up as
compare to 2.6.10's autoconf.h .
2.6.22.7 totally changed the meaning of autoconf.h
By just reading autoconf.h of 2.6.10 , we can understand what is the
system and its configuration, it is properly arranged and divided into
Denys Vlasenko wrote:
> On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
>> Attached are three patches which fix that:
>>
>>textdata bss dec hex filename
>> 261433 500181172 312623 4c52f
>> linux-2.6.23-rc1.org.t/drivers/scsi/aic7xxx/built-in.o
>> 199654
On Sun, 2007-09-23 at 23:21 -0700, Tong Li wrote:
> On Sun, 23 Sep 2007, Mike Galbraith wrote:
>
> > On Sat, 2007-09-22 at 12:01 +0200, Mike Galbraith wrote:
> >> On Fri, 2007-09-21 at 20:27 -0700, Tong Li wrote:
> >>> Mike,
> >>>
> >>> Could you try this patch to see if it solves the latency
Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
- New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
things, mainly (Kumar Gala <[EMAIL PROTECTED]>)
Hi Andrew,
The link error for a PowerMac G5 (powerpc) is
Hello,
I have an LCD panel on a custom PXA27x based board and it must be turned
on/off by some special commands via a GPIO throught a I2C chip.
I'd like some suggestion about I can easily manage this situation.
Maybe can I add a special I2C function to get i2c_client pointer and then
using it
static void lock_and_coalesce_cpu_mnt_writer_counts(void)
{
int cpu;
struct mnt_writer *cpu_writer;
for_each_possible_cpu(cpu) {
cpu_writer = _cpu(mnt_writers, cpu);
spin_lock_nested(_writer->lock, 42);
Hello,
I tried to compile the kernel 2.6.9 because I want to use it with
RTLinux and that the only 2.6.x kernel supported. I used gcc 2.95.3 as
recommended.
But I have an error by compilation of process.c :
CC arch/i386/kernel/process.o
{standard input}: Assembler messages:
{standard
Hi Pierre,
> There are currently three working drivers for this new stack:
>
> - sdio_uart: A driver for the standardised GPS and UART interfaces.
> Currently we only know how the GPS system works, so UART is only a
> future possibility.
>
> - libertas_sdio: Support for Marvell's 8686
Jarek Poplawski wrote:
On Thu, Sep 20, 2007 at 03:08:42PM +0200, Nadia Derbey wrote:
Nadia Derbey wrote:
Jarek Poplawski wrote:
On Thu, Sep 20, 2007 at 08:24:58AM +0200, Nadia Derbey wrote:
...
Actually, ipc_lock() is called most of the time without the
ipc_ids.mutex held and without
Hi Vegard,
On Sat, 2007-09-22 at 21:27 +0200, Vegard Nossum wrote:
> After recent discussions on LKML and a general dissatisfaction at the
> current printk() kernel-message logging interface, I've decided to
> write down some of the ideas for a better system.
Good luck :-)
[snip]
> Example: {
Sorry for the long delay, been very busy since I last posted the 386
kernel patches back in July.
Now that I have more free time I remade the patches in a cleaner manner,
broken down into
smaller patches, with fewer #ifdefs all over the place. most #ifdefs are
in the include/asm-i386 headers
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
- New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
things, mainly (Kumar Gala <[EMAIL PROTECTED]>)
Boilerplate:
- See the `hot-fixes' directory for any important updates to this
From: Andrey Mirkin <[EMAIL PROTECTED]>
Right now futexfs and inotifyfs have one magic 0xBAD1DEA, that looks a little
bit confusing.
Use 0xBAD1DEA as magic for futexfs and 0x2BAD1DEA as magic for inotifyfs.
Signed-off-by: Andrey Mirkin <[EMAIL PROTECTED]>
fs/inotify_user.c |4
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we won't get all of memory stuck there.
If this location is too aggressive we might stick it next to
disable_swap_token().
---
Couple RCU and reclaim.
There could be a lot of memory stuck in RCU
This should be accompanied by
addr2 = __START_KERNEL_map + __pa(address);
/* Make sure the kernel mappings stay executable */
prot2 = pte_pgprot(pte_mkexec(pfn_pte(0, prot)));
- err =
On Mon, Sep 24, 2007 at 09:09:48AM +0100, Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
> > > Please kill lib-y while you're at it. It's useless and a constant
> > > source of pain like this.
> > Kernel-bloat is another "constant source of pain".
> > But
The merge window for 2.6.24 should open up any day now, so it's
probably time for me to detail what I intend to cram in there.
This release will probably be one of the biggest ones for the MMC layer
so far. The major pieces are SDIO and SPI support, but there are
several small nuggets as well.
Davide,
On Sun, 2007-09-23 at 15:49 -0700, Davide Libenzi wrote:
> This is the new timerfd API as it is implemented by the following patch:
> ---
> fs/compat.c | 32 ++-
> fs/timerfd.c | 199
> ++-
>
On Mon, 24 Sep 2007 09:09:48 +0100 Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
> > > Please kill lib-y while you're at it. It's useless and a constant
> > > source of pain like this.
> > Kernel-bloat is another "constant source of
>@@ -162,7 +198,7 @@ __change_page_attr(unsigned long address
> /* on x86-64 the direct mapping set at boot is not using 4k pages */
> BUG_ON(PageReserved(kpte_page));
>
>- save_page(kpte_page);
>+ save_page(kpte_page, 0);
> if (page_private(kpte_page) == 0)
>
Jarek Poplawski wrote:
On Fri, Sep 21, 2007 at 01:03:47PM +0200, Jarek Poplawski wrote:
...
I hope not! But, then it would be probably another logical trick:
ipc_rcu_getref/putref() seems to prevent kfreeing of a structure, so
if it's used in do_msgsnd() there should be a risk something can do
On Mon, 24 Sep 2007 11:44:35 +0400, Alexey Dobriyan said:
> Interesting. Here is output from kernel with patch applied and leak
> plugged into proc_dointvec() (I checked twice):
>
> $ grep kcalloc /proc/slab_allocators
> $ grep proc_dointvec /proc/slab_allocators
>
On Mon, Sep 24, 2007 at 09:35:23AM +0200, Peter Zijlstra wrote:
> On Mon, 24 Sep 2007 11:01:10 +0800 Fengguang Wu <[EMAIL PROTECTED]>
> wrote:
>
> > > That is an interesting idea how about this:
> >
> > It looks like a workaround, but it does solve the most important problem.
> > And it is a
On 09/24/2007 09:37 AM, [EMAIL PROTECTED] wrote:
> (Interestingly, I can't find any of the 3 addresses listed in the 'list_add
> corruption' message anywhere *else* in the netconsole output, and the last
> thing
> we hear from before the kersplat is apparently an RCU callback in a softirq?)
Hmm,
On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
> > Please kill lib-y while you're at it. It's useless and a constant
> > source of pain like this.
> Kernel-bloat is another "constant source of pain".
> But the troubles are that increased blot does not result in compiler erros.
>
>
On Sun, 2007-09-23 at 22:52 +0200, Rafael J. Wysocki wrote:
> > > Second, noacpitimer added to the command line makes all of the kernels,
> > > up to
> > > and including 2.6.23-rc6-mm1, boot (this seems to be 100% reproducible).
> >
> > That's valuable information. Can you please provide a boot
On Thu, 20 Sep 2007 10:57:19 -0700 Frank Mayhar <[EMAIL PROTECTED]> wrote:
> Properly support the ru_maxrss field of the rusage structure returned by
> getrusage(). This patch includes documentation both of the getrusage()
> implementation in general and of the ru_maxrss implementation
>
On Mon, Sep 24, 2007 at 08:41:10AM +0100, Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 11:18:26AM +0400, Alexey Dobriyan wrote:
> > Modular puppyvisor started giving linking errors
> >
> > MODPOST 1 modules
> > ERROR: "kasprintf" [drivers/lguest/lg.ko] undefined!
>
> Please kill
On Mon, 24 Sep 2007 11:44:35 +0400, Alexey Dobriyan said:
> On 9/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
> >
> > > -static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
> > > -{
> > > - if (n != 0 && size >
Try this:
1. At one prompt, do "cat".
Now, switch to another prompt and...
2. Do "pstree -p|grep cat" to find out the PID of your cat command. I
get 20502.
3. Do "cat /proc/20502/wchan". I get "0" here.
4. Do "strace -p 20502". I get "read(0, " here.
So wchan says cat is waiting for "0".
[EMAIL PROTECTED] wrote:
> Using kernel 2.6.23-rc7 as xen domU client system I observe a kernel bug
> which occurs reproducibly when calling a shell from midnight commander F2
> context menu or with testcase given below (However most other programs seem
> to
> be well behaved and do not trigger
On 9/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
>
> > -static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
> > -{
> > - if (n != 0 && size > ULONG_MAX / n)
> > - return NULL;
> > - return __kmalloc(n *
On Mon, Sep 24, 2007 at 08:54:07AM +0200, Jarek Poplawski wrote:
> After rethinking, this scenario seems to be wrong or very unprobable
> (I'm not sure of all ways "if (--container...)" could be compiled),
> so there should be no such risk - double kfree/vfree is more probable,
> so no danger.
On Mon, Sep 24, 2007 at 11:18:26AM +0400, Alexey Dobriyan wrote:
> Modular puppyvisor started giving linking errors
>
> MODPOST 1 modules
> ERROR: "kasprintf" [drivers/lguest/lg.ko] undefined!
Please kill lib-y while you're at it. It's useless and a constant
source of pain like
401 - 500 of 1028 matches
Mail list logo
