Rafael,
On Thu, 2007-09-20 at 23:45 +0200, Rafael J. Wysocki wrote:
> > We disable everything in device_suspend()
>
> No, we don't. sysdevs are _not_ suspended in device_suspend().
> They are suspended in device_power_down(), which is called
> _after_ disable_nonboot_cpus() (from
On Thursday 20 September 2007 4:22:37 pm Jared Hulbert wrote:
> > > I think that this idea is not worth it.
>
> Don't use the config option then
>
> > My problem is that switching off printk is the single biggest bloat
> > cutter in the kernel, yet it makes the resulting system very hard to
>
On Wed, Sep 19, 2007 at 10:46:26PM -0700, Andrew Morton wrote:
(from ecryptfs_encrypt_page()):
> > + enc_extent_virt = kmalloc(PAGE_CACHE_SIZE, GFP_USER);
>
> I'd have thought that alloc_page() would be nicer. After all, we _are_
> treating it as a page, and not as a random piece of memry.
>
>
On Thursday, 20 September 2007 23:35, Linus Torvalds wrote:
>
> On Thu, 20 Sep 2007, Thomas Gleixner wrote:
> >
> > In meantime I figured out what's happening. The ordering in
> > hibernate_snapshot() is wrong. It does:
Actually, this is incorrect. Please read my reply to Thomas, just sent.
PATCH 2.6.23-rc6-mm1 - Panic in blk_rq_map_sg() from CCISS driver
New scatter/gather list chaining [sg_next()] treats 'page' member of
struct scatterlist with low bit set [0x01] as a chain pointer to
another struct scatterlist [array]. The CCISS driver request function
passes an uninitialized,
On Thu, 20 Sep 2007, Thomas Gleixner wrote:
>
> In meantime I figured out what's happening. The ordering in
> hibernate_snapshot() is wrong. It does:
Hmm. This is close to the ordering we have in STR too.
I have some dim memory of there being some ACPI reason why it had to be
done that way.
Jason Gaston wrote:
Resend trying to remove 8-bit characters in the email.
This patch adds the Intel Tolapai RAID controller DID's for SATA support.
Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
--- linux-2.6.23-rc4/drivers/ata/ahci.c.orig2007-08-27 18:32:35.0
-0700
+++
On Thu, 20 Sep 2007 17:07:15 -0400
Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> On 08/09/2007 12:55 PM, Andrew Morton wrote:
> > On Thu, 9 Aug 2007 11:59:43 +0200 Matthias Hensler <[EMAIL PROTECTED]>
> > wrote:
> >
> >> On Sat, Aug 04, 2007 at 10:44:26AM +0200, Matthias Hensler wrote:
> >>> On
Thomas,
On Thursday, 20 September 2007 23:08, Thomas Gleixner wrote:
> Rafael,
>
> On Thu, 2007-09-20 at 22:39 +0200, Rafael J. Wysocki wrote:
> > > Works as well. What's the difference between this and the real thing ?
> >
> > The real thing also calls device_power_down(PMSG_FREEZE), which is
v2: rebasing on 2.6.23-rc6-mm1
Analyzing various data structures when NR_CPU count is raised
to 4096 shows the following arrays over 128k. If the maximum
number of cpus are not installed (about 99.99% of the time),
then a large percentage of this memory is wasted.
--
151289856 CALNDATA
v2: rebasing on 2.6.23-rc6-mm1
(This resulted in one change removed and one change added.)
cpu_data is currently an array defined using NR_CPUS. This means that
we overallocate since we will rarely really use maximum configured cpus.
When NR_CPU count is raised to 4096 the size of cpu_data
Matthew Wilcox <[EMAIL PROTECTED]> writes:
> Connect two machines with a serial cable. On the victim:
>
> [EMAIL PROTECTED]:~$ cat
> Now, let's find out which ttyS on the other machine is connected ...
>
> [EMAIL PROTECTED]:~$ echo foo >/dev/ttyS1
> -bash: echo: write error: Input/output error
On Thu, 20 Sep 2007 15:33:34 -0500
[EMAIL PROTECTED] (Cliff Wickman) wrote:
> Stress testing revealed the need for more revision.
> This is a revision of Andrew's
> mspec-handle-shrinking-virtual-memory-areas.patch
>
> Version 4: clear/release fetchop pages only when vma_data is no longer
Le 14.09.2007 21:04, Laurent Riffard a écrit :
> Le 14.09.2007 13:06, Jens Axboe a écrit :
>> On Fri, Sep 14 2007, Jens Axboe wrote:
>>> On Fri, Sep 14 2007, Laurent Riffard wrote:
Le 10.09.2007 22:19, Laurent Riffard a écrit :
> Jens,
>
> git-block.patch broke pktcdvd, I've got
> > I think that this idea is not worth it.
Don't use the config option then
> My problem is that switching off printk is the single biggest bloat cutter in
> the kernel, yet it makes the resulting system very hard to support. It
> combines a big upside with a big downside, and I'd like
On Thursday 20 September 2007, Frans Pop wrote:
> On Thursday 20 September 2007, Rafael J. Wysocki wrote:
> > On Thursday, 20 September 2007 20:33, Alexey Starikovskiy wrote:
> > > Frans Pop wrote:
> > > > Maybe S0 should be taken outside the #ifdef and the loop as that
> > > > state is also
Jason Gaston wrote:
This patch removes some incorrect formatting spaces and replaces them with tabs.
Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Kristen Carlson Accardi wrote:
In anticipation of more features, increase number of config flags
allowed, and move the init flags.
Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]>
Cc: Hugh Dickens <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the line
It appears that the LSI SAS 1064E chip needs to be reset after a
suspend/resume cycle before the driver attempts further communications with
the chip. Without this patch, resuming the chip results in this error
message being printed repeatedly and no more disk I/O.
mptbase: ioc0: ERROR - Invalid
Rafael,
On Thu, 2007-09-20 at 22:39 +0200, Rafael J. Wysocki wrote:
> > Works as well. What's the difference between this and the real thing ?
>
> The real thing also calls device_power_down(PMSG_FREEZE), which is a
> counterpart of sysdev_shutdown(), more or less, and I think that's what goes
>
On Thu, Sep 20, 2007 at 03:42:31PM -0400, Joseph Fannin wrote:
> I just ran into this link error (CONFIG_PCMCIA=m;
> CONFIG_SSB_PCMCIAHOST=y). No big deal; I don't have the hardware.
>
> But yeah, this is still a problem.
config SSB_PCMCIAHOST_POSSIBLE
bool
depends on
On 08/09/2007 12:55 PM, Andrew Morton wrote:
> On Thu, 9 Aug 2007 11:59:43 +0200 Matthias Hensler <[EMAIL PROTECTED]> wrote:
>
>> On Sat, Aug 04, 2007 at 10:44:26AM +0200, Matthias Hensler wrote:
>>> On Fri, Aug 03, 2007 at 11:34:07AM -0700, Andrew Morton wrote:
>>> [...]
>>> I am also willing to
Connect two machines with a serial cable. On the victim:
[EMAIL PROTECTED]:~$ cat /dev/ttyS1
-bash: echo: write error: Input/output error
Oops, that's not a serial port. No output on rowlf, as expected.
OK, carrying on ...
[EMAIL PROTECTED]:~$ echo bar >/dev/ttyS0
And yet on rowlf, we now
On Thursday 20 September 2007 2:58:44 pm Alexey Dobriyan wrote:
> On Thu, Sep 20, 2007 at 03:38:42PM -0500, Rob Landley wrote:
> > I've been playing with an idea for a while to improve the printk()
> > situation, but it's a more intrusive change than I've had time to bang
> > on.
> >
> > Right
[EMAIL PROTECTED] wrote:
>
> This patch is based on 2.6.23-rc6 with the prior per_cpu patches
> applied. I can also provide a version based on 2.6.23-rc4-mm1
> which has some different changes.
>
I just noticed that 2.6.23-rc6-mm1 is now available. I will rebase
this patch on that version
On Thu, 20 Sep 2007 16:41:22 -0500 Rob Landley wrote:
> On Thursday 20 September 2007 12:10:50 pm Tim Bird wrote:
> > Andy Whitcroft wrote:
> > > Knowing nothing about these options, from a test perspective it would
> > > be nice if we were able to simply enable "the lot" so we can do "normal"
>
David Newall wrote:
Philipp Marek wrote:
AFAIK pivot_root() changes the / mapping for *all* processes, no?
The manual page is confusing. It even admits to being "intentionally
vague". However the goal seems clear:
"pivot_root() moves the root file system of the current process to
Analyzing various data structures when NR_CPU count is raised
to 4096 shows the following arrays over 128k. If the maximum
number of cpus are not installed (about 99.99% of the time),
then a large percentage of this memory is wasted.
--
151289856 CALNDATA irq_desc
135530496
cpu_data is currently an array defined using NR_CPUS. This means that
we overallocate since we will rarely really use maximum configured cpus.
When NR_CPU count is raised to 4096 the size of cpu_data becomes
3,145,728 bytes.
These changes were adopted from the sparc64 (and ia64) code. An
On Thursday, 20 September 2007 22:32, Frans Pop wrote:
> On Thursday 20 September 2007, Rafael J. Wysocki wrote:
> > On Thursday, 20 September 2007 20:33, Alexey Starikovskiy wrote:
> > > Frans Pop wrote:
> > > > On Thursday 20 September 2007, you wrote:
> > > >> Please try this patch.
> > > >
> >
On Thursday 20 September 2007 12:10:50 pm Tim Bird wrote:
> Andy Whitcroft wrote:
> > Knowing nothing about these options, from a test perspective it would
> > be nice if we were able to simply enable "the lot" so we can do "normal"
> > -mm runs and "tiny" -mm runs without any manual intervention?
On Thu, Sep 20, 2007 at 01:09:51PM +0400, Pavel Emelyanov wrote:
> J. Bruce Fields wrote:
> > On Tue, Sep 18, 2007 at 05:41:08PM +0400, Pavel Emelyanov wrote:
> >> This is the next step in fs/locks.c cleanup before turning
> >> it into using the struct pid *.
> >>
> >> This time I found, that
OK, this version I can't see any more problem with. Thanks!
--b.
On Thu, Sep 20, 2007 at 12:48:32PM +0400, Pavel Emelyanov wrote:
> This code is run under lock_kernel(), which is dropped during
> sleeping operations, so the following race is possible:
>
> CPU1:
Stress testing revealed the need for more revision.
This is a revision of Andrew's mspec-handle-shrinking-virtual-memory-areas.patch
Version 4: clear/release fetchop pages only when vma_data is no longer shared
Version 3: single thread the clearing of vma_data maddr[]
Version 2: refcount
On Thursday 20 September 2007, Rafael J. Wysocki wrote:
> On Thursday, 20 September 2007 20:33, Alexey Starikovskiy wrote:
> > Frans Pop wrote:
> > > On Thursday 20 September 2007, you wrote:
> > >> Please try this patch.
> > >
> > > Works. All states are now listed again.
> > > I've not tested
Alexey Dobriyan wrote:
> Given that
> a) there're plenty of printks without any KERN_* bloat,
> b) there're printks that SHOULD NOT have KERN_* bloat,
Just to clarify, which bloat are you concerned about?
I presume source code bloat (but maybe you mean
message size bloat, or object code bloat)?
On Thursday, 20 September 2007 16:12, Rafael J. Wysocki wrote:
> On Thursday, 20 September 2007 15:43, Thomas Gleixner wrote:
> > On Thu, 2007-09-20 at 15:29 +0200, Rafael J. Wysocki wrote:
> > > > > I haven't had the time to check if any special command line arguments
> > > > > help.
> > > > >
On Thursday, 20 September 2007 17:49, Thomas Gleixner wrote:
> On Thu, 2007-09-20 at 16:50 +0200, Thomas Gleixner wrote:
> > > > > Well, the above may affect SMP systems, but the Vaio is UP. Hmm?
> > > >
> > > > My jinxed VAIO variant is SMP, but it looks like the same mysterious
> > > > error.
On Thu, 20 Sep 2007 21:20:24 +0200
Tilman Schmidt <[EMAIL PROTECTED]> wrote:
> Another data point. When booting into runlevel 3, the system is usable,
> although these messages still appear after boot:
>
> <4>[ 22.731025] sysfs: duplicate filename 'bInterfaceNumber' can not be
> created
>
On Thu, 20 Sep 2007 21:19:44 +0200
Olaf Hering <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 19, Andrew Morton wrote:
>
> > I'm not very confident that this will work well with the
> > already-queued move-mm_struct-and-vm_area_struct.patch.
>
> You want me to redo my patch agains the current -mm
On Thu, Sep 20, 2007 at 01:15:05PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 20 Sep 2007, J. Bruce Fields wrote:
> >
> > we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since
> > then we get the message
> ...
>
> Bruce - you're losing authorship information.
Whoops, yes, I
On 9/20/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> Intel's Open Source Technology Center is pleased to announce the
> LessWatts.org project, an open source project for saving power on Linux.
>
> http://www.lesswatts.org
>
>
> What is LessWatts.org about?
>
>
>
On Thu, 20 Sep 2007, J. Bruce Fields wrote:
>
> we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since
> then we get the message
...
Bruce - you're losing authorship information.
Please don't do that.
Put a
From: Wolfgang Walter <[EMAIL PROTECTED]>
at the top of
Fixes from Alan, PCI IDs from ATI/AMD.
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ahci.c| 10 ++
drivers/ata/libata-core.c |4
On Thu, 2007-09-20 at 15:38 -0500, Rob Landley wrote:
> And so far no behavior has changed. But now the _fun_ part is, you can add a
> config symbol for "what is the minimum loglevel I care about?" Set that as a
> number from 0-9. And then you can define the printk to do:
>
> #define
On Thursday, 20 September 2007 20:11, Agarwal, Lomesh wrote:
> Can someone tell me the flow of code for these two scenarios -
> I write disk to /sys/power/state. How does system go to hibernation? How
> does this trigger ACPI driver functions?
> I issue shutdown command.
> I am using 2.6.18
First of all, this makes the structure jumping look a little
bit cleaner. So, this stands alone as a tiny cleanup. But,
we also need 'mnt' by itself a few more times later in this
series, so this isn't _just_ a cleanup.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c |
On Thu, Sep 20, 2007 at 03:38:42PM -0500, Rob Landley wrote:
> I've been playing with an idea for a while to improve the printk() situation,
> but it's a more intrusive change than I've had time to bang on.
>
> Right now, the first argument to printk() is a loglevel, but it's handled via
>
On Thursday, 20 September 2007 19:37, Maxim Levitsky wrote:
> On Thursday 20 September 2007 18:37:27 Len Brown wrote:
> > On Thursday 20 September 2007 12:13, Maxim Levitsky wrote:
[--snip--]
> >
>
>
> Hi,
>
> Well, what can I say
> Big big thanks, works perfectly.
>
> All resume device
On Thursday, 20 September 2007 20:33, Alexey Starikovskiy wrote:
> Frans Pop wrote:
> > On Thursday 20 September 2007, you wrote:
> >> Please try this patch.
> >
> > Works. All states are now listed again.
> > I've not tested suspend to disk, but suspend to ram and power off work fine.
> >
> >>
On Thu, Sep 20, 2007 at 12:52:52PM -0700, Dave Hansen wrote:
>
> First of all, this makes the structure jumping look a little
> bit cleaner. So, this stands alone as a tiny cleanup. But,
> we also need 'mnt' by itself a few more times later in this
> series, so this isn't _just_ a cleanup.
If we can't pull just this patch in for now, it would be
great to get everything leading up to here pulled in. I've
re-implemented this several ways, and it has never caused
the preceeding patches to change at all.
--
This is the real meat of the entire series. It actually
implements the
Originally from: Herbert Poetzl <[EMAIL PROTECTED]>
This is the core of the read-only bind mount patch set.
Note that this does _not_ add a "ro" option directly to
the bind mount operation. If you require such a mount,
you must first do the bind, then follow it up with a
'mount -o remount,ro'
Elevate the write count during the vfs_rmdir() call.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c |5 +
1 file changed, 5 insertions(+)
diff -puN fs/namei.c~do-rmdir-elevate-write-count fs/namei.c
---
This takes care of all of the direct callers of vfs_mknod().
Since a few of these cases also handle normal file creation
as well, this also covers some calls to vfs_create().
So that we don't have to make three mnt_want/drop_write()
calls inside of the switch statement, we move some of its
logic
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c |4
lxc-dave/ipc/mqueue.c |5 -
2 files changed, 8 insertions(+), 1 deletion(-)
diff -puN fs/namei.c~elevate-mnt-writers-for-vfs-unlink-callers fs/namei.c
This basically audits the callers of xattr_permission(), which
calls permission() and can perform writes to the filesystem.
This conflicts with the current (~2.6.23-rc7) audit
git tree in -mm. wiggle'ing the patch merges it.
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave
This is the first really tricky patch in the series. It
elevates the writer count on a mount each time a
non-special file is opened for write.
This is not completely apparent in the patch because the
two if() conditions in may_open() above the
mnt_want_write() call are, combined, equivalent to
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/inode.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff -puN fs/inode.c~elevate-write-count-for-do-sys-utime-and-touch-atime
fs/inode.c
---
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/utimes.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff -puN fs/utimes.c~elevate-write-count-for-do-utimes fs/utimes.c
---
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/open.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff -puN fs/open.c~elevate-writer-count-for-do-sys-truncate fs/open.c
---
may_open() calls vfs_permission() before it does checks for
IS_RDONLY(inode). It checks _again_ inside of vfs_permission().
The check inside of vfs_permission() is going away eventually.
With the mnt_want/drop_write() functions, all of the r/o
checks (except for this one) are consistently done
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
---
lxc-dave/fs/inode.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff -puN fs/inode.c~elevate-write-count-for-file_update_time fs/inode.c
---
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
---
lxc-dave/net/unix/af_unix.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff -puN
net/unix/af_unix.c~unix-find-other-elevate-write-count-for-touch-atime
If we depend on the inodes for writeability, we will not
catch the r/o mounts when implemented.
This patches uses __mnt_want_write(). It does not guarantee
that the mount will stay writeable after the check. But,
this is OK for one of the checks because it is just for a
printk().
The other
This also uses the little helper in the NFS code to
make an if() a little bit less ugly. We introduced
the helper at the beginning of the series.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c|4
chown/chmod,etc... don't call permission in the same way
that the normal "open for write" calls do. They still
write to the filesystem, so bump the write count during
these operations.
This conflicts with the current (~2.6.23-rc7) audit
git tree in -mm. wiggle'ing the patch merges it.
Pretty self-explanatory. Fits in with the rest of the series.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c|5 +
lxc-dave/fs/nfsd/nfs4recover.c |4
2 files changed, 9 insertions(+)
diff -puN
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c | 10 ++
1 file changed, 10 insertions(+)
diff -puN fs/namei.c~elevate-write-count-for-link-and-symlink-calls fs/namei.c
---
Some ioctls need write access, but others don't. Make a helper
function to decide when write access is needed, and take it.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/ncpfs/ioctl.c | 54 +-
1 file changed, 53 insertions(+), 1
It is OK to let access() go without using a mnt_want/drop_write()
pair because it doesn't actually do writes to the filesystem,
and it is inherently racy anyway. This is a rare case when it is
OK to use __mnt_is_readonly() directly.
Acked-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by:
Some ioctl()s can cause writes to the filesystem. Take
these, and make them use mnt_want/drop_write() instead.
We need to pass the filp one layer deeper in XFS, but
somebody _just_ pulled it out in February because nobody
was using it, so I don't feel guilty for adding it back.
Signed-off-by:
This patch adds two function mnt_want_write() and
mnt_drop_write(). These are used like a lock pair around
and fs operations that might cause a write to the filesystem.
Before these can become useful, we must first cover each
place in the VFS where writes are performed with a
want/drop pair.
First of all, this makes the structure jumping look a little
bit cleaner. So, this stands alone as a tiny cleanup. But,
we also need 'mnt' by itself a few more times later in this
series, so this isn't _just_ a cleanup.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c |
I'm going to be modifying nfsd_rename() shortly to support
read-only bind mounts. This #ifdef is around the area I'm
patching, and it starts to get really ugly if I just try
to add my new code by itself. Using this little helper
makes things a lot cleaner to use.
Signed-off-by: Dave Hansen
This is against 2.6.23-rc6. Compared to 2.6.23-rc6-mm1, there
are a few (trivial) merge conflicts with the audit git tree,
and one slightly more complicated one with ext2-reservations.patch.
Changes from last post:
- added several kerneldoc comments for exported functions
- broke out the 'mnt'
Christoph H. says this stands on its own and can go in before the
rest of the r/o bind mount set.
---
Some filesystems forego the vfs and may_open() and create their
own 'struct file's.
This patch creates a couple of helper functions which can be
used by these filesystems, and will provide a
On Thu, 2007-09-20 at 12:22 -0700, Jesse Barnes wrote:
> > Eeek, that sounds scary. Can you add "highres=off" as well ?
>
> FWIW I just tried your linux-2.6-hires tree with the attached config and
> still see the problem. It doesn't look like NO_HZ is even an option in
> that tree...
Right,
we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since
then we get the message
lockd: too many open TCP sockets, consider increasing the number of nfsd threads
lockd: last TCP connect from ^\\236^\É^D
These random characters in the second line are caused by a bug in
On Thu, Sep 20, 2007 at 09:15:07AM +0200, Mike Galbraith wrote:
> But, I did just manage to trigger some horrid behavior, and log it. I
> modified the kernel to print task's actual tree key instead of their
> current vruntime, and was watching that while make -j2 was running (and
> not seeing
On Thursday, 20 September 2007 18:34, Alexey Starikovskiy wrote:
> Maciek Rutecki wrote:
> > Frans Pop pisze:
> >> On Thursday 20 September 2007, you wrote:
> When compared with 2.6.22-4, dmesg no longer lists S4 and S5 as
> supported for my Toshiba Satellite A40 laptop (Mobile Intel
On Thu, 20 Sep 2007 21:42:44 +0530
"Kamalesh Babulal" <[EMAIL PROTECTED]> wrote:
> ...
>
> > i have tested the change with cross compiler for power405 with the same
> > .config
> > with which the build problem is solved, but the build fails with another
> > error
> >
> > CC [M]
The following patch simplifies signalfd code, by avoiding it to remain
attached to the sighand during its lifetime.
In this way, the signalfd remain attached to the sighand only during
poll(2) (and select and epoll) and read(2). This also allows to remove all
the custom "tsk == current" checks
On Thu, Sep 13, 2007 at 10:43:33AM +0900, Paul Mundt wrote:
> On Wed, Sep 12, 2007 at 12:59:00PM +0200, Michael Buesch wrote:
> > On Wednesday 12 September 2007 12:17:45 Paul Mundt wrote:
> > > On Wed, Sep 12, 2007 at 12:09:09PM +0200, Michael Buesch wrote:
> > > > There we go. The usual SELECT
On Wednesday 19 September 2007 1:03:09 pm Tim Bird wrote:
> Recently, the CE Linux forum has been working to revive the
> Linux-tiny project. At OLS, I asked for interested parties
> to volunteer to become the new maintainer for the Linux-tiny patchset.
>
> A few candidates came forward, but
This includes the sky2 update that you and sch discussed.
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-linus
to receive the following updates:
drivers/net/myri10ge/myri10ge.c |3 +
drivers/net/phy/phy.c
Linus, please pull from the for-linus branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
for-linus
to receive the following fix, or simply apply from this mail.
drivers/ieee1394/ieee1394_core.c |2 +-
drivers/ieee1394/ohci1394.c |4 +---
2
Another data point. When booting into runlevel 3, the system is usable,
although these messages still appear after boot:
<4>[ 22.731025] sysfs: duplicate filename 'bInterfaceNumber' can not be
created
<4>[ 22.735872] WARNING: at fs/sysfs/dir.c:433 sysfs_add_one()
<7>[ 22.740737]
On Wed, Sep 19, Andrew Morton wrote:
> I'm not very confident that this will work well with the
> already-queued move-mm_struct-and-vm_area_struct.patch.
You want me to redo my patch agains the current -mm kernel?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Need to null terminate environment. Found by inspection
while looking for similar problems to platform uevent bug
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
--- a/drivers/w1/w1.c 2007-08-18 07:50:12.0 -0700
+++ b/drivers/w1/w1.c 2007-09-20 11:44:06.0 -0700
@@ -431,6
Environment wasn't being NULL terminated.
Suggested by Kay Sievers
Fixes: http://bugzilla.kernel.org/show_bug.cgi?id=9034
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
--- a/drivers/base/platform.c 2007-06-25 09:03:10.0 -0700
+++ b/drivers/base/platform.c 2007-09-20
Need to null terminate environment. Found by inspection
while looking for similar problems to platform uevent bug
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
--- a/drivers/power/power_supply_sysfs.c2007-08-18 07:50:10.0
-0700
+++ b/drivers/power/power_supply_sysfs.c
On 2007-09-20 01:55, /me wrote:
> Rats. Sorry. I remember now. That's not the first time I am hit by
> that one. I had even made a resolution to try and find out the correct
> options to set. So what are they? CONFIG_RTC=y and CONFIG_RTC_DRV_CMOS=n?
> Guess I should try that combination in my next
(Please reply via emailed reply-to-all, not via the bugzilla web interface)
On Thu, 20 Sep 2007 05:46:34 -0700 (PDT) [EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9043
>
>Summary: tty not printed to screen
>Product: Other
>Version:
Christoph Lameter <[EMAIL PROTECTED]> writes:
> On Thu, 20 Sep 2007, Christoph Lameter wrote:
>
>> Eric: Anything that comes to mind in sysfs?
>
> Arg. Forget it. Its likely SLUB mm related.
Ok.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wed, 2007-09-19 at 18:27 +0100, Christoph Hellwig wrote:
> > int permission(struct inode *inode, int mask, struct nameidata *nd)
> > {
> > int retval, submask;
> > + struct vfsmount *mnt = NULL;
> > +
> > + if (nd)
> > + mnt = nd->mnt;
> >
> > if (mask & MAY_WRITE) {
>
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Thu, 20 Sep 2007 03:26:10 -0400
> Please pull from the 'upstream' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git upstream
>
> to receive the following changes:
Pulled into net-2.6.24 and pushed out, thanks Jeff!
-
To
On Thu, 20 Sep 2007, Satyam Sharma wrote:
> > [PATCH 5/4] [-mm patch] Rename macros returning the size.
> > The #define SIZE() should be renamed STRUCT_SIZE() since it's always
> > returning the size of the struct with a given name. This would allow
> > TYPEDEF_SIZE() to simply become
In recent development of the RT kernel, some of our experimental code
corrupted the rcu header. But the side effect (crashing) didn't rear its
ugly head until way after the fact. Discussing this with Paul, he
suggested that RCU should have a "self checking" mechanism to detect
these kind of
Frans Pop wrote:
> On Thursday 20 September 2007, you wrote:
>> Please try this patch.
>
> Works. All states are now listed again.
> I've not tested suspend to disk, but suspend to ram and power off work fine.
>
>> +printk(KERN_INFO PREFIX "(supports");
>> #ifdef CONFIG_SUSPEND
>> -
101 - 200 of 1005 matches
Mail list logo
