On Sun, Apr 22, 2007 at 02:41:48PM +1000, Con Kolivas wrote:
> A significant bugfix for SMP balancing was just posted for the staircase
> deadline cpu scheduler which improves behaviour dramatically on any SMP
> machine.
>
> Thanks to Willy Tarreau for noticing likely fault point.
>
> Also requ
On 4/21/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>> And how the hell do you imagine you'd even *know* what thread holds the
>> futex?
On Sat, Apr 21, 2007 at 06:46:58PM -0700, Ulrich Drepper wrote:
> We know this in most cases. This is information recorded, for
> instance, in the mutex data
> > The MNT_USER flag is not copied on any kind of mount cloning:
> > namespace creation, binding or propagation.
>
> I half agree, and as an initial approximation this works.
> Ultimately we should be at the point that for mount propagation
> that we copy the owner of the from the owner of our pa
> I suspect we can allow MNT_FORCE for non-privileged users
> as well if we can trust the filesystem.
I don't think so. MNT_FORCE has side effects on the superblock. So a
user shouldn't be able to force an unmount on a bind mount s/he did,
but there's no problem with allowing plain/lazy unm
On Sun, Apr 22, 2007 at 12:10:33AM +0200, Andi Kleen wrote:
> > unwind code to even attempt to avoid the problem what should be done?
> > How about:
> >
> > (1) Make it clear the Fault Injection with STACKTRACE on x86_64 is at
> > best "Russian Roulette" -- maybe a !X86_64 in Kconfig.debug?
> >
>
Miklos Szeredi <[EMAIL PROTECTED]> writes:
> Does this mean, that containers will need this? Or that you don't
> know yet?
The uid namespace is something we have to handle carefully and we
have not decided on the final design.
What is clear is that all permission checks will need to become
eith
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > Add sysctl variables for accounting and limiting the number of user
> > mounts.
> >
> > The maximum number of user mounts is set to 1024 by default. This
> > won't in itself enable user mounts, setting a mount to be owned by a
> > user is first
On 4/22/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
I'm just looking for what people want the API to be here. With that in
hand we can just go out and do whatever needs to be done.
I think a sched_yield_to is one interface:
int sched_yield_to(pid_t);
For futex(), the extension is n
On Sat, 21 Apr 2007 13:07:16 +0200 Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> On Sat, 2007-04-21 at 02:55 -0700, Andrew Morton wrote:
> > On Fri, 20 Apr 2007 17:52:02 +0200 Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> >
> > > Count per BDI writeback pages.
> > >
> > > Signed-off-by: Peter Zijlst
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > Allow bind mounts to unprivileged users if the following conditions
> > are met:
> >
> > - mountpoint is not a symlink or special file
>
> Why? This sounds like a left over from when we were checking permissions.
Hmm, yes. Don't know. Mayb
> > + /*
> > +* For unprivileged mounts use current uid/gid. Still allow
> > +* "user_id" and "group_id" options for compatibility, but
> > +* only if they match these values.
> > +*/
> > + if (!capable(CAP_SYS_ADMIN)) {
> > + d->user_id = current->uid;
> > +
On Sat, 21 Apr 2007 14:01:36 +0200 Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> On Sat, 2007-04-21 at 02:55 -0700, Andrew Morton wrote:
>
> > > +
> > > + __mod_bdi_stat64(bdi, BDI_WRITEOUT, -half);
> > > + bdi->cycles += cycle;
> > > + }
> > > + bdi->cycles = global_cycle;
> > > + s
On Sunday 22 April 2007 17:00, Willy Tarreau wrote:
> On Sun, Apr 22, 2007 at 02:41:48PM +1000, Con Kolivas wrote:
> > A significant bugfix for SMP balancing was just posted for the staircase
> > deadline cpu scheduler which improves behaviour dramatically on any SMP
> > machine.
> >
> > Thanks to
On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> On Sunday 22 April 2007 17:00, Willy Tarreau wrote:
> > On Sun, Apr 22, 2007 at 02:41:48PM +1000, Con Kolivas wrote:
> > > A significant bugfix for SMP balancing was just posted for the
> > > staircase deadline cpu scheduler which improves behavio
> > Does this mean, that containers will need this? Or that you don't
> > know yet?
>
> The uid namespace is something we have to handle carefully and we
> have not decided on the final design.
>
> What is clear is that all permission checks will need to become
> either (uid namspace, uid) tuple
Jens Axboe wrote:
Thanks for testing Brad, be sure to use the next patch I sent instead.
The one from this mail shouldn't even get you booted. So double check
that you are still using CFQ :-)
[184901.576773] BUG: unable to handle kernel NULL pointer dereference at
virtual address 005c
[1
On Sat, Apr 21, 2007 at 12:20:45AM -0700, Andrew Morton wrote:
> On Thu, 19 Apr 2007 09:19:32 +0200 Borislav Petkov <[EMAIL PROTECTED]> wrote:
>
> we already did this in the top-level Makefile. It's in $(KERNELVERSION)
> and is printed by `make kernelversion'.
>
> Cannot we use that info somehow?
Miklos Szeredi <[EMAIL PROTECTED]> writes:
>> > The MNT_USER flag is not copied on any kind of mount cloning:
>> > namespace creation, binding or propagation.
>>
>> I half agree, and as an initial approximation this works.
>> Ultimately we should be at the point that for mount propagation
>> that
Sorry about the wrong whitespaces again :), here's a correct one
-
From: Borislav Petkov <[EMAIL PROTECTED]>
This patch shuts warnings of the sort:
make -C /mnt/samsung_200/sam/kernel/trees/21-rc6/build \
KBUILD_SRC=/mnt/samsung_200/sam/kernel/trees/21-rc6 \
KBUILD_EXTMOD=""
On Sun, 2007-04-22 at 02:32 +0200, Arnd Bergmann wrote:
> I just saw that we already have an option like that, with a slightly different
> name.
>
> arch/s390/Kconfig contains
>
> config NO_IOMEM
> def_bool y
>
> and lib/Kconfig contains
>
> config HAS_IOMEM
> boolean
>
Miklos Szeredi <[EMAIL PROTECTED]> writes:
>> > From: Miklos Szeredi <[EMAIL PROTECTED]>
>> >
>> > Add sysctl variables for accounting and limiting the number of user
>> > mounts.
>> >
>> > The maximum number of user mounts is set to 1024 by default. This
>> > won't in itself enable user mounts,
On Sun, 2007-04-22 at 01:19 +0200, Arnd Bergmann wrote:
> > diff -urpN linux-2.6/drivers/ssb/Kconfig
> > linux-2.6-patched/drivers/ssb/Kconfig
> > --- linux-2.6/drivers/ssb/Kconfig 2007-04-19 15:24:40.0 +0200
> > +++ linux-2.6-patched/drivers/ssb/Kconfig 2007-04-19
> > 15:55:4
On Sun, 2007-04-22 at 01:15 +0200, Arnd Bergmann wrote:
> > @@ -81,6 +82,7 @@ config VT_HW_CONSOLE_BINDING
> >
> > config SERIAL_NONSTANDARD
> > bool "Non-standard serial port support"
> > + depends on !S390
> > ---help---
> > Say Y here if you have any non-standard serial boards
Hi Con,
I now have 2.6.21-rc7-sd-0.45 running on my Intel Core2 T7600 2.33
machine and there is something I don't understand.
For testing I have a Perl script that does some numbercrunching
and runs a couple of hours.
I have two scenarios
a) start the job via loops in a shellscript
b) start the
Hello list,
this is an old issue, I reported it to
http://bugzilla.kernel.org/show_bug.cgi?id=5410 in 2005, but it still
bothers me. My mouse light (simple Logitech USB mouse) still stays on
after shutdown with 2.6.21-rc7.
But, headway has been made (a little). It turned out that I don't have
On Sun, Apr 22, 2007 at 05:31:58PM +1000, Con Kolivas wrote:
> On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> > On Sunday 22 April 2007 17:00, Willy Tarreau wrote:
> > > On Sun, Apr 22, 2007 at 02:41:48PM +1000, Con Kolivas wrote:
> > > > A significant bugfix for SMP balancing was just posted
On Tue, 17 Apr 2007 23:59:10 GMT Linux Kernel Mailing List
wrote:
> Gitweb:
> http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1714f9bfc92d6ee67e84127332a1fae27772acfe
> Commit: 1714f9bfc92d6ee67e84127332a1fae27772acfe
> Parent: 08269c6d38e003adb12f55c
On Sun, 2007-04-22 at 01:10 +0200, Arnd Bergmann wrote:
> > --- linux-2.6/drivers/dma/Kconfig 2007-04-19 15:24:33.0 +0200
> > +++ linux-2.6-patched/drivers/dma/Kconfig 2007-04-19 15:49:55.0
> > +0200
> > @@ -3,6 +3,7 @@
> > #
> >
> > menu "DMA Engine support"
> > + depend
> >> > +if (mnt->mnt_flags & MNT_USER)
> >> > +seq_printf(m, ",user=%i", mnt->mnt_uid);
> >> How about making the test "if (mnt->mnt_user != &root_user)"
> >
> > We don't want to treat root_user special. That's what capabilities
> > were invented for.
>
> For the print sta
On Sat, Apr 21, 2007 at 02:17:02PM -0400, Gene Heskett wrote:
> CFS-v4 is quite smooth in terms of the users experience but after prolonged
> observations approaching 24 hours, it appears to choke the cpu hog off a bit
> even when the system has nothing else to do. My amanda runs went from 1 to
> >> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >> >
> >> > Add sysctl variables for accounting and limiting the number of user
> >> > mounts.
> >> >
> >> > The maximum number of user mounts is set to 1024 by default. This
> >> > won't in itself enable user mounts, setting a mount to be owned by
On Tue, 17 Apr 2007 03:15:51 -0400 Rik van Riel <[EMAIL PROTECTED]> wrote:
> Make it possible for applications to have the kernel free memory
> lazily. This reduces a repeated free/malloc cycle from freeing
> pages and allocating them, to just marking them freeable. If the
> application wants to
> > On Apr 21 2007 10:57, Eric W. Biederman wrote:
> >>
> >>> tmpfs!
> >>
> >>tmpfs is a possible problem because it can consume lots of ram/swap.
> >>Which is why it has limits on the amount of space it can consume.
> >
> > Users can gobble up all RAM and swap already today. (Unless they are
> >
> i'm pleased to announce release -v4 of the CFS patchset. The patch
> against v2.6.21-rc7 can be downloaded from:
>
> http://redhat.com/~mingo/cfs-scheduler/
I can't get 2.6.21-rc7-CFS-v4 to boot. Immediately after selecting
this kernel I see a very fast scrolling (loop?) sequence of addrs
On Sun, 22 Apr 2007 10:39:41 +0200 Bastian Blank <[EMAIL PROTECTED]> wrote:
> The commit 34f5a39899f3f3e815da64f48ddb72942d86c366 restricted reading
> of the tainted value. The attached patch changes this back to a
> write-only check and restores the read behaviour of older versions.
>
> Signed-o
On Sunday 22 April 2007 18:06, Willy Tarreau wrote:
> On Sun, Apr 22, 2007 at 05:31:58PM +1000, Con Kolivas wrote:
> > On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> > > On Sunday 22 April 2007 17:00, Willy Tarreau wrote:
> > > > On Sun, Apr 22, 2007 at 02:41:48PM +1000, Con Kolivas wrote:
> >
On 4/22/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
>> I'm just looking for what people want the API to be here. With that in
>> hand we can just go out and do whatever needs to be done.
On Sun, Apr 22, 2007 at 12:17:31AM -0700, Ulrich Drepper wrote:
> I think a sched_yield_to is one inte
On Sun, Apr 22, 2007 at 01:50:45AM -0700, Andrew Morton wrote:
> On Sun, 22 Apr 2007 10:39:41 +0200 Bastian Blank <[EMAIL PROTECTED]> wrote:
>
> > The commit 34f5a39899f3f3e815da64f48ddb72942d86c366 restricted reading
> > of the tainted value. The attached patch changes this back to a
> > write-on
On Sun, 2007-04-22 at 00:19 -0700, Andrew Morton wrote:
> It could be that we never call test_clear_page_writeback() against
> !bdi_cap_writeback_dirty() pages anwyay. I can't think why we would, but
> the relationships there aren't very clear. Does "don't account for dirty
> memory" imply "does
On Sat, Apr 21, 2007 at 09:04:06PM +0200, Andreas Gruenbacher wrote:
> > It is unspecified whether all members of the statvfs structure have
> > meaningful values on all file systems.
>
> In my opinion, the advantage of not reporting bogus pathnames in /proc/mounts
> by far outweighs the problems
The commit 34f5a39899f3f3e815da64f48ddb72942d86c366 restricted reading
of the tainted value. The attached patch changes this back to a
write-only check and restores the read behaviour of older versions.
Signed-off-by: Bastian Blank <[EMAIL PROTECTED]>
--
The joys of love made her human and the a
Disable stacktrace filter support for x86-64 for now.
Will be enable when we can get the dwarf2 unwinder back.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
lib/Kconfig.debug |1 +
1 file changed, 1 insertion(+)
Index: 2.6-git/lib/Kconfig.debug
Currently failslab injects failures into cache_alloc().
But with enabling CONFIG_NUMA it's not enough to let actual
slab allocator functions (kmalloc, kmem_cache_alloc, ...) return NULL.
This patch moves fault injection hook inside of __cache_alloc() and
__cache_alloc_node(). These are lower c
On Sun, Apr 22, 2007 at 01:18:10AM -0700, Andrew Morton wrote:
> On Tue, 17 Apr 2007 03:15:51 -0400 Rik van Riel <[EMAIL PROTECTED]> wrote:
>
> > Make it possible for applications to have the kernel free memory
> > lazily. This reduces a repeated free/malloc cycle from freeing
> > pages and alloc
Add maintainer for fault injection support.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
MAINTAINERS |5 +
1 file changed, 5 insertions(+)
Index: 2.6-git/MAINTAINERS
===
--- 2.6-git.orig/MAINTAINERS
+++ 2.6-git/MAINT
On Sun, Apr 22, 2007 at 06:53:58PM +1000, Con Kolivas wrote:
> On Sunday 22 April 2007 18:06, Willy Tarreau wrote:
> > On Sun, Apr 22, 2007 at 05:31:58PM +1000, Con Kolivas wrote:
> > > On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> > > > On Sunday 22 April 2007 17:00, Willy Tarreau wrote:
> >
On Sat, Apr 21, 2007 at 02:06:22PM -0700, Andrew Morton wrote:
> On Sat, 21 Apr 2007 22:01:47 +0100 Alan Cox <[EMAIL PROTECTED]> wrote:
>
> > > > +#define lower_32_bits(n) (sizeof(n) == 8 ? (u32)(n) : (n))
> > >
> > > n&0x would be simpler.
> > >
> > > Do we actually have any call for th
KVM shadow page tables are always in pae mode, regardless of the guest
setting. This means that a guest pde (mapping 4MB of memory) is mapped
to two shadow pdes (mapping 2MB each).
When the guest writes to a pte or pde, we intercept the write and emulate it.
We also remove any shadowed mappings c
PAGE_MASK is an unsigned long, so using it to mask physical addresses on
i386 (which are 64-bit wide) leads to truncation. This can result in
page->private of unrelated memory pages being modified, with disasterous
results.
Fix by not using PAGE_MASK for physical addresses; instead calculate
the
On Sunday 22 April 2007 09:53, Martin Schwidefsky wrote:
> On Sun, 2007-04-22 at 01:19 +0200, Arnd Bergmann wrote:
> > > diff -urpN linux-2.6/drivers/ssb/Kconfig
> > > linux-2.6-patched/drivers/ssb/Kconfig
> > > --- linux-2.6/drivers/ssb/Kconfig 2007-04-19 15:24:40.0
> > > +0200
> >
On Sunday 22 April 2007 19:14, Willy Tarreau wrote:
> On Sun, Apr 22, 2007 at 06:53:58PM +1000, Con Kolivas wrote:
> > On Sunday 22 April 2007 18:06, Willy Tarreau wrote:
> > > On Sun, Apr 22, 2007 at 05:31:58PM +1000, Con Kolivas wrote:
> > > > On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> >
So after a cheerful five hours making all the new crap with which they have
inflicted me actually compile, first up is powerpc:
initcall 0xc06dc650: .scsi_complete_async_scans+0x0/0x1dc() returned 0.
initcall 0xc06dc650 ran for 0 msecs:
.scsi_complete_async_scans+0x0/0x1dc()
Call
Hi all,
Back to 2.4... I've just released Linux 2.4.35-pre3.
We're getting closer to 2.4.35. It is in good shape, and the major
change I was most afraid of (e1000 driver update) works like a charm.
Kudos to intel people on this one !
I will still have to see whether the skge/sky2 drivers are sta
I've just released Linux 2.4.34.3.
Nothing critical, just a bunch of bugfixes and small security fix.
The patch and changelog will appear soon at the following locations:
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/patch-2.4.34.3.bz2
ftp://ftp.kern
On 4/22/07, oliver pinter <[EMAIL PROTECTED]> wrote:
Hello
I have ASUS P4C800, P4 3GHz HT (Nortwood), 512RAM and I have nothing errors
in my cpu.
in bios have you HT option enabled
Sure, and the hardware is fine as other kernels and other systems (as
WinXP) work fine.
or im =<2.6.21-rc7 fu
Andrew Morton wrote:
> On Sat, 21 Apr 2007 11:26:31 -0400 Jeff Mahoney <[EMAIL PROTECTED]> wrote:
>
>> The listxattr() and getxattr() operations are only protected by a read
>> lock. As a result, if either of these operations run in parallel, a race
>> condition exists where the xattr_root will
irq values are u32, not u8. Large irq numbers will be truncated,
free_irq may free a different irq.
Remove incorrectly sized struct member and use the one from pci_dev.
Signed-off-by: Olaf Hering <[EMAIL PROTECTED]>
---
drivers/serial/icom.c |5 ++---
drivers/serial/icom.h |1 -
2 files
On Sunday 22 April 2007 18:02, Michael Gerdau wrote:
> Hi Con,
>
> I now have 2.6.21-rc7-sd-0.45 running on my Intel Core2 T7600 2.33
> machine and there is something I don't understand.
>
> For testing I have a Perl script that does some numbercrunching
> and runs a couple of hours.
>
> I have two
On Sunday 22 April 2007, William Lee Irwin III wrote:
>On Sat, Apr 21, 2007 at 02:17:02PM -0400, Gene Heskett wrote:
>> CFS-v4 is quite smooth in terms of the users experience but after
>> prolonged observations approaching 24 hours, it appears to choke the cpu
>> hog off a bit even when the system
Hi Ogawa :)
* OGAWA Hirofumi <[EMAIL PROTECTED]> dixit:
> DervishD <[EMAIL PROTECTED]> writes:
> > A mount option to force walking the FAT and getting the real
> > info could be interesting. That way, it will be only done for
> > certain devices (small disks, for example).
>
> Yes. It seems
On Sunday 22 April 2007 20:48, Martin Steigerwald wrote:
> Am Montag 09 April 2007 schrieb Mike Galbraith:
> > On Mon, 2007-04-09 at 07:26 -0400, Ed Tomlinson wrote:
> > > On Monday 09 April 2007 01:38, Mike Galbraith wrote:
> > > > On Sun, 2007-04-08 at 09:08 -0400, Ed Tomlinson wrote:
> > > > > H
Am Montag 09 April 2007 schrieb Mike Galbraith:
> On Mon, 2007-04-09 at 07:26 -0400, Ed Tomlinson wrote:
> > On Monday 09 April 2007 01:38, Mike Galbraith wrote:
> > > On Sun, 2007-04-08 at 09:08 -0400, Ed Tomlinson wrote:
> > > > Hi,
> > > >
> > > > I am one of those who have been happily testing
Hi Ogawa (and Andrew) :)
* OGAWA Hirofumi <[EMAIL PROTECTED]> dixit:
> Andrew Morton <[EMAIL PROTECTED]> writes:
> > Is there some way in which we can work out what's happened and fix
> > it up?
>
> It seems that the recent Windows changed specification, and it's
> undocumented. Windows doesn
Hi,
On Sunday 22 April 2007 00:42, OGAWA Hirofumi wrote:
> Yes. It seems that Windows does not update the ->free_clusters correctly.
> Probably, I think the option is good for now. What do you think about
> an attached patch?
Please don't ask me, because I'm not a filesystem expert. Sorry. My sug
On Sunday 22 April 2007 19:14, Willy Tarreau wrote:
> On Sun, Apr 22, 2007 at 06:53:58PM +1000, Con Kolivas wrote:
> > On Sunday 22 April 2007 18:06, Willy Tarreau wrote:
> > > On Sun, Apr 22, 2007 at 05:31:58PM +1000, Con Kolivas wrote:
> > > > On Sunday 22 April 2007 17:27, Con Kolivas wrote:
> >
DervishD <[EMAIL PROTECTED]> writes:
> The problem is that if a program writes a file onto the filesystem
> without using statfs first to check for free space, the free_clusters
> entry won't have the real value and the driver may report "disk full" (I
> haven't read the code for the vfat driv
On Thu, Apr 19, 2007 at 12:55:29AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> kthread_run replaces the kernel_thread and daemonize calls
> during thread startup.
>
> Calls to signal_pending were also removed as it is currently
> impossible for th
On Thu, Apr 19, 2007 at 12:55:30AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> kthread_run replaces kernel_thread and dameonize.
>
> allow_signal is unnecessary and has been removed.
> tid_poll was unused and has been removed.
Thread handling in t
On Thu, Apr 19, 2007 at 12:55:31AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> This patch changes cpqphp to use kthread_run and not
> kernel_thread and daemonize to startup and setup
> the cpqphp thread.
Thread handling in this driver (and actually
>
> The created a warning storm:
Hmm, yes good idea to fix that. Probably for x86-64 too.
>
> I worry rather a lot about how well runtime tested this very late change
> was,
I tested it with oprofile and checked the nmi watchdog.
> and whether it works correctly even with this fix applied.
Hi,
> Finally, tifm_sd module needs to be manually inserted.
By the way, the driver emits custom uevent when the new card is detected. I was
going to look at
this some day in the future, but if you want to mess a little with hotplug
scripts the issue can
be easily solved.
It would be nice i
Looks like you were missing at least the pcie hotplug driver. Another
one of the horrible thread abuses in drivers/pci/hotpug.
- full conversion to kthread infrastructure
- use wake_up_process to wake the thread up
Like most pci hotplug drivers it still uses very race non-atomic variable
assig
On Sunday 22 April 2007 21:42, Con Kolivas wrote:
Willy I'm still investigating the idle time and fluctuating load as a separate
issue. Is it possible the multiple ocbench processes are naturally
synchronising and desynchronising and choosing to sleep and/or run at the
same time? I can remove t
Am 22.04.2007 00:10 schrieb David Miller:
> From: Alan Cox <[EMAIL PROTECTED]>
> Date: Sat, 21 Apr 2007 21:58:44 +0100
>
>> On Sat, 21 Apr 2007 15:07:51 +0200
>> Tilman Schmidt <[EMAIL PROTECTED]> wrote:
>>
>>> From: Tilman Schmidt <[EMAIL PROTECTED]>
>>>
>>> The "obsolete" label on the ISDN_I4L K
On Thu, Apr 19, 2007 at 12:55:28AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> thread_run is used intead of kernel_thread, daemonize, and mucking
> around blocking signals directly.
This is the full conversion I sent to Dave in April 2006, but neve
On Thu, Apr 19, 2007 at 01:58:45AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]>
>
> This patch modifies the startup of eehd to use kthread_run
> not a combination of kernel_thread and daemonize. Making
> the code slightly simpler and more maintainable.
This one h
On Thu, Apr 19, 2007 at 01:58:46AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]>
>
> This patch modifies the startup of rtasd to use kthread_run instaed of
> a combination of kernel_thread and daemonize. Making the code a little
> simpler and more maintainble.
Loo
On Sun, Apr 22, 2007 at 01:38:23PM +0100, Alan Cox wrote:
> > > > over-engineering. Call it sector_upper32() do it the simple way and stop
> > > > trying to solve a problem we don't have
> > >
> > > James said we have the same problem with dma_addr_t.
> >
> > Yes. It's in fact the far more commo
> > > over-engineering. Call it sector_upper32() do it the simple way and stop
> > > trying to solve a problem we don't have
> >
> > James said we have the same problem with dma_addr_t.
>
> Yes. It's in fact the far more common case and we have a bread of
> macros dealing with the issue in vario
Hi,
I just wondered if the below type of crash was a known thing, and if
there are any obvious things I can do to prevent/fix it ?
BUG: spinlock bad magic on CPU#0, kswapd0/242 (Not tainted)
lock: c06c9380, .magic: c06c9380, .owner:
[] _raw_spin_lock+0x1a/0xd9
[] _spin_lock_irqsave+0x9/0xd
[] __
On 4/22/07, oliver pinter <[EMAIL PROTECTED]> wrote:
I have CC the kernel
Did you?
and the result is:
your'e config : failed smp
your'e config + power managment : ok
Interesting, can anyone tell me why does not SMP work without Power
Managment? Should it be that way?
--
Miguel Ojeda
htt
Just to throw another possibly-overlooked variable into the mess:
My system here is using the on-demand cpufreq policy governor.
I wonder how that interacts with the various schedulers here?
I suppose for the "make" kernel case, after a couple of seconds
the cpufreq would hit max and stay there
> >> If it isn't obsolete then fix the code to use the newer APIs
>
> Why should that be a precondition for removing the incorrect
> "obsolete" label?
Because if we remove the obsolete label the users are going to be
suprised when it goes away entirely with && BROKEN or && !HOTPLUG or
similar.
>
On 4/19/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
On 4/19/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Dmitry Torokhov napsal(a):
> > If we are interested in using FF API we need to come up with a way
> > to express this effect without exposing implementation details of
> > one particular dev
On Sunday 22 April 2007 22:54, Mark Lord wrote:
> Just to throw another possibly-overlooked variable into the mess:
>
> My system here is using the on-demand cpufreq policy governor.
> I wonder how that interacts with the various schedulers here?
>
> I suppose for the "make" kernel case, after a co
On Sun, 2007-04-22 at 13:24 +0100, Christoph Hellwig wrote:
> This is the full conversion I sent to Dave in April 2006, but never
> got any feedback to:
Sorry about that; I need prodding sometimes. I'll provide some now...
Can you show me why the thread won't now miss a wakeup if it goes to
slee
Con Kolivas wrote:
Oh I definitely was not advocating against renicing X, I just suspect that
virtually all the users who gave glowing reports to CFS comparing it to SD
had no idea it had reniced X to -19 behind their back and that they were
comparing it to SD running X at nice 0.
I really
Bodo Eggert <[EMAIL PROTECTED]> writes:
> Windows _does_ care*, it will pretend the disk to be full.
Did you test on 2000 or XP? (e.g. write 0 to free_clusters, then
create new file.)
> - usefree is a bad name (I'd suggest recalc_free instead),
Is it about nofree option?
> and your description
On 4/22/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Opcode 0xb0 is "WIN_SMART".
Error 0x04 is "command aborted/rejected/unsupported".
Something on your system is issuing S.M.A.R.T. commands from userspace
to the drive, and the drive either (1) doesn't support S.M.A.R.T.,
or (2) currently does not
Am 22.04.2007 14:58 schrieb Alan Cox:
If it isn't obsolete then fix the code to use the newer APIs
>> Why should that be a precondition for removing the incorrect
>> "obsolete" label?
>
> Because if we remove the obsolete label the users are going to be
> suprised when it goes away entirely w
OGAWA Hirofumi <[EMAIL PROTECTED]> writes:
>> - You forgot to update Documentation/
>
> Sure. If you can post the patch, it'll be great.
Updated patch is here.
Thanks.
--
OGAWA Hirofumi <[EMAIL PROTECTED]>
It seems that the recent Windows changed specification, and it's
undocumented. Windows
> Anyway the more important part is... Can you test this patch please? Dump
> all the other patches I sent you post 045. Michael, if you could test too
> please?
Have it up running for 40 minutes now and my perljobs show a constant
cpu utilization of 100/50/50 in top most of the time. When the 100
The task load_weight needs to be set every time the quota is set and wasn't
being set in activate_task which assumed it would not have changed. Due to
changes in where the default rr_interval is set on SMP this assumption
failed. Also if one were to change rr_interval on the fly it would break
agai
On 4/22/07, Len Brown <[EMAIL PROTECTED]> wrote:
This is an AML run-time error from a PCI Interrupt Link
trying to find its "Present Resource Settings" --
ie. the current IRQ for a programmable IRQ.
Please open up a bug report here:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
Yep, r
On Sun, Apr 22, 2007 at 10:18:32PM +1000, Con Kolivas wrote:
> On Sunday 22 April 2007 21:42, Con Kolivas wrote:
>
> Willy I'm still investigating the idle time and fluctuating load as a
> separate
> issue. Is it possible the multiple ocbench processes are naturally
> synchronising and desynchr
Andreas Schwab <[EMAIL PROTECTED]> writes:
> OGAWA Hirofumi <[EMAIL PROTECTED]> writes:
>
>> diff -puN
>> Documentation/filesystems/vfat.txt~fat_dont-use_free_clusters-for-fat32
>> Documentation/filesystems/vfat.txt
>> ---
>> linux-2.6/Documentation/filesystems/vfat.txt~fat_dont-use_free_cluste
On 4/22/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
(added linux-acpi)
Are any other problems observeable due to this?
This issue I did observe with 2.6.20.7 & 2.6.21-rc7. Should I try anymore tests?
Anyway, here is the dmesg of 2.6.21-rc7:-
Linux version 2.6.21-rc7-Akula2 ([EMAIL PROTECTE
OGAWA Hirofumi <[EMAIL PROTECTED]> wrote:
>> * Juergen Beisert <[EMAIL PROTECTED]> dixit:
>>> So the last free sector count is also stored. When mounting this
>>> filesystem you don't need to walk through the whole FAT to calculate
>>> the available space, you can use this "cached" value instead
On Fri, 20 Apr 2007, Alan Cox wrote:
> I'm looking for some testers for a revamp of the initio driver. No real
> code changes other than to hopefully stop it exploding on load on 64bit,
> but a major reorganisation, commenting and "de-windowsification" so the
> code is actually readable and I can
Ingo Molnar wrote:
* Jan Engelhardt <[EMAIL PROTECTED]> wrote:
i've attached it below in a standalone form, feel free to put it
into SD! :)
Assume X went crazy (lacking any statistics, I make the unproven
statement that this happens more often than kthreads going berserk),
then having it nice
1 - 100 of 285 matches
Mail list logo
