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
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, 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
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 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
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
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
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
>
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 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
On Thu, Sep 27, 2007 at 12:48:33PM -0700, Andrew Morton wrote:
> > __fput+0x124/0x1a9
> > fput+0x31/0x35
> > reiserfs_xattr_set+0x291/0x2b0 [reiserfs]
> > user_set+0x4c/0x57 [reiserfs]
> > reiserfs_setxattr+0x81/0xf1 [reiserfs]
> > vfs_setxattr+0x7d/0xfa
> > setxattr+0xb9/0xd1
> >
Sean,
IB aside,
it looks like an ULP which is capable of being both RDMA aware and RDMA
not-aware,
like iSER and iSCSI, NFS-RDMA and NFS, SDP and sockets,
will be treated as two separete ULPs.
Each has its own IP address, since there is a different IP address for
iWARP
port and "regular" Ethernet
Stephen Hemminger <[EMAIL PROTECTED]> writes:
> No, please don't down this legal rat hole. It would cause bullshit like
> people submitting dual licensed patches to the scheduler or GPL only
> patches to the ath5k or ACPI code.
Precisely. Signed-off-by means the patch author already authorized
On Wed, Sep 26, 2007 at 09:05:15PM -0700, Randy Dunlap wrote:
> On Thu, 27 Sep 2007 11:24:40 +0900 Paul Mundt wrote:
>
> > > +/* static helper functions */
> > > +static s32 max_compare(s32 v1, s32 v2)
> > > +{
> > > + if (v1 < v2)
> > > + return v2;
> > > + else
> > > + return
>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, 2007-09-27 at 12:48 -0700, Andrew Morton wrote:
>
> Hi, Dave!
>
> > It's fully reproducible.
> >
> > /home is mounted with the following options:
> >/dev/mapper/vglinux1-lvhome on /home type reiserfs
> (rw,noatime,nodiratime,user_xattr)
> >
> > This BUG happened with rc8-mm1 too.
>
a.k.a. mm-use-pagevec-to-rotate-reclaimable-page-cleanup-2.patch
Opinions may differ, but I'm uneasy with leaving pages to be rotated on
their pagevecs for too long: although they're still visible via the LRU,
their page counts are raised, which excludes them from some operations.
Memory hotplug
On Thu, 27 Sep 2007 21:18:55 +0200
Laurent Riffard <[EMAIL PROTECTED]> wrote:
> Le 27.09.2007 11:22, Andrew Morton a écrit :
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/
>
> I've got this BUG a few seconds after I logged in into Gnome desktop :
>
a.k.a. mm-use-pagevec-to-rotate-reclaimable-page-cleanup.patch
diff -U5 shows rotate_reclaimable_page() is pointlessly testing
PageActive and PageLRU twice in a row: of course there used to be a
lock taken in between those tests; but now that pagevec_move_tail() is
making those tests under lock,
a.k.a. mm-use-pagevec-to-rotate-reclaimable-page-fix-3.patch
put_page_testzero's VM_BUG_ON(atomic_read(>_count) == 0) fired
a couple of times while heavily swapping (on -rc7-mm1 and -rc8-mm1).
release_pages() has been using spin_lock_irq/spin_unlock_irq: but now
that it's being called by
On Thursday, 27 September 2007 21:37, Randy Dunlap wrote:
> On Thu, 27 Sep 2007 21:48:59 +0200 Rafael J. Wysocki wrote:
>
> > On Thursday, 27 September 2007 21:19, Sam Ravnborg wrote:
> > > On Thu, Sep 27, 2007 at 10:33:51AM -0700, Randy Dunlap wrote:
> > > > On Thu, 27 Sep 2007 18:53:46 +0200
Dhaval Giani wrote:
> +config FAIR_CGROUP_SCHED
> + bool "Control groups"
> + depends on CGROUPS
> + help
There are also stray spaces before the tab on the last two lines above.
Cheers,
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
> It's not necessary to include all of linux/sched.h in linux/oom.h. Instead,
> simply include prototypes for the relevant structs and include linux/types.h
> for gfp_t.
>
> Cc: Andrea Arcangeli <[EMAIL PROTECTED]>
> Cc: Christoph Lameter <[EMAIL PROTECTED]>
> Cc: Alexey Dobriyan <[EMAIL
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 controller independent resource accounting
>
> Above line is
On Thu, 27 Sep 2007 21:48:59 +0200 Rafael J. Wysocki wrote:
> On Thursday, 27 September 2007 21:19, Sam Ravnborg wrote:
> > On Thu, Sep 27, 2007 at 10:33:51AM -0700, Randy Dunlap wrote:
> > > On Thu, 27 Sep 2007 18:53:46 +0200 Sam Ravnborg wrote:
> > >
> > > > Hi Rafael.
> > > > >
> > > > > Fix
On Thu, 27 Sep 2007, Majumder, Rajib wrote:
> We have observed 40ms latency spikes in TCP connections in "burst" type of
> traffic.
> This affects regular TCP sockets.
Are segments being sent full-sized, or is there perhaps some Nagle
component in it as well? I.e., are the applications using
On Thursday, 27 September 2007 21:19, Sam Ravnborg wrote:
> On Thu, Sep 27, 2007 at 10:33:51AM -0700, Randy Dunlap wrote:
> > On Thu, 27 Sep 2007 18:53:46 +0200 Sam Ravnborg wrote:
> >
> > > Hi Rafael.
> > > >
> > > > Fix CPU hotplug breakage on HP nx6325 and similar boxes caused by a
> > > >
On Thu, Sep 27, 2007 at 10:13:42AM -0700, Andrew Morton wrote:
> On Thu, 27 Sep 2007 14:13:21 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]>
> wrote:
>
> > On Thu, 27 Sep 2007, Andy Whitcroft wrote:
> >
> > > Ok, this problem seems to still persist in 2.6.23-rc8-mm2. It seems we
> > > have
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 intended behavior:
parport0 (bw-qcam): use data_reverse for this!
Also increases
I still need to look at the code in detail but I have some concerns
I want to inject into this conversation of future sysfs architecture.
- If we want to carefully limit sysfs from going to wild code review
is clearly not enough. We need some technological measures to
assist us. As the
Sean Hefty wrote:
The sysadmin creates "for iwarp use only" alias interfaces of the form
"devname:iw*" where devname is the native interface name (eg eth0) for
the
iwarp netdev device. The alias label can be anything starting with "iw".
The "iw" immediately after the ':' is the key used by
Le 27.09.2007 11:22, Andrew Morton a écrit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/
I've got this BUG a few seconds after I logged in into Gnome desktop :
[partially hand copied BUG]
BUG: unable to handle kernel NULL pointer dereference at
On Thu, Sep 27, 2007 at 10:33:51AM -0700, Randy Dunlap wrote:
> On Thu, 27 Sep 2007 18:53:46 +0200 Sam Ravnborg wrote:
>
> > Hi Rafael.
> > >
> > > Fix CPU hotplug breakage on HP nx6325 and similar boxes caused by a
> > > reference
> > > to disable_apic_timer (labeled as __initdata) from the
From: Jan Engelhardt <[EMAIL PROTECTED]>
Date: Thu, 27 Sep 2007 16:55:36 +0200 (CEST)
>
> On Sep 27 2007 07:51, Stephen Hemminger wrote:
> >
> >You need every socket to close and all routes to go away including the
> >routes through loopback device, and still there probably are control
>
>What is the model on how client connects, say for iSCSI,
>when client and server both support, iWARP and 10GbE or 1GbE,
>and would like to setup "most" performant "connection" for ULP?
For the "most" performance connection, the ULP would use IB, and all these
problems go away. :)
This proposal
On Thu, Sep 27, 2007 at 12:08:23PM -0700, Dave Hansen wrote:
>
> This kills off the almost empty do_filp_open(). However,
> let's keep filp_open() around. It does the nameidata allocation
> on the stack, and also adds the AT_FDCWD argument. I think
> that's enough to keep it around.
So why
This kills off the almost empty do_filp_open(). However,
let's keep filp_open() around. It does the nameidata allocation
on the stack, and also adds the AT_FDCWD argument. I think
that's enough to keep it around.
---
lxc-dave/fs/open.c | 40 ++--
1 file
On Thu, 27 Sep 2007 23:34:15 +0530 Dhaval Giani wrote:
> > > +config RESOURCE_COUNTERS
> > > + bool "Resource counters"
> > > + help
> > > + This option enables controller independent resource accounting
> > > + infrastructure that works with cgroups
> >
> > Use tab + 2 spaces
From: Helge Hafting <[EMAIL PROTECTED]>
Date: Thu, 27 Sep 2007 13:54:23 +0200
> Wouldn't it be enough to down all the interfaces and close all the sockets?
> No need to bring down every app.
And there are routes, and neighbour cache entries, and all sorts
of external references to the stack.
Sean,
What is the model on how client connects, say for iSCSI,
when client and server both support, iWARP and 10GbE or 1GbE,
and would like to setup "most" performant "connection" for ULP?
Thanks,
Arkady Kanevsky email: [EMAIL PROTECTED]
Network Appliance Inc.
On Thu, Sep 27, 2007 at 11:52:15AM -0700, Dave Hansen wrote:
> If open_namei() succeeds, there is potentially a mnt_want_write()
> that needs to get balanced. If the caller doesn't create a
> 'struct file' and eventually __fput() it, or manually drop the
> write count on an error, we have a bug.
On Thu, Sep 27, 2007 at 02:00:09PM -0400, Luis R. Rodriguez wrote:
> Our guidelines for patches [1] for Linux-wireless has been updated.
> One section asks Linux-wireless developers to subscribe to the patch
> guideline wiki page (section 2) and another which introduces the new
>
My end goal here is to make sure all users of may_open()
return filps. This will ensure that we properly release
mount write counts which were taken for the filp in
may_open().
This patch moves the sys_open flags to namei flags
calculation into fs/namei.c. We'll shortly be moving
the
may_open() can fail in a lot of ways. It is also named
such that it doesn't appear to be _taking_ action, just
checking a bunch of conditions.
So, it makes a poor place to take and release the mnt
writer count. This moves the burder of taking the
mnt writer counts into the callers. The
In a moment, we're going to make may_open() stop doing
the mnt_want/drop_write() pair. Doing this first makes
the next patch simpler.
---
lxc-dave/fs/namei.c | 28 ++--
1 file changed, 22 insertions(+), 6 deletions(-)
diff -puN
Since we know the shared inode count is always >0, we can avoid igrab()
and use an open coded atomic_inc().
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
---
fs/anon_inodes.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
Index:
If open_namei() succeeds, there is potentially a mnt_want_write()
that needs to get balanced. If the caller doesn't create a
'struct file' and eventually __fput() it, or manually drop the
write count on an error, we have a bug.
Forcing open_namei() to return a filp fixes this. Any caller
The first three patches here fix actual bugs. I think
the last two will reduce the chance for any future bugs
to creep in. RFC for now.
--
This is a bug fix for the r/o bind mount patch set.
We need to ensure taking a mnt write on the mnt
referenced by any new struct file.
---
On Thu, Sep 27, 2007 at 02:37:42PM -0400, Theodore Tso wrote:
> I'm reminded of Rusty's 2003 OLS Keynote, where he points out that
> what's important is not making an interface easy to use, but _hard_
> _to_ _misuse_. That fact that sysfs is all laid out in a directory,
> but for which some
The sysadmin creates "for iwarp use only" alias interfaces of the form
"devname:iw*" where devname is the native interface name (eg eth0) for the
iwarp netdev device. The alias label can be anything starting with "iw".
The "iw" immediately after the ':' is the key used by the iw_cxgb3 driver.
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 these data structures so that no
> breakage occurs.
I've read
Ivan Kokshaysky wrote:
> On Wed, Sep 26, 2007 at 03:20:40PM -0700, Jesse Barnes wrote:
>> Ivan, your concern is about disabling things like interrupt controllers
>> and power management chips during probe right? You're right that doing
>> that could cause problems if we get and interrupt or PMU
> 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 controllers.
Old IDE
On Thu, 2007-09-27 at 12:41 +0100, mahamuni ashish wrote:
> I have small code
>
> #include
> #include
>
> int main()
> {
> float f= 1256.35;
> char ch[4];
>
> printf("\n1. f : %f",f);
> memset(ch,'\0',strlen(ch) );
> printf("\n2. f : %f",f);
> return 0;
> }
>
> Expected output is
> 1. f
Hello, Greg.
Please read the other reply first. We need some consensus there first.
Greg KH wrote:
>> * Notify pollers on file deactivation.
>
> This looks nice.
Cool.
>> * Name-formatting for symlinks. e.g. symlink pointing to
>> /dira/dirb/leaf can be named as "symlink:%1-%0" and it
Hello, Greg.
Sorry about the late reply. I'm sandwiched between several release
dates (I bet you know) and sudden burst of family/personal events (all
kinds of them - good, annual and bad).
Greg KH wrote:
>> * sysfs becomes a separate module and driver model becomes a user of
>> sysfs. Those
Hernan G Solari wrote:
> Hello
> I am disturbing you with this problem because I think there is
> something to be learnt, I have
> no urgency or further-problem with my work-around.
>
> Description: trying to boot with kernel 2.6.22 the booting process
> stops not finding
> the root
Mark Lord wrote:
> Tejun Heo wrote:
>> Hello,
>>
>> Mark Lord wrote:
>>> I reported a very similar bug back a few releases ago.
>>> Anyone who wants to try it themselves, can do this with hdparm-7.7 (from
>>> sourceforge):
>>>
>>>hdparm --drq-hsm-error /dev/sda
>>>
>>> Whether or not it hangs
On Thu, 27 Sep 2007 14:00:09 -0400
"Luis R. Rodriguez" <[EMAIL PROTECTED]> wrote:
> Our guidelines for patches [1] for Linux-wireless has been updated.
> One section asks Linux-wireless developers to subscribe to the patch
> guideline wiki page (section 2) and another which introduces the new
>
Peter Schwabe wrote:
> Hello,
>
> in my Thinkpad T61 there is another Hitachi harddisk with NCQ problems
> (spurious completions during NCQ...).
>
> Model number: HITACHI HTS541612J9SA00
> Serial number: SBDIC7JP
>
> Adding the line
>
> { "HITACHI HTS541612J9SA00", "SBDIC7JP",
On Thu, Sep 27, 2007 at 10:40:05AM -0700, Randy Dunlap wrote:
> On Thu, 27 Sep 2007 20:36:24 +0530 Srivatsa Vaddagiri wrote:
> Hi :)
>
> Uh, a few of my previous comments weren't fixed... (below)
>
>
> > --
> >
> > Enable "cgroup" (formerly containers) based fair group scheduling.
> > This
On Thu, Sep 27, 2007 at 10:23:43AM -0700, Andrew Morton wrote:
> On Thu, 27 Sep 2007 11:59:02 -0400 Theodore Tso <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Sep 27, 2007 at 04:19:12PM +0100, Alan Cox wrote:
> > > There are real things to worry about - sysfs, sysfs, sysfs, ... and all
> > > the other
Our guidelines for patches [1] for Linux-wireless has been updated.
One section asks Linux-wireless developers to subscribe to the patch
guideline wiki page (section 2) and another which introduces the new
'Changes-licensed-under' (section 10).
Here I'll cover the new 'Changes-licensed-under' tag
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. Also, if they
did, the support for /sys/firmware/acpi/tables/*
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 helper for
hotplug _very_ early in the boot sequence when the
For Michael Kerrisk request, the following patch renames signalfd_siginfo
fields in order to keep them consistent with the siginfo_t ones.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
---
fs/signalfd.c| 44 ++--
On Thu, 27 Sep 2007 20:36:24 +0530 Srivatsa Vaddagiri wrote:
> Andrew,
> This is a resend of the patch I had sent earlier at:
>
> http://marc.info/?l=linux-kernel=119065506607858
>
> This patch enables group cpu scheduler feature to work with control
> groups.
>
> Could you include
Dave Jones wrote:
> Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
>
> diff --git a/Documentation/devices.txt b/Documentation/devices.txt
> index 8de132a..6c46730 100644
> --- a/Documentation/devices.txt
> +++ b/Documentation/devices.txt
> @@ -94,6 +94,8 @@ Your cooperation is appreciated.
>
On Thu, 27 Sep 2007 18:53:46 +0200 Sam Ravnborg wrote:
> Hi Rafael.
> >
> > Fix CPU hotplug breakage on HP nx6325 and similar boxes caused by a
> > reference
> > to disable_apic_timer (labeled as __initdata) from the CPU initialization
> > code.
> >
> > Signed-off-by: Rafael J. Wysocki
On 9/27/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Torsten Kaiser wrote:
> > I compared the dmesg form good and bad boots with -rc7-mm1 but could
> > not see any difference, so do you think that these additional
> > diagnostics could show a difference?
> > Or could you suggest any other
On Thu, 27 Sep 2007 11:59:02 -0400 Theodore Tso <[EMAIL PROTECTED]> 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
> > >
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. Also, if they
> did, the support for /sys/firmware/acpi/tables/* would be
On Thu, 27 Sep 2007 14:13:21 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Sep 2007, Andy Whitcroft wrote:
>
> > Ok, this problem seems to still persist in 2.6.23-rc8-mm2. It seems we
> > have three options from here:
> > 1) update the compiler support list to exclude these
> Von: Davide Libenzi <[EMAIL PROTECTED]>
> On Thu, 27 Sep 2007, Michael Kerrisk wrote:
[...]
> > .\" FIXME Davide, what does the following mean? How (in userspace
> > .\" terms) does a sighand structure become orphaned?
> > The
> > .BR read (2)
> > call can also return 0,
> > in case the sighand
CONFIG_EXT3_INDEX is not an exposed config option in the kernel,
and it is unconditionally defined in ext3_fs.h. tune2fs is already
able to turn off dir indexing, so at this point it's just cluttering
up the code. Remove it.
Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]>
Index:
CONFIG_EXT4_INDEX is not an exposed config option in the kernel,
and it is unconditionally defined in ext4_fs.h. tune2fs is already
able to turn off dir indexing, so at this point it's just cluttering
up the code. Remove it.
Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]>
Index:
H. Peter Anvin wrote:
Konrad Rzeszutek wrote:
+config ISCSI_IBFT
+ tristate "iSCSI Boot Firmware Table Attributes"
+ depends on X86
why only on X86?
PowerPC exports this data via the OpenFirmware so it already shows in
the /sysfs entries. I was thinking to combine those sysfs
Konrad Rzeszutek wrote:
>>> +config ISCSI_IBFT
>>> + tristate "iSCSI Boot Firmware Table Attributes"
>>> + depends on X86
>> why only on X86?
>
> PowerPC exports this data via the OpenFirmware so it already shows in
> the /sysfs entries. I was thinking to combine those sysfs entries under
On Thu, 27 Sep 2007, Michael Kerrisk wrote:
> .\" Copyright (C) 2007 Michael Kerrisk <[EMAIL PROTECTED]>
> .\" starting from a version by Davide Libenzi <[EMAIL PROTECTED]>
> .\"
> .\" This program is free software; you can redistribute it and/or modify
> .\" it under the terms of the GNU General
Handle memory allocation failures when reading packets.
We have to read something from the host, even if we can't allocate any
memory. If we don't, the host side of the device may fill up and stop
delivering interrupts because no new packets can be queued.
A single sk_buff is allocated whenever
Hi Rafael.
>
> Fix CPU hotplug breakage on HP nx6325 and similar boxes caused by a reference
> to disable_apic_timer (labeled as __initdata) from the CPU initialization
> code.
>
> Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>
> ---
> arch/x86_64/kernel/apic.c |2 +-
> 1 file
On Thu, 27 Sep 2007, Michael Kerrisk wrote:
> Hi Davide,
>
> I've slightly tweaked the eventfd.2 man page in preparation for adding it
> to the man-pages set. Could you please review the text below, and confirm
> that it correctly describes intended behavior.
Looks good to me. At the time that
On Fri, 28 Sep 2007 01:38:27 +0900
FUJITA Tomonori <[EMAIL PROTECTED]> wrote:
> This patch is for Jens' block tree (sg chaining branch).
>
> I don't have the hardware but this looks like a bug.
>
> ---
> From: FUJITA Tomonori <[EMAIL PROTECTED]>
> Subject: [PATCH] x86-64: pci-gart iommu sg
On Thu, 27 Sep 2007, Michael Kerrisk wrote:
> Davide,
>
> A further question: what is the expected behavior in the
> following scenario:
>
> 1. Create a timerfd and arm it.
> 2. Wait until M timer expirations have occurred
> 3. Modify the settings of the timer
> 4. Wait for N further timer
On Thu, 27 Sep 2007, Michael Kerrisk wrote:
> Hi Davide,
>
> A follow up to the man page text. Does passing a timerfd file
> descriptor via a Unix domain socket to another process do the
> expected thing? That is, the receiving process will be able to
> read from the file descriptor in order
This patch is for Jens' block tree (sg chaining branch).
I don't have the hardware but this looks like a bug.
---
From: FUJITA Tomonori <[EMAIL PROTECTED]>
Subject: [PATCH] x86-64: pci-gart iommu sg chaining zeroes a wrong sg's
dma_length
Needs to zero the end of the list.
Signed-off-by:
On Thu, September 27, 2007 09:00, Arnd Bergmann wrote:
> Assuming that we want to go down that road, I think you can do better with
> more evil macro magic, by using something along the lines of
>
> #define KERN_NOTICE "<5>",
>
> #define PRINTK_CONTINUED "",
>
> #define printk(level, str, ...) \
Thanks Juergen,
> It runs stable on 5 different GX1 systems.
>
> But I do not use a standard BIOS. I'm using LinuxBIOS instead. But I'm
also using
> these patches.
>
set_cx86_inc was one of performance trick called by geode_configure
I didn't find any documentation about "incrementor margin"
On Thu, Sep 27, 2007 at 11:24:40AM +0900, Paul Mundt wrote:
> On Wed, Sep 26, 2007 at 03:40:26PM -0700, Mark Gross wrote:
> > + struct list_head list;
> > + union {
> > + s32 value;
> > + s32 usec;
> > + s32 kbps;
> > + };
> > + char *name;
>
> Your }
> On Thursday, 27 September 2007 17:22, Jordan Crouse wrote:
> > On 27/09/07 17:30 +0200, R. J. Wysocki wrote:
> > > On Thursday, 27 September 2007 16:44, Marco Tralli wrote:
> > > > Hello all,
> > > >
> > > > I have random hangs on kernel boot or after few minutes on a NatSemi
Geode
> > > > GX1
> if you're going to add that libata-related parm to the kernel parms
> file, wouldn't it make sense for consistency to add the other
> available boot-time parms from libata-core.c as well? it seems
> counter-productive to document only a subset of them from the same
> source file.
He's not
Hi AMrco,
On Thursday 27 September 2007 16:44, Marco Tralli wrote:
> I have random hangs on kernel boot or after few minutes on a NatSemi Geode
> GX1 based PC-104 (from Advantech) using kernel 2.6.23-rc6. The system
> locks, no way to use SysRq key, no usefull logs.
>
> No problems using kernel
On Wed, 26 Sep 2007, Francois Romieu wrote:
> Apply and try each patch of the attached tarball on top of 2.6.23-git
> until the behavior changes (assuming it does).
>
> Patch #000n applies on top of patch #000(n - 1).
I tested the series on top of -rc8 and 0005 did the trick. And if I use
0005
> On 27/09/07 17:30 +0200, R. J. Wysocki wrote:
> > On Thursday, 27 September 2007 16:44, Marco Tralli wrote:
> > > Hello all,
> > >
> > > I have random hangs on kernel boot or after few minutes on a NatSemi
Geode
> > > GX1 based PC-104 (from Advantech) using kernel 2.6.23-rc6. The system
locks,
>
On Thu, 27 Sep 2007, Dave Jones wrote:
> 'noacpi' isn't a standalone parameter, give it its prefix.
>
> Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
>
> diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> index 4d175c7..a87bc58 100644
> ---
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 about two releases later
> > saying it
On Thu, 2007-09-27 at 15:00 +0100, Christoph Hellwig wrote:
> On Thu, Sep 27, 2007 at 03:51:07PM +0200, Peter Zijlstra wrote:
> > Christoph,
> >
> > does Steve's story make sense?
>
> Yes.
>
> > All that would need to be done is add an extra lock_class_key to
> > file_system_type for
101 - 200 of 714 matches
Mail list logo
