I don't like adding these funny special case sort of things like this. The user should just be able to specify exactly the partitioning of tasks required, and cpusets should ask the scheduler to do the best job of load balancing possible. I implemented that with my patches to do automatic discovery of the largest set of disjoint cpusets. From there, the problem that cpusets has, is that it lacks a good way to specify that the machine should be partitioned (IIRC because stuff defaults to going ...

From: Rob Landley <rob@landley.net> Two 00-INDEX files under Documentation/w1 Signed-off-by: Rob Landley <rob@landley.net> --- Documentation/w1/00-INDEX | 8 ++++++++ Documentation/w1/masters/00-INDEX | 6 ++++++ 2 files changed, 14 insertions(+) --- /dev/null 2007-04-23 10:59:00.000000000 -0500 +++ kdocs/Documentation/w1/00-INDEX 2007-09-29 13:24:40.000000000 -0500 @@ -0,0 +1,8 @@ +00-INDEX + - This file +masters/ + - Individual chips providing 1-wire busses....

From: Rob Landley <rob@landley.net> The existing Documentation/SM501.txt gives no clue what the chip is or does, so copy the description from Kconfig help text. cc: Ben Dooks <ben@simtec.co.uk> Signed-off-by: Rob Landley <rob@landley.net> --- Documentation/SM501.txt | 5 +++++ 1 file changed, 5 insertions(+) diff -r dc28e4e17791 Documentation/SM501.txt --- a/Documentation/SM501.txt Wed Sep 26 15:52:17 2007 -0700 +++ b/Documentation/SM501.txt Sat Sep 29 14:01:43 2007...

From: Casey Schaufler <casey@schaufler-ca.com> Smack is the Simplified Mandatory Access Control Kernel. Smack implements mandatory access control (MAC) using labels attached to tasks and data containers, including files, SVIPC, and other tasks. Smack is a kernel based scheme that requires an absolute minimum of application support and a very small amount of configuration data. Smack is implemented as a clean LSM. It requires no external code changes and the patch modifies only the Kcon...

Over the last few weeks I have pondered with the idea to extend the current kbuild syntax. The idea have existed for long but only recently I started to think how to do this in a truely flexible manner. Two areas are in need for a bit of attention to improve current kbuild files in the kernel. The first issue is the EXTRA_CFLAGS. They are often conditionally assigned like in the following example: ifeq ($(DEBUG),y) EXTRA_CFLAGS := -DDEBUG endif Introducing the following new variable coul...

The Marvell bridge chips used on HighPoint SATA cards do not seem to support the MWDMA modes (at least that caould be seen in their so-called drivers :-), so the driver needs to account for this -- to achieve this: - add mdma_filter() method from the original patch by Bartlomiej Zolnierkewicz with his consent, also adding the method callout to ide_rate_filter(); - install the method for all chips to only return empty mask if a SATA drive is detected on HPT372{AN]/374 chips... Signed-off-by:...

Running FC6 (updated this am) the temp sensors GNOME applet works with the kernel.org kernel, not the FC6 kernel. This has been true for a while, and I've stopped chasing it, I don't really care right now, since the sensors command works fine and that's what my daemon checks. Using 2.6.23-rc8 (no git) the NIC came up at 100Mbit instead of gigE once, not reproducible. Just in case this kicks off a bunch of "mee too" replies. lspci info follows text. Boot times: I occasionally boot repeatedly ...

That would hardly be a portable NFS environment. Boot a Solaris, or older Linux kernel, and watch your applications barf... This sort of stuff belongs in the automounter, not the kernel. Trond -

Package: samba Looks like it is hardware related after all: http://forums.gentoo.org/viewtopic-p-2820556.html http://ubuntuforums.org/showthread.php?t=531505 http://www.fedoraforum.org/forum/showthread.php?p=452451 One poster wrote "I got similar problems:" http://forums.gentoo.org/viewtopic-t-570392.html http://forums.gentoo.org/viewtopic-t-389449-postdays-0-postorder-asc-start-25.html?sid... I found out that poor smb performance is related to a broken udp-pe...

From: Jan Lübbe <jluebbe@lasnet.de> The new behaviour of CFS exposes a race which occurs if a switch is requested when vt_mode.mode is VT_PROCESS. The process with vc->vt_pid is signaled before vc->vt_newvt is set. This causes the switch to fail when triggered by the monitoing process because the target is still -1. Signed-off-by: Jan Lübbe <jluebbe@lasnet.de> --- Index: linux-2.6.22/drivers/char/vt_ioctl.c ==================================================================...

