It is ok to block while holding a mutex, yes?
It's okay, I just didn't try to trace through the code to see if it ever tries
to acquire the same mutex in the thread that needs to signal the event.
- Sean
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Thu, Sep 27, 2007 at 10:46:04AM -0700, Greg KH wrote:
On Thu, Sep 27, 2007 at 04:12:02PM +0200, [EMAIL PROTECTED] wrote:
This test seems to be unnecessary since we always have rootfs mounted before
calling a usermodehelper.
Are you sure this is true? I thought we called the usermode
Warning to Recipient: Action taken by attachment blocking.
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 2007-09-27 at 23:28 +0300, Dmitry Tyschenko wrote:
I have laptop Asus X50M. Using old Debian Etch from February.
Kernel from 2.6.21 doesn't boot, hangs up just in 10seconds - 1minute
after GRUB screen.
I have tryed different versions of gcc (4.1.1, 4.1.2, 4.2.1) to build
2.6.22.8
When a /proc/bus/pci file is written to, the size of that PCI device's
configuration space must be written to the inode. Otherwise, it is
possible for the file to specify a size of 0 on stat if a task is holding
the same file open.
Signed-off-by: David Rientjes [EMAIL PROTECTED]
---
On pci_proc_attach_device(), the size of the PCI configuration space is
stored in the proc_dir_entry as the size of the file. Thus, the procfs
interface to PCI devices should use it instead of the device directly.
Signed-off-by: David Rientjes [EMAIL PROTECTED]
---
drivers/pci/proc.c |4
On Thursday, 27 September 2007 22:28, Dmitry Tyschenko wrote:
Hello,
I have laptop Asus X50M. Using old Debian Etch from February.
Kernel from 2.6.21 doesn't boot, hangs up just in 10seconds - 1minute
after GRUB screen.
I have tryed different versions of gcc (4.1.1, 4.1.2, 4.2.1) to build
On Thu, 27 Sep 2007 09:50:16 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
We don't want to introduce pointless delays in throttle_vm_writeout()
when the writeback limits are not yet exceeded, do we?
Cc: Nick Piggin [EMAIL PROTECTED]
Cc: OGAWA Hirofumi [EMAIL PROTECTED]
Cc: Kumar Gala [EMAIL
On Thursday 27 September 2007 13:51, Peter Jones wrote:
H. Peter Anvin wrote:
Peter Jones wrote:
It should, presumably, depend on ACPI, rather than on X86...?
Actually no. That /should/ be the correct answer, but none of the
hardware vendors actually provide the table via ACPI yet.
If Windows lets you get away with this, then Windows is broken.
memset(ch,'\0',strlen(ch) );
'ch' is uninitialized local data. Nobody knows what evil lurks...
Thay said, the kernel will make sure that any data that gets
put into your address-space doesn't contain anybody else's
information
On Thu, 2007-09-27 at 21:26 +0100, Christoph Hellwig wrote:
Dave will probably find a bandaid to work around this, but the
right fix is to stop using a file struct here entirely. If you
look at reiserfs_xattr_set it's not actually used at all except
for passing it to -prepare_write and
Sorry, I am newbie in linux. Hope you was talking about:
/boot/vmlinuz-2.6.22-1-k7 root=/dev/sda5 ro nohz=off
But it doesn't help for Debians 2.6.22-1 (I don't have another
prebuiled) still same problems.
2007/9/27, Rafael J. Wysocki [EMAIL PROTECTED]:
On Thursday, 27 September 2007 22:28,
On Sep 27 2007 16:53, linux-os (Dick Johnson) wrote:
If Windows lets you get away with this, then Windows is broken.
memset(ch,'\0',strlen(ch) );
No, probably just the chance that the memory to which ch points
had a nul in it or in the near bytes.
Use valgrind, move along.
On Thu, 27 Sep
On Thu, Sep 27, 2007 at 01:53:39PM -0700, Dave Hansen wrote:
-int reiserfs_commit_write(struct file *f, struct page *page,
- unsigned from, unsigned to);
-int reiserfs_prepare_write(struct file *f, struct page *page,
-unsigned from, unsigned to);
Please don't top post.
On Thursday, 27 September 2007 23:01, Dmitry Tyschenko wrote:
Sorry, I am newbie in linux. Hope you was talking about:
/boot/vmlinuz-2.6.22-1-k7 root=/dev/sda5 ro nohz=off
Yes.
But it doesn't help for Debians 2.6.22-1 (I don't have another
prebuiled) still same
The current kswapd (and try_to_free_pages) code has an oddity where the
code will wait on IO, even if there is no IO in flight. This problem is
notable especially when the system scans through many unfreeable pages,
causing unnecessary stalls in the VM.
Signed-off-by: Rik van Riel [EMAIL
On Fri, 2007-09-28 at 00:01 +0300, Dmitry Tyschenko wrote:
Sorry, I am newbie in linux. Hope you was talking about:
/boot/vmlinuz-2.6.22-1-k7 root=/dev/sda5 ro nohz=off
Yes.
But it doesn't help for Debians 2.6.22-1 (I don't have another
prebuiled) still same problems.
Can you please add:
Hello,
A big thanks to everybody who read and replied to my first e-mail; I
have tried my best to incorporate your feedback and suggestions. I
also added some CCs who recently participated in logging-related
discussions.
Changes (since Sept. 22):
* Extensibility - Allowing the compiler to
Hi,
Could you please sent the objdump of the ext4_discard_reservation
function? It doesn't match what I see here.
Thanks,
Mingming
On Thu, 2007-09-27 at 12:31 +0200, [EMAIL PROTECTED]
wrote:
Hi all!
(Please Cc)
kernel 2.6.23-rc6
Debian/sid
kernel ooops:
BUG: unable to handle kernel
On Thu, 27 Sep 2007 12:28:31 -0700
Brett Warden [EMAIL PROTECTED] wrote:
Fixes use of parport_write_control() to match the newer interface that
requires explicit parport_data_reverse() and parport_data_forward()
calls. This eliminates the following error message and restores the
original
On Thu, 2007-09-27 at 22:04 +0100, Christoph Hellwig wrote:
On Thu, Sep 27, 2007 at 01:53:39PM -0700, Dave Hansen wrote:
-int reiserfs_commit_write(struct file *f, struct page *page,
- unsigned from, unsigned to);
-int reiserfs_prepare_write(struct file *f, struct page
Question: do we disable all CPUs except 0 when doing ACPI power off?
Background:
I have a machine here dedicated to running MythTV.
It powers up to record, and then sets the RTC alarm for next time
and powers down again in between recordings.
It has an Intel Core2duo E6300 CPU, currently on an
Mark Lord wrote:
Question: do we disable all CPUs except 0 when doing ACPI power off?
Background:
I have a machine here dedicated to running MythTV.
It powers up to record, and then sets the RTC alarm for next time
and powers down again in between recordings.
It has an Intel Core2duo E6300
2007/9/28, Thomas Gleixner [EMAIL PROTECTED]:
On Fri, 2007-09-28 at 00:01 +0300, Dmitry Tyschenko wrote:
Sorry, I am newbie in linux. Hope you was talking about:
/boot/vmlinuz-2.6.22-1-k7 root=/dev/sda5 ro nohz=off
Yes.
But it doesn't help for Debians 2.6.22-1 (I don't have another
Replace some SPIN_LOCK_UNLOCKED with DEFINE_SPINLOCK
Signed-off-by: Roel Kluin [EMAIL PROTECTED]
---
diff --git a/arch/mips/pci/ops-pmcmsp.c b/arch/mips/pci/ops-pmcmsp.c
index 09fa007..059eade 100644
--- a/arch/mips/pci/ops-pmcmsp.c
+++ b/arch/mips/pci/ops-pmcmsp.c
@@ -206,7 +206,7 @@ static void
On Thu, Sep 27, 2007 at 02:37:42PM -0400, Theodore Tso wrote:
On Thu, Sep 27, 2007 at 10:59:17AM -0700, Greg KH wrote:
Come on now, I'm _very_ tired of this kind of discussion. Please go
read the documentation on how to _use_ sysfs from userspace in such a
way that you can properly access
On Thu, Sep 27, 2007 at 10:39:22PM +0200, Christoph Hellwig wrote:
On Thu, Sep 27, 2007 at 10:46:04AM -0700, Greg KH wrote:
On Thu, Sep 27, 2007 at 04:12:02PM +0200, [EMAIL PROTECTED] wrote:
This test seems to be unnecessary since we always have rootfs mounted
before
calling a
On Thursday, 27 September 2007 23:29, Mark Lord wrote:
Question: do we disable all CPUs except 0 when doing ACPI power off?
No, but we should.
Background:
I have a machine here dedicated to running MythTV.
It powers up to record, and then sets the RTC alarm for next time
and powers down
On Thu, 27 Sep 2007 17:08:16 -0400
Rik van Riel [EMAIL PROTECTED] wrote:
The current kswapd (and try_to_free_pages) code has an oddity where the
code will wait on IO, even if there is no IO in flight. This problem is
notable especially when the system scans through many unfreeable pages,
On Thu, 27 Sep 2007 14:27:14 -0700
Dave Hansen [EMAIL PROTECTED] wrote:
On Thu, 2007-09-27 at 22:04 +0100, Christoph Hellwig wrote:
On Thu, Sep 27, 2007 at 01:53:39PM -0700, Dave Hansen wrote:
-int reiserfs_commit_write(struct file *f, struct page *page,
- unsigned
Kernel 2.6.23-rc8-mm2 on a AMD-64, filesystems mounted are reiserfs,
reiser4 and tmpfs.
netconsole dmesg output and .config are included below.
Near the end of my boot sequence, there is a kernel error. I am not
sure exactly what user-space is doing to make this happen, but I know
that a simple
On Thu, 27 Sep 2007 14:51:25 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Plus, reiserfs seems to compile with that patch I just sent. Sure as
heck surprised me.
That'll be because reiserfs-convert-to-new-aops.patch witched reiserfs over
to -write_begin() and -write_end().
Actually,
Dave Jones wrote:
If memory serves correctly, that was circa 2.6.10, back in these commits..
commit a068ea13d1db406e15c346e93530343f6e70184c
Author: Len Brown [EMAIL PROTECTED]
Date: Sun Oct 10 05:21:08 2004 -0400
[ACPI] If BIOS disabled the LAPIC, believe it by default.
lapic is
On Thu, 2007-09-27 at 14:51 -0700, Andrew Morton wrote:
So your stuff becomes dependent on Nick's stuff, and Nick's stuff is still
failing on NFS, I think.
It worked today, it turned out to be a UML bug. Real hardware seemed to
work properly, but will test a bit more tomorrow.
-
To
On Thu, 27 Sep 2007 14:13:21 +0200 (CEST)
Jiri Kosina [EMAIL PROTECTED] wrote:
i386 and x86_64: randomize brk()
...
--- a/arch/x86_64/ia32/ia32_binfmt.c
+++ b/arch/x86_64/ia32/ia32_binfmt.c
@@ -262,6 +262,7 @@ static void elf32_init(struct pt_regs *);
#define
On Thu, 27 Sep 2007 14:47:02 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 27 Sep 2007 17:08:16 -0400
Rik van Riel [EMAIL PROTECTED] wrote:
The current kswapd (and try_to_free_pages) code has an oddity where the
code will wait on IO, even if there is no IO in flight. This problem
In periodic broadcast mode the next_event member of the broadcast device
structure is set to KTIME_MAX in the interrupt handler. This is wrong,
as we calculate the next periodic interrupt with this variable.
Remove it.
Noticed by Ralf. MIPS is the first user of this mode, it does not affect
On Thu, 27 Sep 2007, Andrew Morton wrote:
+extern void arch_randomize_brk(void);
#include ../../../fs/binfmt_elf.c
Is this sinful extern-decl-in-C acually needed?
Some time passed since I have written the patch, but I remember that this
was needed, otherwise under some circumstances the
As luck would have it, it's not just an obscure Geode system which has a
broken E820 implementation. Today I received a bug report about a Dell
system (XPS M1330) with broken E820.
Unfortunately, the workaround for the Geode breaks this system, because
x86-64 doesn't fall back to the e801/88
On Thu, 27 Sep 2007 18:13:25 -0400
Rik van Riel [EMAIL PROTECTED] wrote:
On Thu, 27 Sep 2007 14:47:02 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 27 Sep 2007 17:08:16 -0400
Rik van Riel [EMAIL PROTECTED] wrote:
The current kswapd (and try_to_free_pages) code has an oddity
On Sep 27, 2007, at 17:34:45, Greg KH wrote:
On Thu, Sep 27, 2007 at 02:37:42PM -0400, Theodore Tso wrote:
That fact that sysfs is all laid out in a directory, but for which
some directories/symlinks are OK to use, and some are NOT OK to
use --- is why I call the sysfs interface an open pit.
On Thu, 2007-09-27 at 10:05 +, Paul Rolland wrote:
Hello,
On Thu, 27 Sep 2007 19:04:11 +1000
Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
Let me guess... this is a T61 or X61 ?
Bad luck ;)
This is an Asus P5W-DH Deluxe motherboard, with a Core2 6400 CPU,
a bunch of disk (2
On Wed, Sep 26, 2007 at 09:02:16AM -0600, Matthew Wilcox wrote:
On Fri, Apr 20, 2007 at 03:47:20PM -0500, Linas Vepstas wrote:
Implement the so-called first failure data capture (FFDC) for the
symbios PCI error recovery. After a PCI error event is reported,
the driver requests that MMIO be
On Thu, Sep 27, 2007 at 05:00:22PM -0500, Linas Vepstas wrote:
On Wed, Sep 26, 2007 at 09:02:16AM -0600, Matthew Wilcox wrote:
I'm a little concerned by the mention of MMIO. It's entirely possible
for the sym2 driver to be using ioports to access the card rather than
MMIO. Is it simply
On Thursday 27 September 2007, you wrote:
Then you don't have to change every single printk in the kernel, but
only those that don't currently come with a log level. More importantly,
you can do the conversion without a flag day, by spreading (an empty)
PRINTK_CONTINUED in places that do
Jordan Crouse wrote:
I copied in a 2.6.22 kernel to see that it really did work, and it did.
But here's the crazy part - I did a dmesg, and it looks like it
*is* using e820 data, and it looks complete (I see the entire map -
including the ACPI and reserved blocks way up high).
So
Torsten Kaiser wrote:
Known good is for me 2.6.23-rc3-mm1, the first known bad is 2.6.23-rc4-mm1.
I will try to look at the diff between these revisions some more, but
the change in sata_sil24.c looked like a perfect match for the
symptoms I was seeing.
I think the first thing to do here is
On Thu, Sep 27, 2007 at 06:27:48PM -0400, Kyle Moffett wrote:
On Sep 27, 2007, at 17:34:45, Greg KH wrote:
On Thu, Sep 27, 2007 at 02:37:42PM -0400, Theodore Tso wrote:
That fact that sysfs is all laid out in a directory, but for which some
directories/symlinks are OK to use, and some are NOT
On Thu, Sep 27, 2007 at 02:34:45PM -0700, Greg KH wrote:
Ok, how then should I advertise this better? What can we do better to
help userspace programmers out in this regard?
Would you accept a patch which causes the deprecated sysfs
files/directories to disappear, even if CONFIG_SYS_DEPRECATED
On 27/09/07 15:47 -0700, H. Peter Anvin wrote:
Jordan Crouse wrote:
Breaks on the Geode - original behavior.
I think that having boot_prams.e820_entries != 0 makes the kernel
assume the e820 data is correct.
Okay, now I'm utterly baffled how 2.6.22 ever worked on this Geode,
On Thursday 27 September 2007 2:00:36 am Arnd Bergmann wrote:
#define KERN_NOTICE 5,
#define PRINTK_CONTINUED ,
#define printk(level, str, ...) \
do { \
if (sizeof(level) == 1) /* continued printk */\
actual_printk(str, __VA_ARGS__); \
else if ((level[1] - '0')
Hi Cornelia,
Yet another report, once again while putting rfcomm system under load.
Several USB adapters, several links.
Is this a regression or does it happen with 2.6.22 too?
I've not tested with 2.6.22, but have done it a few days ago with
2.6.21-2-486 (stock debian
Jordan Crouse wrote:
On 27/09/07 15:47 -0700, H. Peter Anvin wrote:
Jordan Crouse wrote:
Breaks on the Geode - original behavior.
I think that having boot_prams.e820_entries != 0 makes the kernel
assume the e820 data is correct.
Okay, now I'm utterly baffled how 2.6.22 ever worked on this
On Thu, Sep 27, 2007 at 07:19:27PM -0400, Theodore Tso wrote:
Would you accept a patch which causes the deprecated sysfs
files/directories to disappear, even if CONFIG_SYS_DEPRECATED is
defined, via a boot-time parameter?
How about a mount option? That way people can test without a reboot:
On Thu, 27 Sep 2007 15:21:21 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Nope, sc.nr_io_pages will also be incremented when the code runs into
pages that are already PageWriteback.
yup, I didn't think of that. Hopefully someone else will be in there
working on that zone too. If this
Jordan Crouse wrote:
Breaks on the Geode - original behavior.
I think that having boot_prams.e820_entries != 0 makes the kernel
assume the e820 data is correct.
Okay, now I'm utterly baffled how 2.6.22 ever worked on this Geode,
because this, to the best of my reading, mimics the 2.6.22
On Thu, 27 Sep 2007 18:50:27 -0400
Rik van Riel [EMAIL PROTECTED] wrote:
On Thu, 27 Sep 2007 15:21:21 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Nope, sc.nr_io_pages will also be incremented when the code runs into
pages that are already PageWriteback.
yup, I didn't think of
On 27/09/07 15:17 -0700, H. Peter Anvin wrote:
As luck would have it, it's not just an obscure Geode system which has a
broken E820 implementation. Today I received a bug report about a Dell
system (XPS M1330) with broken E820.
Unfortunately, the workaround for the Geode breaks this system,
On Sep 25, 2007, at 18:50:05, Greg KH wrote:
On Thu, Sep 20, 2007 at 05:31:37PM +0900, Tejun Heo wrote:
* Name-formatting for symlinks. e.g. symlink pointing to /dira/
dirb/leaf can be named as symlink:%1-%0 and it will show up as
symlink:dirb-leaf. This only applies when new interface is
This patch removes some ARRAY_SIZE macro duplicates. There is also one in
arch/um/include/user.h, which isn't fixed here because comments in that file
explicitly state a preference for the 'less fancy' version. If that's the
case as well for any of the other replacements please comment.
Rafael J. Wysocki wrote:
On Thursday, 27 September 2007 23:29, Mark Lord wrote:
Question: do we disable all CPUs except 0 when doing ACPI power off?
No, but we should.
Background:
I have a machine here dedicated to running MythTV.
It powers up to record, and then sets the RTC alarm for
On Thu, 27 Sep 2007 15:59:07 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
And lost the changelog ;)
Good point.
The current kswapd (and try_to_free_pages) code has an oddity where the
code will wait on IO, even if there is no IO in flight. This problem is
notable especially when the system
Alan Cox wrote:
I think there have been enough cases where this draining was necessary.
IIRC, ata_piix was involved in those cases, right? If so, can you
please submit a patch which applies this only to affected controllers?
I don't feel too confident about applying this to all SFF
On 27/09/07 16:27 -0700, H. Peter Anvin wrote:
Jordan Crouse wrote:
On 27/09/07 15:47 -0700, H. Peter Anvin wrote:
Jordan Crouse wrote:
Breaks on the Geode - original behavior.
I think that having boot_prams.e820_entries != 0 makes the kernel
assume the e820 data is correct.
Okay,
On Thu, Sep 27, 2007 at 04:10:31PM -0600, Matthew Wilcox wrote:
In the error handler, we wait_for_completion(io_reset_wait).
In sym2_io_error_detected, we init_completion(io_reset_wait).
Isn't it possible that we hit the error handler before we hit the
io_error_detected path, and thus the
Jordan Crouse wrote:
Oh bugger, looks like this one might be genuinely my fault after all.
The ID check in the new code is buggy.
Can you please test this revised patch out (against current -git)?
That looks the same as the previous patch you sent?
Sorry, this is the right one...
On Thu, Sep 27, 2007 at 11:18:44AM +0200, Michal Schmidt wrote:
Hello,
HP ProLiant systems DL385 G2 and DL585 G2 need pci=bfsort to enumerate PCI
devices in the expected order.
(John, can you please confirm and ACK this?)
As a shameless plug, biosdevname is a userspace app I wrote to help
On Wed, Sep 26, 2007 at 12:49:50AM -0600, Grant Grundler wrote:
[edited out several points that I think have been already
addresed by others in this thread.]
Defining it terms of completion queues won't mean much to most folks.
Better to add a description of completion queues to the
Example: {
struct kprint_block out;
kprint_block_init(out, KPRINT_DEBUG);
kprint_block(out, Stack trace:);
while(unwind_stack()) {
kprint_block(out, %p %s, address, symbol);
}
kprint_block_flush(out);
}
Assuming that kprint_block_flush()
On Thu, Sep 27, 2007 at 11:16:10AM -0400, Rik van Riel wrote:
On Thu, 27 Sep 2007 09:50:16 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
We don't want to introduce pointless delays in throttle_vm_writeout()
when the writeback limits are not yet exceeded, do we?
Good catch.
Thank you.
Use the dma_flags_set_dmabarrier() interface to allow a dmabarrier
attribute to be associated with user-allocated memory. (For now,
it's only implemented for mthca.)
Signed-off-by: Arthur Kepner [EMAIL PROTECTED]
---
drivers/infiniband/core/umem.c |7 +--
Document dma_flags_set_dmabarrier().
Signed-off-by: Arthur Kepner [EMAIL PROTECTED]
---
DMA-API.txt | 26 ++
1 files changed, 26 insertions(+)
diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.txt
index cc7a8c3..5fc0bba 100644
---
define dma_flags_set_dmabarrier() for sn-ia64 - it borrows
bits from the direction argument (renamed flags) to the
dma_map_* routines to pass an additional dmabarrier attribute.
Also define routines to retrieve the original direction and
attribute from flags.
Signed-off-by: Arthur Kepner [EMAIL
Introduce the dma_flags_set_dmabarrier() interface and give it
a default no-op implementation.
Signed-off-by: Arthur Kepner [EMAIL PROTECTED]
---
dma-mapping.h |6 ++
1 files changed, 6 insertions(+)
diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
index
On Altix, DMA may be reordered between a device and host memory.
This reordering can happen in the NUMA interconnect, and it usually
results in correct operation and improved performance. In some
situations it may be necessary to explicitly synchronize DMA from
the device.
This patchset
Bill Davidsen wrote:
It seems there are (at least) two parts to this, one regarding
changing working directory which is clearly stated in the standards
and must work as it does, and the various issues regarding getting out
of the chroot after the cwd has entered that changed root. That second
On Thu, Sep 27, 2007 at 05:28:57PM -0600, Matthew Wilcox wrote:
On Thu, Sep 27, 2007 at 07:19:27PM -0400, Theodore Tso wrote:
Would you accept a patch which causes the deprecated sysfs
files/directories to disappear, even if CONFIG_SYS_DEPRECATED is
defined, via a boot-time parameter?
On Thu, Sep 27, 2007 at 04:53:40PM -0700, Andrew Morton wrote:
Still wanna know why it is safe for uml_net_rx to be playing with
drop_skb when update_drop_skb() could be concurrently reallocating
and freeing it.
Ah, yes, I missed that point in the horror of my botch last night.
I'll add
On Thursday, September 27, 2007 7:05:31 pm Dave Airlie wrote:
Hi Linus,
The attached patch is to fix a bug reported on 965gm chipsets (lots of new
laptops), I think distros will all have to patch this in to fix it, so can
we get it into the 2.6.23 final?
(Otherwise I'll wait until stable..)
Jeff Garzik wrote:
Tejun Heo wrote:
Alan Cox wrote:
I think there have been enough cases where this draining was necessary.
IIRC, ata_piix was involved in those cases, right? If so, can you
please submit a patch which applies this only to affected controllers?
I don't feel too confident
On Thu, Sep 27 2007, Theodore Tso wrote:
On Thu, Sep 27, 2007 at 04:19:12PM +0100, Alan Cox wrote:
Well it's not my call, just seems like a really bad idea to change the
error value. You can't claim full coverage for such testing anyway, it's
one of those things that people will complain
Tejun Heo wrote:
Alan Cox wrote:
I think there have been enough cases where this draining was necessary.
IIRC, ata_piix was involved in those cases, right? If so, can you
please submit a patch which applies this only to affected controllers?
I don't feel too confident about applying this to
On Fri, 28 Sep 2007 01:05:12 +0530
Dhaval Giani [EMAIL PROTECTED] wrote:
On Thu, Sep 27, 2007 at 12:00:33PM -0700, Randy Dunlap wrote:
On Thu, 27 Sep 2007 23:34:15 +0530 Dhaval Giani wrote:
+config RESOURCE_COUNTERS
+ bool Resource counters
+ help
+ This option enables
On Thu, Sep 27 2007, Alan D. Brunelle wrote:
[PATCH] Some IO scheduler cleanup in Documentation/block
[snip]
Thanks Alan, applied.
--
Jens Axboe
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, 27 Sep 2007 13:01:26 -0400
Jeff Dike [EMAIL PROTECTED] wrote:
+static int update_drop_skb(int max)
+{
+ struct sk_buff *new;
+ int err = 0;
+
+ spin_lock(drop_lock);
+
+ if (max = drop_max)
+ goto out;
+
+ err = -ENOMEM;
+ new =
On 27/09/07 16:36 -0700, H. Peter Anvin wrote:
Jordan Crouse wrote:
Oh bugger, looks like this one might be genuinely my fault after all.
The ID check in the new code is buggy.
Can you please test this revised patch out (against current -git)?
That looks the same as the previous
On Thu, Sep 27, 2007 at 01:17:39PM -0700, Mark Gross wrote:
Updated qos PM parameter patch:
Note: the replacing of latency.c with this is a separate patch.
this patch attempts to address the issues raised so far.
[snip]
+static int register_new_qos_misc(struct qos_object *qos)
+{
+
Jordan Crouse wrote:
Worked, but that just raises more questions. Why didn't more x86 boxes
break or, alternatively, why did a new version of the BIOS fix the problem?
I guess we shouldn't look a gift horse in the mouth. Or something.
Why didn't more x86 boxes break... well, it's pretty
On Tue, Sep 25, 2007 at 10:13:33PM -0700, Randy Dunlap wrote:
On Tue, 25 Sep 2007 17:00:57 -0700 [EMAIL PROTECTED] wrote:
..
1. Function signature should be on one line if possible (and it is).
Aw crud, I looked at dma-mapping.h and it uses this format sometimes.
Well, it's undesirable,
Hi Linus,
The attached patch is to fix a bug reported on 965gm chipsets (lots of new
laptops), I think distros will all have to patch this in to fix it, so can
we get it into the 2.6.23 final?
(Otherwise I'll wait until stable..)
Dave.From 14e53712e5e2ccc72dac1131de78e590e9a9d451 Mon Sep
Uniprocessor Althlon 64, 64-bit kernel, 2G ECC RAM,
2.6.23-rc8 + linuxpps (5.0.0) + ip1000a driver.
(patch from http://marc.info/?l=linux-netdevm=118980588419882)
After a few hours of operation, ntp loses the ability to send packets.
sendto() returns -EAGAIN to everything, including the 24-byte
Greg KH wrote:
On Thu, Sep 27, 2007 at 03:22:35AM -0400, Jeff Garzik wrote:
Greg KH wrote:
On Wed, Sep 26, 2007 at 11:40:58PM +0200, Brice Goglin wrote:
Greg KH wrote:
Here's a summary of the current state of the Linux PCI subsystem, as of
2.6.23-rc8.
If the information in here is
On Thu, Sep 27, 2007 at 09:18:50PM -0400, Jeff Garzik wrote:
Greg KH wrote:
On Thu, Sep 27, 2007 at 03:22:35AM -0400, Jeff Garzik wrote:
Greg KH wrote:
On Wed, Sep 26, 2007 at 11:40:58PM +0200, Brice Goglin wrote:
Greg KH wrote:
Here's a summary of the current state of the Linux PCI
Hi !
Just a little question in the light of the discussion we had at Kernel
Summit about merging drivers upstream (and here, I strongly agree with
Linus, hence my message).
I just got that new T61 laptop which happens to have an iwl4xxx chip.
The distro I installed on it (ubuntu) has a driver
On Thu, Sep 27, 2007 at 05:28:57PM -0600, Matthew Wilcox wrote:
On Thu, Sep 27, 2007 at 07:19:27PM -0400, Theodore Tso wrote:
Would you accept a patch which causes the deprecated sysfs
files/directories to disappear, even if CONFIG_SYS_DEPRECATED is
defined, via a boot-time parameter?
On Thu, 2007-09-27 at 22:30 -0400, John W. Linville wrote:
It doesn't seem to pull any depedency nor affect any other external
piece of code unless I'm missing something, so it's a perfect
example of
what we've been discussing back then: there is just no point not
merging
it at any time
Well, pulling in iwlwifi would require also pulling in the mac80211
subsystem, so it's not quite that simple (although I'm not sure what's
holding back that going into the kernel.)
I though that was already in 2.6.23 ... my bad if I missed something
(there is definitely something there
On Fri, Sep 28, 2007 at 11:39:27AM +1000, Benjamin Herrenschmidt wrote:
Just a little question in the light of the discussion we had at Kernel
Summit about merging drivers upstream (and here, I strongly agree with
Linus, hence my message).
You must not have been watching me SPAM netdev for
On Fri, Sep 28, 2007 at 11:39:27AM +1000, Benjamin Herrenschmidt wrote:
Just a little question in the light of the discussion we had at Kernel
Summit about merging drivers upstream (and here, I strongly agree with
Linus, hence my message).
I just got that new T61 laptop which happens to
On Thu, Sep 27, 2007 at 05:17:44PM +0200, Jan Engelhardt wrote:
On Sep 27 2007 12:41, mahamuni ashish wrote:
I have small code
This is not a kernel problem. (Read your C book and/or ask in
a C newsgroup.)
Please goto comp.lang.c for help. ;)
--
Bill, look, we understand that you're
601 - 700 of 714 matches
Mail list logo