Some shipped files were wrongly ignored by git. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- .gitignore | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 45a1318453ecc5fa346d323e8d806a5630a7191c diff --git a/.gitignore b/.gitignore index 27c3e83..80d891b 100644 --- a/.gitignore +++ b/.gitignore @@ -17,15 +17,21 @@ *.lst *.symtypes +# .gitignore files +!.gitignore + # # Top-level generic files # tags TAGS vmlinux* -!vmlinux.lds.S +!vmlinux*.l...

Noticed today that the combination of 4KSTACKS and DEBUG_STACKOVERFLOW config options is a bit deadly. DEBUG_STACKOVERFLOW warns in do_IRQ if we're within THREAD_SIZE/8 of the end of useable stack space, or 512 bytes on a 4k stack. If we are, then it goes down the dump_stack path, which uses most, if not all, of the remaining stack, thereby turning a well-intentioned warning into a full-blown catastrophe. The callchain from the warning looks something like this, with stack usage shown as found...

Yep, I thought about something like that... and I assume you'd need a Yes, but if you happen to warn deeper anyway, just because you got "lucky" with IRQ timing, you'll still explode. Regardless of where the threshold is, there's still a risk of starting the warning deeper than that. Whatever stack the warning takes effectively reduces the useable stack size. -Eric -

Hi! I'm a newbie here on the list and also as a "kernel hacker". There's a I have marked it as rejected as as I can see at the time this function is called, it is guaranteed that ret_from_intr() will not call schedule() on return from an interrupt handler to either kernel space or user space because of the call to macro might_sleep() in semaphore's down(). Am I wrong? Thanks and best regards, Aleksandar Dezelin -

On Wed, 29 Aug 2007 23:41:13 +0200 Looks good to me - does need a Signed-off-by: line however -

Hi, I am wondering if this is a known issue, but I just built the current git and several autofs mounts mysteriously disappeared. Restarting autofs could fix some, but then lose others. 2.6.22 was fine. Is there anything I could check other than bisect? (It may take some time for me to get to it) Thanks for your help. Hua -

does anyone know from which address does the kernel load the initrd? I mean the default value? I want to boot the filesystem using a ramdisk. but the I don't know where to put it in my ram? as I don't have flash , I can only load the ramdisk into the ram. and which boot option should I use? thanks regards, yang -

I've long hated the non-killability of tasks accessing a dead NFS server. Linus had an idea for fixing this way back in 2002: http://www.ussg.iu.edu/hypermail/linux/kernel/0208.0/0167.html which I've prototyped in this patch. Splitting up TASK_* into separate bits is going to need a lot more auditing, I think. It was easier back in 2002, but since then we've added TASK_STOPPED and TASK_TRACED which also need to be gingerly checked for. There's some debug code left in here to discourage Linus ...

Andrew, Here's rev 3 of the IOAT DCA patches that are currently in -mm. These patches include updates based on feedback on the previous sets, as well as a couple of other fixes we found internally. These were originally posted on 20-Jul-2007 - see http://marc.info/?l=linux-kernel&m=118489237427303&w=2 They apply to 2.6.23-rc4 and are targeted for merge into 2.6.24. The following series implements support for providers and clients of Direct Cache Access (DCA), a method for warming the ca...

Direct Cache Access (DCA) is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses. This patch adds a manager and interface for matching up client requests for DCA services with devices that offer DCA services. In order to use DCA, a module must do bus writes with the appropriate tag bits set to trigger a cache read for a specific CPU. However, different CPUs and chipsets can require different sets of tag bits, and the methods for determin...

Split the general PCI startup from the DMA handling code in order to prepare for adding support for DCA services and future versions of the ioatdma device. [Rusty Russell] Removal of __unsafe() usage. Signed-off-by: Shannon Nelson <shannon.nelson@intel.com> Acked-by: David S. Miller <davem@davemloft.net> --- drivers/dma/Makefile | 2 drivers/dma/ioat.c | 196 ++++++++++++++++++++++++++++++++++++++++++++++ drivers/dma/ioat_dma.c | 180 ++++++++++--------------...