Not at all. 1024k stripes are way outside the norm. If you do something way outside the norm, and don't tune for it in advance, don't be terribly surprised when something like bonnie++ brings your box to its knees. That's not to say we couldn't make md auto-tune itself more intelligently, but this isn't really a bug. With a sufficiently huge amount of RAM, you'd be able to dynamically allocate the buffers that you're not pre-allocating with stripe_cache_size, but bonnie++ is eating that up...

What problems with ALSA's userspace mixing are you trying to solve? Lee -

Oh and i also forget to mention that i get the same errors when using: KDIR=/usr/src/linux-source-2.6.22/ make [Where the ubuntu kernel package put the source. I configured it with the default ubuntu .config and make oldconfig]. I get one more message though: ~/source/build_stuff/fusd/kfusd$ KDIR=/usr/src/linux-source-2.6.22/ make make -C /usr/src/linux-source-2.6.22/ SUBDIRS=/home/tapas/source/build_stuff/fusd/kfusd EXTRA_CFLAGS=-I/home/tapas/source/build_stuff/fusd/kfusd/../include modul...

/. I hope I haven't crossed the line between determined and annoying. I thought we were done, but now I find meat still on this bone. Posit a normal process having some filesystem root, and a current working directory (pwd) lying within that root subtree. When chroot is performed, pwd is left unchanged. This means it can (and often will) lie outside of the new root. How much of the filesystem lying outside of root should a process be allowed to access? Currently it is the complete fil...

None that I know of. You might find it's easier to just work with a bastardized version of the (latest, with the 2.6.24 MTD updates so it handleds even more chips) m25p80 driver and not go through the SPI framework. It doesn't look like you could even bitbang SPI there, since not all those pins are usable for bit-level I/O. As you note, that hardware doesn't support all that a SPI controller does. It's provided for accessing a single serial flash chip; and not even to do that very smoothly. Y...

Yes, because x86 allows loads to be executed before earlier stores, Anyone that does expect this needs to adjust their expectations. ;-) -

You're 100% right, that comment is total crap. An lfence is *not* a memory barrier, it's just a read memory barrier. Although on some microarchitectures they may of course end up being the same thing. Linus -

Hi Ingo & everbody on the list, first of all: many thanks for developing this great scheduler (also: kudos to Con Kolivas for having developed SD & CK-patchset) (this is my second mail to this list and I hope I'm doing everything right) I'm doing some backup during work right now: rsyncing my home partition (nearly 180 GB) to another harddrive locally & since I'm running compiz-fusion, openoffice and gnome, therefore am in some real "working environment" I thought: give Ingo's new ...

I wonder how that got there. Printing something like bytes remaining: 0x12 (18) is a quite logical thing to do, although pretty darm pointless. otoh, looking at the various instances, we have lots of stuff like this: printk(KERN_ERR "seq-oss: unable to delete queue %d (%d)\n", queue, rc); which I would argue is wrong and is inconsistent with most other error reporting. It should be unable to delete queue %d: %d And this: printk(KERN_ERR "%s: context size (%u) exc...

http://linux.bkbits.net:8080/linux-2.6/?PAGE=cset&REV=4034429a6JsOCMNXT3tTPAX1kX40... Let's kill it, please. (i.e., ACK) --- ~Randy -

"Me, I agree that numbers in parens don't usually make sense for kernel messages." It's too trivial to be included in CodingStyle. --- ~Randy -

Thanks for clearing that up. Yes, you did have me confused. Sure, if something is needless, it doesn't provide value. Andrew listed some cases where parens make sense. He didn't say (and I don't say) [oops, parens] that they always make sense, but the statement in CodingStyle is too strict. Sometimes they --- ~Randy -

freeze_bdev() with the device which is mounted as read only does not change sb->s_frozen from SB_UNFROZEN to SB_FREEZE_TRANS. Because of this behavior, xfs_freeze can break read-only XFS filesystem. Because xfs_thaw does nothing for the filesystem whose sb->s_frozen is SB_UNFROZEN. So freezed readonly XFS filesystem will never be unfreezed. Then we cannot do any unmount/remount operations for that filesystem. This patch updates sb->s_frozen when freeze_bdev() is called for read-only mo...

I must be still asleep this morning, but I think this patch does the exact same thing as the original code does, right? Otherwise, this code would always be failing. Or do I just need to go get my morning coffee to wake up and see the problem here? thanks, greg k-h -

Ah, ok, that makes sense now, thanks. It was the error not getting returned, it was not the fact that we were incorrectly checking the return value of mod_sysfs_init. thanks for clearing this up. greg k-h -