"Roy Huang" <[EMAIL PROTECTED]> writes:
> A patch provide a interface to limit total page cache in
> /proc/sys/vm/pagecache_ratio. The default value is 90 percent. Any
> feedback is appreciated.
Anything except a default value of 100% will change the behavior
and probably reduce the performance o
On 18 Jan 2007, Greg KH wrote:
> > Since 2.6.19, I get the following Oops once a day, always with the same
> > process, newspipe[1] which use a lot of CPU, threads and I/O.
> > ...
> Can you reproduce it without the grsec patch applied?
I'm compiling a new kernel and will try it soon!
--
Nicola
"Rajat Jain" <[EMAIL PROTECTED]> writes:
>> >
>> > Is there any way volunteers like me can help in this exercise?
>>
>> See the /APIchanges in the Kernel Janitors TODO list
>> http://kernelnewbies.org/KernelJanitors/Todo
>>
>
> Hi,
>
> This is regarding the link posted above.
>
> 1) How do I make
* Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 17, 2007 at 10:04:53AM +0100, Pierre Peiffer wrote:
> > Hi,
> >
> > This latest patch is an adaptation of the sys_futex64 syscall
> > provided in -rt patch (originally written by Ingo). It allows the
> > use of 64bit futex.
>
> Big
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> This fix is mostly from Thomas ..
>
> The problem was that a futex can be called with a zero timeout (0
> seconds, 0 nanoseconds) and it's a valid expired timeout. However, the
> current futex in -rt assumes a zero timeout is an infinite timeout.
>
* Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> > I'll be happy to move this over to the utrace setting, once it is
> > merged. Do you think it would be better to include the current
> > version of kwatch now or to wait for utrace?
> >
> > Roland, is there a schedule for when you plan to get
Vivek Goyal <[EMAIL PROTECTED]> writes:
>> Hi Eric,
>>
>> In physical destination mode, the destination APIC is determined by
>> APIC ID and in logical destination mode, destination apics are determined
>> by the configurations based on LDR and DFR registers in APIC (Depending
>> on Flat mode or
On Wed, 2007-01-17 at 16:25 -0800, Daniel Walker wrote:
> The patch reworks do_futex, and futex_wait* so a NULL pointer in the timeout
> position is infinite, and anything else is evaluated as a real timeout.
>
> Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
Ack.
tglx
-
To unsubscri
On Wed, Jan 17, 2007 at 04:55:49PM -0600, Dave Kleikamp wrote:
...
> diff -Nurp linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h linux/fs/jfs/jfs_lock.h
> --- linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h2006-11-29 15:57:37.0
> -0600
> +++ linux/fs/jfs/jfs_lock.h 2007-01-17 15:30:19.0 -0600
>
--- Randy Dunlap <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Jan 2007 04:10:17 + (GMT) Seetharam
> Dharmosoth wrote:
>
> (please don't top-post)
>
>
> > Generally sysrq will work with serial console
> right?
> >
> > suppose system is connected through serial port to
> the
> > other system, (i
>
> Is there any way volunteers like me can help in this exercise?
See the /APIchanges in the Kernel Janitors TODO list
http://kernelnewbies.org/KernelJanitors/Todo
Hi,
This is regarding the link posted above.
1) How do I make sure if some one is NOT working on any of the
mentioned bullet po
On Wed, 17 Jan 2007, Andrew Morton wrote:
> > The problem there is that we do a GFP_ATOMIC allocation (no allocation
> > context) that may fail when the first page is dirtied. We must therefore
> > be able to subsequently allocate the nodemask_t in set_page_dirty().
> > Otherwise the first fail
On Thu, Jan 18, 2007 at 09:45:04AM +0530, Daniel Rodrick wrote:
> Hi list,
>
> Whenever there is a change in the kernel API (or a new API is
> introduced), all of the drivers that use the older API need to be
> changed (or recommended to be changed). I believe it is the
> responsibility of the per
On Thu, Jan 18, 2007 at 09:45:04AM +0530, Daniel Rodrick wrote:
> Hi list,
>
> Whenever there is a change in the kernel API (or a new API is
> introduced), all of the drivers that use the older API need to be
> changed (or recommended to be changed). I believe it is the
> responsibility of the per
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> On 01/17, Eric W. Biederman wrote:
>>
>> Cedric Le Goater <[EMAIL PROTECTED]> writes:
>> >
>> > your first analysis was correct : exit_task_namespaces() should be moved
>> > above exit_notify(tsk). It will require some extra fixes for nsproxy
>> > thou
On Thu, Jan 18, 2007 at 09:11:53AM +0530, Vivek Goyal wrote:
> On Wed, Jan 17, 2007 at 12:08:48PM -0700, Eric W. Biederman wrote:
> > Benjamin Romer <[EMAIL PROTECTED]> writes:
> >
> > > On the Unisys ES7000/ONE system, we encountered a problem where
> > > performing a kexec reboot or dump on any c
On Thu, 18 Jan 2007 04:10:17 + (GMT) Seetharam Dharmosoth wrote:
(please don't top-post)
> Generally sysrq will work with serial console right?
>
> suppose system is connected through serial port to the
> other system, (ie serial console), at this time we can
> fire some set of commands thr
The call to aio_advance_iovec() in aio_rw_vect_retry() becomes problematic
when it comes to pipe and socket operations which internally modify/advance
the iovec themselves. As a result AIO writes to sockets fail to return
the correct result.
I'm not sure what the best way to fix this is. One opt
Hi Grant !
On Thu, Jan 18, 2007 at 11:09:57AM +1100, Grant Coady wrote:
(...)
> > } else {
> >-mnt->file_mode = mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
> >-S_IROTH | S_IXOTH | S_IFREG;
> >-mnt->dir_mode = mnt->dir_mode =
Hi list,
Whenever there is a change in the kernel API (or a new API is
introduced), all of the drivers that use the older API need to be
changed (or recommended to be changed). I believe it is the
responsibility of the person changing the kernel API, to change all
the drivers that have found thei
Generally sysrq will work with serial console right?
suppose system is connected through serial port to the
other system, (ie serial console), at this time we can
fire some set of commands through the serial console.
the sequesnce is as follows
do ctrl+]
send brk
then some commands
What is my
On Wed, Jan 17, 2007 at 12:08:48PM -0700, Eric W. Biederman wrote:
> Benjamin Romer <[EMAIL PROTECTED]> writes:
>
> > On the Unisys ES7000/ONE system, we encountered a problem where
> > performing a kexec reboot or dump on any cell other than cell 0 causes
> > the system timer to stop working, res
On Wed, Jan 17, 2007 at 07:23:52PM -0700, Matthew Wilcox wrote:
> On Wed, Jan 17, 2007 at 04:53:45PM -0800, Greg KH wrote:
> > I'm trying to clean up all the usages of struct class_device to use
> > struct device, and I ran into the pci_bus code. Right now you create a
> > symlink called "bridge"
On Thu, 2007-01-18 at 10:46 +1100, Jens Axboe wrote:
> On Wed, Jan 17 2007, Dave Kleikamp wrote:
> > On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote:
> >
> > > Can you try io_schedule() and verify that things just work?
> >
> > I actually did do that in the first place, but wondered if it was t
Here is the newest patch against 2.6.20-rc5.
==
From ad9ca9a32bdcaddce9988afbf0187bfd04685a0c Mon Sep 17 00:00:00 2001
From: Aubrey.Li <[EMAIL PROTECTED]>
Date: Thu, 18 Jan 2007 11:08:31 +0800
Subject: [PATCH] Add an interface to limit total vf
On Wed, Jan 17, 2007 at 04:53:45PM -0800, Greg KH wrote:
> I'm trying to clean up all the usages of struct class_device to use
> struct device, and I ran into the pci_bus code. Right now you create a
> symlink called "bridge" under the /sys/class/pci_bus/:XX/ directory
> to the pci device that
On Wed, Jan 17 2007, Chris Frost wrote:
> We are working on a kernel module which uses the linux block device
> interface as part of a larger project, are seeing unexpected block
> write behavior from our usage of the noop scheduler, and were
> wondering whether anyone might have feedback on what t
On Tuesday 16 January 2007 00:38, you wrote:
> As always with these things, the devil is in the details. It requires
> the device to support a ->prepare_flush() queue hook, and not all
> devices do that. It will work for IDE/SATA/SCSI, though. In some devices
> you don't want/need to do a real disk
We are working on a kernel module which uses the linux block device
interface as part of a larger project, are seeing unexpected block write
behavior from our usage of the noop scheduler, and were wondering whether
anyone might have feedback on what the behavior we see?
We would like to send block
> On Wed, 17 Jan 2007 17:10:25 -0800 (PST) Christoph Lameter <[EMAIL
> PROTECTED]> wrote:
> On Wed, 17 Jan 2007, Andrew Morton wrote:
>
> > > The inode lock is not taken when the page is dirtied.
> >
> > The inode_lock is taken when the address_space's first page is dirtied. It
> > is
> > also
Harald Dunkel wrote:
> How comes that there is no such problem if I connect the drive
> via an USB SATA adapter?
Ah... right. I forgot about that. Scrap my analysis. What happens is
really weird tho.
> Do you think it would be reasonable to send a bug report to Samsung,
> and see what they say
On Wed, 17 Jan 2007, Andrew Morton wrote:
> > The inode lock is not taken when the page is dirtied.
>
> The inode_lock is taken when the address_space's first page is dirtied. It is
> also taken when the address_space's last dirty page is cleaned. So the place
> where the inode is added to and
Hi Matt,
I'm trying to clean up all the usages of struct class_device to use
struct device, and I ran into the pci_bus code. Right now you create a
symlink called "bridge" under the /sys/class/pci_bus/:XX/ directory
to the pci device that is the bridge.
This is messy to try to convert to str
This fix is mostly from Thomas ..
The problem was that a futex can be called with a zero timeout (0 seconds,
0 nanoseconds) and it's a valid expired timeout. However, the current futex
in -rt assumes a zero timeout is an infinite timeout.
Kevin Hilman found this using LTP's nptl01 test case whi
On Wed, Jan 17, 2007 at 10:04:53AM +0100, Pierre Peiffer wrote:
> Hi,
>
> This latest patch is an adaptation of the sys_futex64 syscall provided in
> -rt
> patch (originally written by Ingo). It allows the use of 64bit futex.
Big NACK here, we don't need yet another goddamn multiplexer. Please
On Wed, Jan 17, 2007 at 11:09:21AM +0100, Turbo Fredriksson wrote:
> Quoting Ken Moffat <[EMAIL PROTECTED]>:
>
> > Certainly, fdisk from util-linux doesn't know about mac disks, and
> > I thought the same was true for cfdisk and sfdisk. Many years ago
> > there was mac-fdisk, I think also known
On Wed, Jan 17, 2007 at 11:17:37AM -0500, Alan Stern wrote:
> I'll be happy to move this over to the utrace setting, once it is merged.
> Do you think it would be better to include the current version of kwatch
> now or to wait for utrace?
>
> Roland, is there a schedule for when you plan to ge
Should apply to -mm tree or current libata-dev git tree. This version
leaves out part of a change in the first version which in retrospect
should have been left alone.
---
This cleans up a few issues with the error handling in sata_nv in ADMA
mode to make it more consistent with other NCQ-capabl
from: Kevin Lloyd <[EMAIL PROTECTED]>
This patch ensures that the device is turned on when inserted into the system.
It also adds more VID/PIDs and matches the N_OUT_URB with the airprime driver.
Signed-off-by: Kevin Lloyd <[EMAIL PROTECTED]>
---
--- linux-2.6.20-rc5/drivers/usb/serial/sierr
I'm trying to do a SYSRQ over a serial console. As I understand it a
break will do that, but I'm not seeing the SYSRQ. In looking at
uart_handle_break() in drivers/serial/8250.c it looks like the code will
toggle port->sysrq, rather than just setting it when the port is a
console. I think the co
Adam Kropelin wrote:
Allen Parker wrote:
Allen Parker wrote:
From what I've been able to gather, other Intel Pro/1000 chipsets
work fine in 2.6.20-rc5. If the e1000 guys need any assistance
testing, I'll be more than happy to volunteer myself as a guinea pig
for patches.
I wasn't aware that
On Wed, Jan 17 2007, Dave Kleikamp wrote:
> On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote:
>
> > Can you try io_schedule() and verify that things just work?
>
> I actually did do that in the first place, but wondered if it was the
> right thing to introduce the accounting changes that came
On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote:
> Can you try io_schedule() and verify that things just work?
I actually did do that in the first place, but wondered if it was the
right thing to introduce the accounting changes that came with that.
I'll change it back to io_schedule() and te
On Wed, Jan 17, 2007 at 11:21:59AM +0100, Nicolas Bareil wrote:
>
> Hello,
>
> Since 2.6.19, I get the following Oops once a day, always with the same
> process, newspipe[1] which use a lot of CPU, threads and I/O.
>
> The kernel is patched by Grsecurity. The ext3 filesystem is on a
> software R
> Allen Parker wrote:
>> Allen Parker wrote:
>>> From what I've been able to gather, other Intel Pro/1000 chipsets
>>> work fine in 2.6.20-rc5. If the e1000 guys need any assistance
>>> testing, I'll be more than happy to volunteer myself as a guinea pig
>>> for patches.
>>
>> I wasn't aware t
On Wed, 17 Jan 2007, Benjamin LaHaise wrote:
On Mon, Jan 15, 2007 at 08:25:15PM -0800, Nate Diller wrote:
the right thing to do from a design perspective. Hopefully it enables
a new architecture that can reduce context switches in I/O completion,
and reduce overhead. That's the real motive ;)
On Wed, Jan 17 2007, Dave Kleikamp wrote:
> Jens,
> Can you please take a look at this patch, and if you think it's sane,
> add it to your explicit i/o plugging patchset? Would it make sense in
> any of these paths to use io_schedule() instead of schedule()?
I'm glad you bring that up, actually.
> --- linux-2.6-git.orig/fs/inode.c 2007-01-12 08:03:47.0 +0100
> +++ linux-2.6-git/fs/inode.c 2007-01-12 08:53:26.0 +0100
> @@ -81,6 +81,7 @@ static struct hlist_head *inode_hashtabl
> * the i_state of an inode while it is in use..
> */
> DEFINE_SPINLOCK(inode_lock);
> +E
On Wed, 17 Jan 2007, [EMAIL PROTECTED] wrote:
> On Wed, 17 Jan 2007 17:04:20 EST, "Robert P. J. Day" said:
>
> > > How much of the 'OBSOLETE' code should just be labelled 'BROKEN'
> > > instead?
> >
> > the stuff that's actually "broken." :-)
>
> Right - the question is how much code qualifies as
On Wed, Jan 17, 2007 at 04:35:02PM -0600, Miller, Mike (OS Dev) wrote:
> > On Wed, Jan 17, 2007 at 10:43:14AM -0600, Miller, Mike (OS Dev) wrote:
> > > Hello,
> > > We've been seeing some nasty data corruption issues on some
> > platforms.
> > > We've been capturing PCI-E traces looking for someth
On 01/17, Eric W. Biederman wrote:
>
> Cedric Le Goater <[EMAIL PROTECTED]> writes:
> >
> > your first analysis was correct : exit_task_namespaces() should be moved
> > above exit_notify(tsk). It will require some extra fixes for nsproxy
> > though.
>
> I think the only issue is the child_reaper
Jens,
Can you please take a look at this patch, and if you think it's sane,
add it to your explicit i/o plugging patchset? Would it make sense in
any of these paths to use io_schedule() instead of schedule()?
I hadn't looked at your patchset until I discovered that jfs was easy to
hang in the -mm
On Wed, 17 Jan 2007 17:04:20 EST, "Robert P. J. Day" said:
> > How much of the 'OBSOLETE' code should just be labelled 'BROKEN'
> > instead?
>
> the stuff that's actually "broken." :-)
Right - the question is how much code qualifies as either/both, and which
we should use when we encounter the
Next to EXPERIMENTAL, add two new kernel config categories of
DEPRECATED and OBSOLETE.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
speak now or forever ... too late.
diff --git a/init/Kconfig b/init/Kconfig
index a3f83e2..433dd30 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@
On Wed, 2007-01-17 at 15:30 -0700, Eric W. Biederman wrote:
> Cedric Le Goater <[EMAIL PROTECTED]> writes:
> >
> > your first analysis was correct : exit_task_namespaces() should be moved
> > above exit_notify(tsk). It will require some extra fixes for nsproxy
> > though.
>
> I think the only is
On Tue, 16 Jan 2007, Arjan van de Ven wrote:
> On Tue, 2007-01-16 at 21:26 +0100, Bodo Eggert wrote:
> > Helge Hafting <[EMAIL PROTECTED]> wrote:
> > > Michael Tokarev wrote:
> > >> But seriously - what about just disallowing non-O_DIRECT opens together
> > >> with O_DIRECT ones ?
> > >>
> > >
greg k-h wrote:
> On Wed, Jan 17, 2007 at 10:43:14AM -0600, Miller, Mike (OS Dev) wrote:
> > Hello,
> > We've been seeing some nasty data corruption issues on some
> platforms.
> > We've been capturing PCI-E traces looking for something
> nasty but we
> > haven't found anything yet. One of the
Cedric Le Goater <[EMAIL PROTECTED]> writes:
>
> your first analysis was correct : exit_task_namespaces() should be moved
> above exit_notify(tsk). It will require some extra fixes for nsproxy
> though.
I think the only issue is the child_reaper and currently we only have one of
those. When we
> On Wed, 17 Jan 2007 11:43:42 -0800 (PST) Christoph Lameter <[EMAIL
> PROTECTED]> wrote:
> On Tue, 16 Jan 2007, Andrew Morton wrote:
>
> > Do what blockdevs do: limit the number of in-flight requests (Peter's
> > recent patch seems to be doing that for us) (perhaps only when PF_MEMALLOC
> > is i
> On Wed, 17 Jan 2007 16:09:41 -0500 [EMAIL PROTECTED] wrote:
> commit d8238afa7eedc047b57da7ec98e98fb051fc4e85
> Author: Chris Leech <[EMAIL PROTECTED]>
> Date: Fri Nov 17 11:37:29 2006 -0800
>
> I/OAT: Add documentation for the tcp_dma_copybreak sysctl
>
> Signed-off-by: Chris Leech <
> We've just verified that configuring the graphics aperture to be
> write-combining instead of write-back using an MTRR also solves the
> problem. It appears to be a cache incoherency issue in the graphics
> aperture.
Interesting.
Unfortunately it is also not correct. It was intentional to
m
Trond Myklebust <[EMAIL PROTECTED]> writes:
> On Sat, 2007-01-13 at 23:57 +0100, [EMAIL PROTECTED] wrote:
>> Hi there,
>>
>> I've been curious enough to try 2.6.20-rc5 with nfs4/kerberos.
>> It was working fine before. I was using 2.6.18.1 on the client and
>> 2.6.20-rc3-git4 on server and today
Sridhar Samudrala a écrit :
> I think the following patch
>
> [IPV6] MCAST: Fix joining all-node multicast group on device initialization.
> http://www.spinics.net/lists/netdev/msg22663.html
>
> that went in after 2.6.20-rc5 should fix this problem.
>
Yep that fixes the problem. Thanks a lot.
Hello,
here is a patch for ehca_uverbs.c with the following changes:
- Rename mm_open/close() to ehca_mm_open/close() respectively
- Refactor ehca_mmap() into sub-functions ehca_mmap_cq/qp(),
which then call the new common sub-functions ehca_mmap_fw()
and ehca_mmap_queue() to register firmware memo
On Wed, 17 Jan 2007, H. Peter Anvin wrote:
> DEPRECATED should presumably default to Y; OBSOLETE to n.
crap, now i see what you were getting at -- i forgot to assign
defaults. i'll resubmit, but i'll wait for anyone to suggest any
better help content if they have a better idea.
rday
-
To unsubs
On Wed, 17 Jan 2007, H. Peter Anvin wrote:
> DEPRECATED should presumably default to Y; OBSOLETE to n.
you presume correctly.
rday
-
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.or
On Wed, 17 Jan 2007, [EMAIL PROTECTED] wrote:
> On Wed, 17 Jan 2007 11:51:27 EST, "Robert P. J. Day" said:
> >
> > in any event, what about introducing a new config variable,
> > OBSOLETE, under "Code maturity level options"? this would seem to be
> > a quick and dirty way to prune anything tha
On Mon, Jan 15, 2007 at 05:33:28PM -0800, Kevin Lloyd wrote:
> from: Kevin Lloyd <[EMAIL PROTECTED]>
>
> This patch ensures that the device is turned on when inserted into the
> system (which mostly affects the EM5725 and MC5720. It also adds more
> VID/PIDs and matches the N_OUT_URB with the ai
Robert P. J. Day wrote:
To go along with the EXPERIMENTAL kernel config status, introduce
two new states: DEPRECATED and OBSOLETE.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
just adding these config variables to init/Kconfig shouldn't affect
the current build status, but it w
Robert P. J. Day wrote:
To go along with the EXPERIMENTAL kernel config status, introduce
two new states: DEPRECATED and OBSOLETE.
I think this is a very good idea. If nothing else, it gives some
middle-of-the-roadness to the continual "to remove or not to remove" debate.
-hpa
-
Hello Santiago,
On Wed, Jan 17, 2007 at 11:00:30AM +0100, Santiago Garcia Mantinan wrote:
> Hi!
>
> I have discovered a problem with the changes applied to smbfs in 2.4.34 and
> in the security backports like last Debian's 2.4 kernel update these changes
> seem to be made to solve CVE-2006-5871 a
On Wed, 2007-01-17 at 22:52 +0100, Peter Zijlstra wrote:
> >
> > > Index: linux-2.6-git/fs/inode.c
> > > ===
> > > --- linux-2.6-git.orig/fs/inode.c 2007-01-12 08:03:47.0 +0100
> > > +++ linux-2.6-git/fs/inode.c 2007-01-
On Wed, 17 Jan 2007 11:51:27 EST, "Robert P. J. Day" said:
>
> in any event, what about introducing a new config variable,
> OBSOLETE, under "Code maturity level options"? this would seem to be
> a quick and dirty way to prune anything that is *supposed* to be
> obsolete from the build, to make
On Wed, 2007-01-17 at 12:05 -0800, Christoph Lameter wrote:
> On Tue, 16 Jan 2007, Peter Zijlstra wrote:
>
> > The current NFS client congestion logic is severely broken, it marks the
> > backing device congested during each nfs_writepages() call and implements
> > its own waitqueue.
>
> This is
On Mon, Jan 15, 2007 at 08:25:15PM -0800, Nate Diller wrote:
> the right thing to do from a design perspective. Hopefully it enables
> a new architecture that can reduce context switches in I/O completion,
> and reduce overhead. That's the real motive ;)
And it's a broken motive. Context switch
On Wed, Jan 17, 2007 at 05:04:45PM +0100, =?UTF-8?Q? taps ?= wrote:
> Hello,
>
> I got this text when I boot my linux :
>
> --cut--
>
> PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
> PCI quirk: region 1180-11bf claimed by ICH4 GPIO
> PCI: Ignoring BAR0-3 of IDE controller :00:1f
Hi Tejun,
Tejun Heo wrote:
>
> Okay, I just tested a number of dvds on x86-64 and x86. The error
> pattern is really interesting. It doesn't matter whether you're on
> x86-64 or x86, 2.6.18 or 2.6.20-rc5. The problem occurs when a dvd
> which doesn't match dvd's region mask is played.
>
> MMC
On Wed, Jan 17, 2007 at 10:43:14AM -0600, Miller, Mike (OS Dev) wrote:
> Hello,
> We've been seeing some nasty data corruption issues on some platforms.
> We've been capturing PCI-E traces looking for something nasty but we
> haven't found anything yet. One of the hardware guys if asking if there
>
To go along with the EXPERIMENTAL kernel config status, introduce
two new states: DEPRECATED and OBSOLETE.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
just adding these config variables to init/Kconfig shouldn't affect
the current build status, but it will allow developers to s
On Wed, Jan 17, 2007 at 05:51:18PM +0100, Frank Haverkamp wrote:
> Sysfs.h uses definitions (e.g. struct list_head s_sibling) from list.h
> but does not include it.
>
> Signed-off-by: Frank Haverkamp <[EMAIL PROTECTED]>
> ---
> include/linux/sysfs.h |1 +
> 1 file changed, 1 insertion(+)
>
>
On 1/17/07, Len Brown <[EMAIL PROTECTED]> wrote:
The code that enables ACPI mode hasn't really changed since before 2.6.12 --
unless udelay() has changed beneath us...
So if you are going to test an old version of Linux, you should start before
then.
Perhaps you can try this debug patch on top
commit d8238afa7eedc047b57da7ec98e98fb051fc4e85
Author: Chris Leech <[EMAIL PROTECTED]>
Date: Fri Nov 17 11:37:29 2006 -0800
I/OAT: Add documentation for the tcp_dma_copybreak sysctl
Signed-off-by: Chris Leech <[EMAIL PROTECTED]>
looks fishy, like a cvs update went bad:
diff -puN Docu
Tomasz Chmielewski wrote:
All right.
I see that initramfs is attached to the kernel itself.
So it leaves me only a question: will I fit all tools into 300 kB
(considering I'll use uClibc and busybox)?
You don't need to use busybox and have a bunch of tools.
The klibc distribution comes wi
Oleg Nesterov wrote:
> On 01/17, Cedric Le Goater wrote:
>> Oleg Nesterov wrote:
>>> On 01/17, Daniel Hokka Zakrisson wrote:
It was the only semi-plausible explanation I could come up with. I added a
printk in do_exit right before exit_task_namespaces, where sighand was
still set, an
Am Montag, 15. Januar 2007 15:53 schrieb Vaidyanathan Srinivasan:
>
> 33Mhz 32-bit PCI bus on typical PC can do around 100MB/sec...
Substract roughly n * 5MB for VIA chipsets, where n is the age (1 <= n <=
4), and even more for SIS, ATI..
Pete
-
To unsubscribe from this list: send the line "uns
On Tue, 16 Jan 2007, Peter Zijlstra wrote:
> The current NFS client congestion logic is severely broken, it marks the
> backing device congested during each nfs_writepages() call and implements
> its own waitqueue.
This is the magic bullet that Andrew is looking for to fix the NFS issues?
> Inde
On Wed, 17 Jan 2007, Chip Coldwell wrote:
On Wed, 17 Jan 2007, Andi Kleen wrote:
On Wednesday 17 January 2007 07:31, Chris Wedgwood wrote:
On Tue, Jan 16, 2007 at 08:52:32PM +0100, Christoph Anton Mitterer wrote:
I agree,... it seems drastic, but this is the only really secure
solution.
I'
On 01/17, Cedric Le Goater wrote:
>
> Oleg Nesterov wrote:
> > On 01/17, Daniel Hokka Zakrisson wrote:
> >> It was the only semi-plausible explanation I could come up with. I added a
> >> printk in do_exit right before exit_task_namespaces, where sighand was
> >> still set, and one right before the
On 1/17/07, Sunil Naidu <[EMAIL PROTECTED]> wrote:
On 1/17/07, Matheus Izvekov <[EMAIL PROTECTED]> wrote:
> I just tried the firmwarekit, and here are the results, attached.
> TYVM, thats a very useful tool.
I do suspect ACPI issues on my new DG965WH MOBO:-
http://www.intel.com/products/motherb
On Tue, 16 Jan 2007, Andrew Morton wrote:
> Do what blockdevs do: limit the number of in-flight requests (Peter's
> recent patch seems to be doing that for us) (perhaps only when PF_MEMALLOC
> is in effect, to keep Trond happy) and implement a mempool for the NFS
> request critical store. Additio
Kirill Korotaev <[EMAIL PROTECTED]> writes:
> Eric, though I personally don't care much:
> 1. I ask for not setting your authorship/copyright on the code which you just
> copied
> from other places. Just doesn't look polite IMHO.
I can't claim complete ownership of the code, there was plenty of
The 5th parameter of filldir_t function type used by vfs_readdir
was changed from ino_t to u64 in October. Unfortunately the patch
missed some files in fs/nfsd where functions pointers of type
encode_dent_fn are passed around and finally cast to filldir_t.
The effect is only visible when an NFS
On Wed, Jan 17, 2007 at 10:09:08AM +0059, Jiri Slaby wrote:
> [EMAIL PROTECTED] wrote:
> [...]
> > +Tips on when/where to use the above attributes:
> > + o The module_init()/module_exit() functions (and all
> > + initialization functions called _only_ from these)
> > + should be marked __
Quoting Alexey Dobriyan ([EMAIL PROTECTED]):
> Apply after "[PATCH] Fix NULL ->nsproxy dereference in /proc/*/mounts".
>
> Similar to get_task_mm(): get a reference to task's mnt namespace if any.
> Suggested by Pavel Emelianov.
>
> Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Yeah, that's
Oleg Nesterov wrote:
> On 01/17, Daniel Hokka Zakrisson wrote:
Call Trace:
[] _spin_lock_irqsave+0x20/0x90
[] lockd_down+0x125/0x190
[] nfs_free_server+0x6d/0xd0
[] nfs_kill_super+0xc/0x20
[] deactivate_super+0x7d/0xa0
[] release_mounts+0x6e/0x80
[] __
Benjamin Romer <[EMAIL PROTECTED]> writes:
> On the Unisys ES7000/ONE system, we encountered a problem where
> performing a kexec reboot or dump on any cell other than cell 0 causes
> the system timer to stop working, resulting in a hang during timer
> calibration in the new kernel.
>
> We traced
Kirill Korotaev <[EMAIL PROTECTED]> writes:
> Eric, really good job!
>
> Patches: 1-13, 15-24, 26-32, 34-44, 46-49, 52-55, 57 (all except below)
> Acked-By: Kirill Korotaev <[EMAIL PROTECTED]>
>
> 14/59 - minor (extra space)
> 25/59 - minor note
> 33/59 - not sorted sysctl IDs
> 45/59 - typo
>
On 01/17, Daniel Hokka Zakrisson wrote:
>
> >> Call Trace:
> >> [] _spin_lock_irqsave+0x20/0x90
> >> [] lockd_down+0x125/0x190
> >> [] nfs_free_server+0x6d/0xd0
> >> [] nfs_kill_super+0xc/0x20
> >> [] deactivate_super+0x7d/0xa0
> >> [] release_mounts+0x6e/0x80
> >> [] __put_mnt_ns+0x66/0x80
On Wed, 17 Jan 2007, Bill Davidsen wrote:
> Robert P. J. Day wrote:
> > a couple random thoughts on the notion of obsolescence and
> > deprecation.
>
> [...horrible example deleted...]
>
> > so is that ioctl obsolete or deprecated? those aren't the same
> > things, a good distinction be
Bernhard Walle <[EMAIL PROTECTED]> :
> --- linux-2.6.20-rc4.orig/drivers/net/r8169.c 2007-01-07 06:45:51.0
> +0100
> +++ linux-2.6.20-rc4/drivers/net/r8169.c 2007-01-17 11:39:13.792309228
> +0100
[...]
> @@ -2227,7 +2227,7 @@ static int rtl8169_xmit_frags(struct rtl
> {
> stru
1 - 100 of 207 matches
Mail list logo