Rename the ioatdma.c file in preparation for splitting into multiple files, which will allow for easier adding new functionality. Signed-off-by: Shannon Nelson <shannon.nelson@intel.com> Acked-by: David S. Miller <davem@davemloft.net> --- drivers/dma/Makefile | 1 drivers/dma/ioat_dma.c | 818 ++++++++++++++++++++++++++++++++++++++++++++++++ drivers/dma/ioatdma.c | 818 ------------------------------------------------ 3 files changed, 819 insertions(+), 818 deletions(-) ...

From: Peter Lund <firefly@vax64.dk> Negative shifts are not allowed in C (the result is undefined). Same thing with full-width shifts. It works on most platforms but not on the VAX with gcc 4.0.1 (it results in an "operand reserved" fault). Applies to Linux 2.6.22. Signed-off-by: Peter Lund <firefly@vax64.dk> --- Take 4 uses BITS_PER_LONG instead of 8 * sizeof(unsigned long) Take 3 checks for shifts >= the width of the left value (after promotion) Take 2 removes index, a var...

It's stex, right? It seems to have some issues with multiple completions -- Jens Axboe -

And you based that conclusion on what exactly? -- Jens Axboe -

Yep indeed, I thought you meant that it was a scsi bug (and not an stex one). You could try and copy the 2.6.19 stex driver into 2.6.20 and see if that works, though. -- Jens Axboe -

Hi all, at least the 2x Quad-Core Apple Mac Pro appears to have some over-heat protection which suddenly powers off the whole box under load. This adds support for the fans and temerature sensors in the Mac Pro - later some "windwarm" a-like code should probably monitor the values. For now manually tweaking the fans prevents the sudden shutdown for me. cd /sys/devices/platform/applesmc.768 for x in fan{1,2,3,4}; do echo 1 > ${x}_manual echo 1285 > ${x}_output done Two sensors are 0,...

Hi, -- Best Regards, Felipe Balbi felipebalbi@users.sourceforge.net -

Hello, When my system boots, I get several set_drive_speed_status errors. (Please see attached dmesg output.) Can someone explain what they mean? How do I get rid of them? Is there something I need to set in the config? or something I should not have set? Bonus question: is there some way to turn on DMA for hda? Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot 0000:00:07...

Hi, http://ucmk.sourceforge.net/ucmk-project.pdf We are working on Andi Kleen's suggestions. We have started this project. The link is given above. As of now we have suggested and elaborated three implementations. regards Soumendu Sekhar S -

What happens when the full name is > 31 characters? It looks to me that it will be truncated, which takes away the uniqueness guarantee. There must be an individual property that is guaranteed to be unique and less than 32 characters. How about "ibm,my-drc-index"? That looks like a good candidate. -

Commit: 2aae950b21e4bc789d1fc6668faf67e8748300b7 With new vdso gettimeofday support in glibc: [https://bugzilla.redhat.com/show_bug.cgi?id=262481] After 5 minutes of uptime, the system clock goes screwy. When running a simple 'while /bin/true ; date ; uptime ; sleep 2 ; done' loop: Wed Aug 29 01:01:14 EDT 2007 01:01:14 up 4 min, 4 users, load average: 0.13, 0.40, 0.21 Wed Aug 29 01:01:16 EDT 2007 01:01:16 up 4 min, 4 users, load average: 0.13, 0.40, 0.21 Wed Aug 29 02:09:3...

8* sizeof(unsigned long) is the constant BITS_PER_LONG. -

Hi all, Here is a list of some known regressions in 2.6.23-rc4 with patches available. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions List of Aces Name Regressions fixed since 21-Jun-2007 Adrian Bunk 9 Andi Kleen 5 Linus Torvalds 5 Andrew Morton 4 Hugh Dickins 4 Al Viro ...

The following patch fixes this regression (confirmed by Andrey). Please queue it for 2.6.23. I'll come back later for another try at sorting this all out. PNP: remove SMCf010 quirk If the quirk enables the SIR part of the SMCf010 device, the 8250 driver may claim it as a legacy ttyS device, which makes the legacy probe in the smsc-ircc2 driver fail. Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com> Index: w/drivers/pnp/quirks.c ==================================================...