Re: [PATCH] hugetlbfs read() support

On Thu, 19 Jul 2007, Bill Irwin wrote: > On Thu, Jul 19, 2007 at 10:07:59AM -0700, Nishanth Aravamudan wrote: > > But I do think a second reason to do this is to make hugetlbfs behave > > like a normal fs -- that is read(), write(), etc. work on files in the > > mountpoint. But that is simply my

Re: [patch] add kdump_after_notifier

Eric W. Biederman wrote: > Vivek Goyal <[EMAIL PROTECTED]> writes: > >>> Bernhard's idea (kdump uses panic_notifier) is very good for me. But it >>> isn't >>> good for kdump user, because they want to take a dump ASAP when panicked. >>> >> This one is better than registering kdump as one of the

Re: inotify and /proc/

Joseph Pingenot wrote: While we're on the subject, is there some way to receive notification that some aspect of a process changes (in this case, stopping using CPU, but not exiting). For some internal stuff a while back I did a patch that allows any process to register for status change

[PATCH] fs/gfs2: mark struct *_operations const

these struct *_operations are all method tables, thus should be const. Signed-off-by: Denis Cheng <[EMAIL PROTECTED]> --- fs/gfs2/eaops.c|8 fs/gfs2/eaops.h|4 ++-- fs/gfs2/glock.c|2 +- fs/gfs2/ops_dentry.c |3 +-- fs/gfs2/ops_dentry.h |2

[rfc] balance-on-fork NUMA placement

Hi, I haven't given this idea testing yet, but I just wanted to get some opinions on it first. NUMA placement still isn't ideal (eg. tasks with a memory policy will not do any placement, and process migrations of course will leave the memory behind...), but it does give a bit more chance for the

Re: [SPARC32] NULL pointer derefference

Hi David, One possible issue is sequencing, perhaps the stack argument copy is occuring before the new context is setup properly on sun4c. I think it is somthing related to this but too much has changed for me to work out what is going on. At present, I don't have a good enough

Re: [patch 20/26] saa7134: fix thread shutdown handling

On Tue, Jul 31, 2007 at 02:05:48AM -0300, Mauro Carvalho Chehab wrote: > Hi Greg, > > Em Seg, 2007-07-30 ??s 21:33 -0700, Greg KH escreveu: > > anexo Documento somente texto > > (saa7134-fix-thread-shutdown-handling.patch) > > -stable review patch. If anyone has any objections, please let us

Re: [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v4)

> +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan, > + struct list_head *dst, > + unsigned long *scanned, int order, > + int mode, struct zone *z, > +

Re: regression on HP zx1 platform from ACPI autoload modules patches

> > During bootup it panics with: > > > > Kernel panic - not syncing: Unable to find SBA IOMMU: Try a generic or DIG > > kernel I think that the fix for this has already gone into Linus's tree (on Friday). Commit SHA1 for the patch that should fix this is:

Re: [SPARC32] NULL pointer derefference

On 7/29/07, Mark Fortescue <[EMAIL PROTECTED]> wrote: > Hi All, > > Unfortunatly Sparc32 sun4c low level memory management apears to be > incompatible with commit b6a2fea39318e43fee84fa7b0b90d68bed92d2ba > mm: variable length argument support. I feel like I ought to help out with this since it's

Re: [PATCH 2/2] Introduce CONFIG_SUSPEND (updated)

On Sunday 29 July 2007 17:27, Rafael J. Wysocki wrote: > Still, there are many other files in which CONFIG_PM can be replaced > with CONFIG_PM_SLEEP or even with CONFIG_SUSPEND, but they can be updated in > the future. There is #ifdef CONFIG_PM around all the .suspend and .resume methods.

Re: [patch 20/26] saa7134: fix thread shutdown handling

Hi Greg, Em Seg, 2007-07-30 às 21:33 -0700, Greg KH escreveu: > anexo Documento somente texto > (saa7134-fix-thread-shutdown-handling.patch) > -stable review patch. If anyone has any objections, please let us know. > > -- > > From: Jeff Mahoney <[EMAIL PROTECTED]> > > This

Re: TCP SACK issue, hung connection, tcpdump included

I've been able to capture a tcpdump from both ends during the problem and its my belief there is a bug in 2.6.20.1 (at the client side) in that it issues a SACK option for an old sequence which the current window being advertised is beyond it. This is the most concerning issue as the

Re: [PATCH] add check do_direct_IO() return val

Joe Jin wrote: Hmm.. in this config file, whats causing DIO to panic ? Which test actually passing faulty buffer ? By my testing, just defined job3 and job10 will also get the panic, but if only have one of them, panic will not appear. the faulty buffer maybe passed by mmap. Thanks.

Re: [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito

On Tue, 31 Jul 2007 13:29:32 +0900 KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote: > On Mon, 30 Jul 2007 22:15:50 -0600 > "David Mosberger-Tang" <[EMAIL PROTECTED]> wrote: > > > This seems crazy to me. Flushing should occur according to the > > *architecture*, not model-by-model. Even if we

Re: [PATCH 0/5] x86_64 EFI support -v3

"Huang, Ying" <[EMAIL PROTECTED]> writes: > Looking forward to your comments, After reading through the patches. I don't see any compelling reason to use the efi runtime support. It looks like we get the interesting support for efi without out. The graphics and the memory map. We have ACPI

Re: [patch 00/26] 2.6.21.7 -stable review

On Mon, Jul 30, 2007 at 09:30:47PM -0700, Greg KH wrote: > This is the start of the stable review cycle for the 2.6.21.7 release. > There are 26 patches in this series, all will be posted as a response to > this one. If anyone has any issues with these being applied, please let > us know. If

Re: [PATCH 2/2] Debug handling of early spurious interrupts

On Tue, 31 Jul 2007 11:25:26 +0900 Fernando Luis Vázquez Cao <[EMAIL PROTECTED]> wrote: > > runtime. Some drivers don't get used by many people and users of some > > architectures (esp embedded) tend to lag kernel.org by a long time. So it > > could be years before all the fallout from this

Re: [PATCH 1/5] x86_64 EFI support -v3: EFI base support

"Huang, Ying" <[EMAIL PROTECTED]> writes: > Changelog between v2 and v3: > > 1. The EFI callwrapper is re-implemented in assembler. > > --- > > This patch adds basic support for EFI x86_64 system. The main file of > the patch is the addition of efi.c for x86_64. This file is modeled > after the

Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document

"Huang, Ying" <[EMAIL PROTECTED]> writes: > This patch adds document for EFI x86_64 support. The boot parameters > added are documented in Documentation/i386/zero-page.txt. The setup > and operation guide of EFI based system is documented in > Documentation/x86_64/uefi.txt. > > Signed-off-by:

Re: [2.6.22] negative time jump

john stultz wrote: > On 7/29/07, Vasily Averin <[EMAIL PROTECTED]> wrote: >> I've investigated why my testnode freezes. When I found that node is freezed >> again I've started to press Sysrq keys and noticed the following negative >> time jump. >> >> Could anybody please help me to understand the

[patch 24/26] sky2: workaround for lost IRQ

-stable review patch. If anyone has any objections, please let us know. -- This patch restores a couple of workarounds from 2.6.16: * restart transmit moderation timer in case it expires during IRQ routine * default to having 10 HZ watchdog timer. At this point it more

Re: [PATCH 4/5] x86_64 EFI support -v3: EFI framebuffer driver

"Huang, Ying" <[EMAIL PROTECTED]> writes: > This patch adds Graphics Output Protocol support to the kernel. > UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and > only Graphics Output Protocol (GOP) is produced. Therefore, the boot > loader needs to query the UEFI firmware with

Re: [PATCH] add check do_direct_IO() return val

> Hmm.. in this config file, whats causing DIO to panic ? Which test actually > passing faulty buffer ? > By my testing, just defined job3 and job10 will also get the panic, but if only have one of them, panic will not appear. the faulty buffer maybe passed by mmap. Thanks, Joe - To unsubscribe

[patch 23/26] NTP: remove clock_was_set() call to prevent deadlock

-stable review patch. If anyone has any objections, please let us know. -- The clock_was_set() call in seconds_overflow() which happens only when leap seconds are inserted / deleted is wrong in two aspects: 1. it results in a call to on_each_cpu() with interrupts disabled 2. it

[patch 25/26] V4L: bttv: fix v4l1 api usage breaking the driver

-stable review patch. If anyone has any objections, please let us know. -- From: Trent Piepho <[EMAIL PROTECTED]> If one uses a V4L *one* application, such as vlc or mplayer's v4l driver, as the first user after the driver is loaded, the driver wedges itself and will never

[patch 26/26] V4L: cx88-blackbird: fix vidioc_g_tuner never ending list of tuners

-stable review patch. If anyone has any objections, please let us know. -- From: Jelle Foks <[EMAIL PROTECTED]> v4l-info and other programs would loop indefinitely while querying the tuners for cx88-blackbird cards. The cause was that vidioc_g_tuner didn't return an error

[patch 20/26] saa7134: fix thread shutdown handling

-stable review patch. If anyone has any objections, please let us know. -- From: Jeff Mahoney <[EMAIL PROTECTED]> This patch changes the test for the thread pid from >= 0 to > 0. When the saa8134 driver initialization fails after a certain point, it goes through the complete

[patch 21/26] serial: clear proper MPSC interrupt cause bits

-stable review patch. If anyone has any objections, please let us know. -- From: Jay Lubomirski <[EMAIL PROTECTED]> The interrupt clearing code in mpsc_sdma_intr_ack() mistakenly clears the interrupt for both controllers instead of just the one its supposed to. This can result

[patch 22/26] i386: fix infinite loop with singlestep int80 syscalls

-stable review patch. If anyone has any objections, please let us know. -- The commit 635cf99a80f4ebee59d70eb64bb85ce829e4591f introduced a regression. Executing a ptrace single step after certain int80 accesses will infinitely loop and never advance the PC. The TIF_SINGLESTEP

[patch 17/26] audit: fix oops removing watch if audit disabled

-stable review patch. If anyone has any objections, please let us know. -- From: Tony Jones <[EMAIL PROTECTED]> Removing a watched file will oops if audit is disabled (auditctl -e 0). To reproduce: - auditctl -e 1 - touch /tmp/foo - auditctl -w /tmp/foo - auditctl -e 0 - rm

[patch 18/26] POWERPC: Fix subtle FP state corruption bug in signal return on SMP

-stable review patch. If anyone has any objections, please let us know. -- This fixes a bug which can cause corruption of the floating-point state on return from a signal handler. If we have a signal handler that has used the floating-point registers, and it happens to

[patch 19/26] mm: kill validate_anon_vma to avoid mapcount BUG

-stable review patch. If anyone has any objections, please let us know. -- From: Hugh Dickins <[EMAIL PROTECTED]> validate_anon_vma gave a useful check on the integrity of the anon_vma list when Andrea was developing obj rmap; but it was not enabled in SLES9 itself, nor in

[patch 14/26] sched: fix next_interval determination in idle_balance()

-stable review patch. If anyone has any objections, please let us know. -- From: Christoph Lameter <[EMAIL PROTECTED]> Fix massive SMP imbalance on NUMA nodes observed on 2.6.21.5 with CFS. (and later on reproduced without CFS as well). The intervals of domains that do not

[patch 15/26] posix-timers: Prevent softirq starvation by small intervals and SIG_IGN

-stable review patch. If anyone has any objections, please let us know. -- posix-timers which deliver an ignored signal are currently rearmed in the timer softirq: This is necessary because the timer needs to be delivered again when SIG_IGN is removed. This is not a problem,

[patch 16/26] FUTEX: Restore the dropped ERSCH fix

-stable review patch. If anyone has any objections, please let us know. -- The return value of futex_find_get_task() needs to be -ESRCH in case that the search fails. This was part of the original futex fixes and got accidentally dropped, when the futex-tidy-up patch was split

[patch 13/26] hugetlb: fix get_policy for stacked shared memory files

-stable review patch. If anyone has any objections, please let us know. -- From: Adam Litke <[EMAIL PROTECTED]> Here's another breakage as a result of shared memory stacked files :( The NUMA policy for a VMA is determined by checking the following (in the order given): 1)

[patch 12/26] dm crypt: fix remove first_clone

-stable review patch. If anyone has any objections, please let us know. -- From: Olaf Kirch <[EMAIL PROTECTED]> Get rid of first_clone in dm-crypt This gets rid of first_clone, which is not really needed. Apparently, cloned bios used to share their bvec some time way in the

[patch 11/26] dm crypt: fix avoid cloned bio ref after free

-stable review patch. If anyone has any objections, please let us know. -- From: Olaf Kirch <[EMAIL PROTECTED]> Do not access the bio after generic_make_request We should never access a bio after generic_make_request - there's no guarantee it still exists. Signed-off-by: Olaf

Re: [PATCH 3/5] x86_64 EFI support -v3: EFI runtime support

"Huang, Ying" <[EMAIL PROTECTED]> writes: > This patch adds runtime service support for EFI x86_64 system. > > The EFI support for emergency_restart and RTC clock is added. The EFI > based implementation and legacy BIOS or CMOS based implementation are > put in separate functions and are chosen

[patch 09/26] dm crypt: disable barriers

-stable review patch. If anyone has any objections, please let us know. -- From: Milan Broz <[EMAIL PROTECTED]> Disable barriers in dm-crypt because of current workqueue processing can reorder requests. This must be addresed later but for now disabling barriers is needed to

[patch 10/26] dm crypt: fix call to clone_init

-stable review patch. If anyone has any objections, please let us know. -- From: Olaf Kirch <[EMAIL PROTECTED]> Call clone_init early We need to call clone_init as early as possible - at least before call bio_put(clone) in any error path. Otherwise, the destructor will try to

[patch 08/26] md: Fix bug in error handling during raid1 repair.

-stable review patch. If anyone has any objections, please let us know. -- From: Mike Accetta <[EMAIL PROTECTED]> If raid1/repair (which reads all block and fixes any differences it finds) hits a read error, it doesn't reset the bio for writing before writing correct data back,

[patch 05/26] pi-futex: Fix exit races and locking problems

-stable review patch. If anyone has any objections, please let us know. -- From: Alexey Kuznetsov <[EMAIL PROTECTED]> 1. New entries can be added to tsk->pi_state_list after task completed exit_pi_state_list(). The result is memory leakage and deadlocks. 2.

[patch 06/26] hpt366: disallow Ultra133 for HPT374

-stable review patch. If anyone has any objections, please let us know. -- Eliminate UltraATA/133 support for HPT374 -- the chip isn't capable of this mode according to the manual, and doesn't even seem to tolerate 66 MHz DPLL clock... Signed-off-by: Sergei Shtylyov <[EMAIL

[patch 07/26] md: Fix two raid10 bugs.

-stable review patch. If anyone has any objections, please let us know. -- 1/ When resyncing a degraded raid10 which has more than 2 copies of each block, garbage can get synced on top of good data. 2/ We round the wrong way in part of the device size calculation, which

[patch 03/26] rt-mutex: Fix stale return value

-stable review patch. If anyone has any objections, please let us know. -- Alexey Kuznetsov found some problems in the pi-futex code. The major problem is a stale return value in rt_mutex_slowlock(): When the pi chain walk returns -EDEADLK, but the waiter was woken up

[patch 04/26] rt-mutex: Fix chain walk early wakeup bug

-stable review patch. If anyone has any objections, please let us know. -- Alexey Kuznetsov found some problems in the pi-futex code. One of the root causes is: When a wakeup happens, we do not to stop the chain walk so we we follow a non existing locking chain. Drop out

[patch 02/26] sparsemem: fix oops in x86_64 show_mem

-stable review patch. If anyone has any objections, please let us know. -- We aren't sampling for holes in memory. Thus we encounter a section hole with empty section map pointer for SPARSEMEM and OOPs for show_mem. This issue has been seen in 2.6.21, current git and current

[patch 00/26] 2.6.21.7 -stable review

Very sorry for the long delay in getting these out, it should be the last 2.6.21-stable release, unless there are some patches that people point out to us that deserve a new .21.y release. This is the start of the stable review cycle for the 2.6.21.7 release. There are 26 patches in this series,

[patch 01/26] BNX2: Fix netdev watchdog on 5708.

-stable review patch. If anyone has any objections, please let us know. -- There's a bug in the driver that only initializes half of the context memory on the 5708. Surprisingly, this works most of the time except for some occasional netdev watchdogs when sending a lot of

Re: [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito

On Mon, 30 Jul 2007 22:15:50 -0600 "David Mosberger-Tang" <[EMAIL PROTECTED]> wrote: > This seems crazy to me. Flushing should occur according to the > *architecture*, not model-by-model. Even if we happen to get "lucky" > on pre-Montecito CPUs, that doesn't justify such ugly hacks. I'm not

Re: [rfc] direct IO submission and completion scalability issues

On Mon, Jul 30, 2007 at 01:35:19PM -0700, Suresh B wrote: > On Mon, Jul 30, 2007 at 11:20:04AM -0700, Christoph Lameter wrote: > > On Fri, 27 Jul 2007, Siddha, Suresh B wrote: > > > > Observation #2: This introduces some migration overhead during IO > > > submission. > > > With the current

[GIT PULL] sh updates for 2.6.23-rc2

Please pull from: master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.23.git Which contains: Adrian McMenamin (1): sh: Fix Dreamcast DMA issues. David McCullough (2): sh: arch/sh/boot - fix shell usage sh: fix get_wchan() for SH kernels without framepointers

Re: [PATCH 0/5] x86_64 EFI support -v3

"Huang, Ying" <[EMAIL PROTECTED]> writes: > Following sets of patches add EFI/UEFI (Unified Extensible Firmware > Interface) support to x86_64 architecture. The patches have been > tested against 2.6.23-rc1 kernel on Intel platforms with EFI1.10 and > UEFI2.0 firmware. > > UEFI specification can

Re: [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito

This seems crazy to me. Flushing should occur according to the *architecture*, not model-by-model. Even if we happen to get "lucky" on pre-Montecito CPUs, that doesn't justify such ugly hacks. Or you really want to debug this *again* come next CPU? --david On 7/30/07, KAMEZAWA Hiroyuki

[GIT PULL] sh64 updates for 2.6.23-rc2

Please pull from: master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh64-2.6.git Which contains: Paul Mundt (3): sh64: Fix fs.h removal from mm.h regressions. sh64: Fix irq_intc build failure. sh64: Kill off virt_to_bus()/bus_to_virt(). arch/sh64/Kconfig

RE: [PATCH 0/4][RFC] lro: Generic Large Receive Offload for TCP traffic

> -Original Message- > From: [EMAIL PROTECTED] [mailto:netdev- > [EMAIL PROTECTED] On Behalf Of Andrew Gallatin > Sent: Monday, July 30, 2007 10:43 AM > To: Linas Vepstas > Cc: Jan-Bernd Themann; netdev; Thomas Klein; Jeff Garzik; Jan-Bernd > Themann; linux-kernel; linux-ppc; Christoph

Re: CONFIG_SUSPEND? (was: Re: [GIT PATCH] ACPI patches for 2.6.23-rc1)

On Mon, 30 Jul 2007, Len Brown wrote: On Saturday 28 July 2007 12:55, Linus Torvalds wrote: So I think the real issue is that we allow that "suspend_devices_and_enter()" code to be compiled without HOTPLUG_CPU in the first place. It's not supposed to work that way. I don't see how

Re: [2/3] 2.6.23-rc1: known regressions v3

Meelis Roos wrote: >>> Subject : New ACPI error/warning with Linus' latest GIT >>> References : http://lkml.org/lkml/2007/7/26/395 >>> Last known good : ? >>> Submitter : Ismail Dönmez <[EMAIL PROTECTED]> >>> Caused-By : ? >>> Handled-By : ? >>> Status :

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 10:56:27PM -0500, Joseph Pingenot wrote: > >From Al Viro on Tuesday, 31 July, 2007: > >On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote: > >> I'm trying to implement pwait. It blocks until a specified PID exits, > >> and then it exits. > >er... ptrace(2)?

Re: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:

Quoting Len Brown ([EMAIL PROTECTED]): > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > > pnpacpi=off Went out for dinner, machine was frozen on return. One less on the checklist .. -- - To unsubscribe from this list: send the line "unsubscribe

Re: inotify and /proc/

>From Al Viro on Tuesday, 31 July, 2007: >On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote: >> I'm trying to implement pwait. It blocks until a specified PID exits, >> and then it exits. >er... ptrace(2)? Should work for most common usage scenarios, although will suspect that it

[PATCH] create CONFIG_SUSPEND_UP_POSSIBLE

From: Linus Torvalds <[EMAIL PROTECTED]> Without this change, it is possible to build CONFIG_HIBERNATE on all !SMP architectures, but not necessarily their SMP versions. I don't know for sure if the architecture list under SUSPEND_UP_POSSIBLE is correct. For now it simply matches the list for

Re: Kernel Build Failure

On Mon, 30 Jul 2007 22:31:00 -0500 Chris Holvenstot wrote: > I am having a problem, likely caused by the vacuum between my ears, but > I thought that a few of you would find it recreational to tear up an > inexperienced user for doing dumb things. > > I have what is quickly becoming a

Re: [PATCH 0/2] Introduce CONFIG_HIBERNATION and CONFIG_SUSPEND (updated)

On Sunday 29 July 2007 20:21, Linus Torvalds wrote: > > Ok, I took this, and modified Len's patch to re-introduce ACPI_SLEEP on > top of it (I took the easy way out, and just made PM_SLEEP imply > ACPI_SLEEP, which should make everything come out right. I could have > dropped ACPI_SLEEP

Re: [PATCH] Remove fs.h from mm.h

On Mon, Jul 30, 2007 at 02:36:13AM +0400, Alexey Dobriyan wrote: > 0) Remove fs.h from mm.h. For this, > 1) Uninline vma_wants_writenotify(). It's pretty huge anyway. > 2) Add back fs.h or less bloated headers (err.h) to files that need it. > sh ended up breaking all over the place, and sh64 in a

Re: CONFIG_SUSPEND? (was: Re: [GIT PATCH] ACPI patches for 2.6.23-rc1)

On Saturday 28 July 2007 12:55, Linus Torvalds wrote: > So I think the real issue is that we allow that > "suspend_devices_and_enter()" code to be compiled without HOTPLUG_CPU in > the first place. It's not supposed to work that way. I don't see how CONFIG_HOTPLUG_CPU justifies its own

Marvell 7042 (sata_mv) fails to initialize drive

I just tried hooking up a Hitachi 1TB SATA-II drive to a Marvell 7042 based controller, and the most recent Linux kernel (2.6.23-rc1) fails to properly initialize the interface. Here are the relevant kernel messages: kernel: [43.312417] sata_mv :06:00.0: version 0.81 kernel: [43.312752]

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote: > I'm trying to implement pwait. It blocks until a specified PID exits, > and then it exits. er... ptrace(2)? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote: > From Al Viro on Tuesday, 31 July, 2007: > >On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote: > >> >From Joseph Pingenot on Monday, 30 July, 2007: > >> >From Al Viro on Tuesday, 31 July, 2007: > >> >>On Mon, Jul 30,

Re: [RFC 12/26] ext2 white-out support

On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote: > Introduce white-out support to ext2. > > Known Bugs: > - Needs a reserved inode number for white-outs You picked different reserved inodes for the ext2 and ext3 filesystems. That's good for a NACK right there. The codepoints (i.e.,

Re: [PATCH] add check do_direct_IO() return val

Joe Jin wrote: Well, I'm having a heck of a time getting this to fail. It looks possible, though. Joe, were you guys able to narrow it down to a reproducible test case? Do you have any oops output messages from the crashes? Zach, it easy to reproduce through fio with following

Re: inotify and /proc/

>From Al Viro on Tuesday, 31 July, 2007: >On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote: >> >From Joseph Pingenot on Monday, 30 July, 2007: >> >From Al Viro on Tuesday, 31 July, 2007: >> >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: >> >>> I was trying to use

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote: > >From Joseph Pingenot on Monday, 30 July, 2007: > >From Al Viro on Tuesday, 31 July, 2007: > >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: > >>> I was trying to use inotify to watch process changes (especially

Re: [-mm PATCH 4/9] Memory controller memory accounting (v4)

> + lock_meta_page(page); > + /* > + * Check if somebody else beat us to allocating the meta_page > + */ > + race_mp = page_get_meta_page(page); > + if (race_mp) { > + kfree(mp); > + mp = race_mp; > + atomic_inc(>ref_cnt); > +

[Fwd: [PlanetCCRMA] atl1 driver; sleeping function]

Hi Ingo, I'm forwading this report from a Planet CCRMA user, this is happening to him with 2.6.21.6-rt21... -- Fernando Forwarded Message From: Matt Barber To: [EMAIL PROTECTED] Subject: [PlanetCCRMA] atl1 driver; sleeping function Date: Mon, 30 Jul 2007 06:09:58 -0400 Hello,

Re: [PATCH] sysrq: add a show-stacktrace-on-all-cpus command

Andrew Morton wrote: > On Sun, 29 Jul 2007 13:29:26 +0300 > Avi Kivity <[EMAIL PROTECTED]> wrote: > > >> If a cpu is spinning in the kernel but still responding to interrupts, >> pressing sysrq-y will show you where it's spinning. >> >> Signed-off-by: Avi Kivity <[EMAIL PROTECTED]> >> >> diff

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 10:25:21PM -0500, Joseph Pingenot wrote: > >From Al Viro on Tuesday, 31 July, 2007: > >On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: > >> I was trying to use inotify to watch process changes (especially process > >> termination) by watching /proc/. > >>

Re: inotify and /proc/

>From Joseph Pingenot on Monday, 30 July, 2007: >From Al Viro on Tuesday, 31 July, 2007: >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: >>> I was trying to use inotify to watch process changes (especially process >>> termination) by watching /proc/. >>> Sadly, although I

Kernel Build Failure

I am having a problem, likely caused by the vacuum between my ears, but I thought that a few of you would find it recreational to tear up an inexperienced user for doing dumb things. I have what is quickly becoming a "un-ubuntu" 7.04 system - as time goes on I seem to be replacing the standard

Re: inotify and /proc/

>From Al Viro on Tuesday, 31 July, 2007: >On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: >> I was trying to use inotify to watch process changes (especially process >> termination) by watching /proc/. >> Sadly, although I could see something reading various files, nothing >>

[PATCH 4/5] x86_64 EFI support -v3: EFI framebuffer driver

This patch adds Graphics Output Protocol support to the kernel. UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and only Graphics Output Protocol (GOP) is produced. Therefore, the boot loader needs to query the UEFI firmware with appropriate Output Protocol and pass the video

Re: inotify and /proc/

On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote: > I was trying to use inotify to watch process changes (especially process > termination) by watching /proc/. > > Sadly, although I could see something reading various files, nothing > was issued when the process I was watching

[PATCH 2/5] x86_64 EFI support -v3: EFI boot support

This patch adds boot support for EFI x86_64 system. Boot parameter setup file is updated for x86_64 EFI support. x86_64 EFI boot loader must conform to the EFI boot parameter offsets defined in the file include/asm-x86_64/bootsetup.h (and x86_64 patches submitted to ELILO bootloader conforms to

[PATCH 3/5] x86_64 EFI support -v3: EFI runtime support

This patch adds runtime service support for EFI x86_64 system. The EFI support for emergency_restart and RTC clock is added. The EFI based implementation and legacy BIOS or CMOS based implementation are put in separate functions and are chosen based on the value of efi_enabled. Signed-off-by:

[PATCH 5/5] x86_64 EFI support -v3: EFI document

This patch adds document for EFI x86_64 support. The boot parameters added are documented in Documentation/i386/zero-page.txt. The setup and operation guide of EFI based system is documented in Documentation/x86_64/uefi.txt. Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]> Signed-off-by:

[PATCH 0/5] x86_64 EFI support -v3

Following sets of patches add EFI/UEFI (Unified Extensible Firmware Interface) support to x86_64 architecture. The patches have been tested against 2.6.23-rc1 kernel on Intel platforms with EFI1.10 and UEFI2.0 firmware. UEFI specification can be found here: http://www.uefi.org For booting the

[PATCH 1/5] x86_64 EFI support -v3: EFI base support

Changelog between v2 and v3: 1. The EFI callwrapper is re-implemented in assembler. --- This patch adds basic support for EFI x86_64 system. The main file of the patch is the addition of efi.c for x86_64. This file is modeled after the EFI IA32 avatar. EFI initialization are implemented in

Re: [ck] Re: SD still better than CFS for 3d ?

On 7/31/07, Roland Dreier <[EMAIL PROTECTED]> wrote: > > Fuck you Martin! > > I think you meant to yell at Matthew, not Martin ;) What's amusing about this is he's yelling at me for something I didn't do, can't even get my name right, and has the audacity to claim that *I* am the one

inotify and /proc/

I was trying to use inotify to watch process changes (especially process termination) by watching /proc/. Sadly, although I could see something reading various files, nothing was issued when the process I was watching exited and the directory went away. Is this intentional, or a bug?

Re: [TULIP] Need new maintainer

On Mon, 30 Jul 2007, Valerie Henson wrote: On Mon, Jul 30, 2007 at 03:31:58PM -0400, Kyle McMartin wrote: On Mon, Jul 30, 2007 at 01:04:13PM -0600, Valerie Henson wrote: The Tulip network driver needs a new maintainer! I no longer have time to maintain the Tulip network driver and I'm

[PATCH] Check patch reports multiple var with a function assignment

Running checkpatch.pl products an warning when it should not. I believe it can be fixed by adding to the regular expression, but feel free to fix it another way as I may not know all the cases this is trying to catch. -- check patch output -- WARNING: declaring multiple variables together

Re: [PATCH] Remove fs.h from mm.h

On Mon, 2007-07-30 at 23:43 +0400, Alexey Dobriyan wrote: > On Mon, Jul 30, 2007 at 12:42:07PM +0800, Bryan Wu wrote: > > Can I do something to help this regression testing? > > > > Please feel free to ask me. > > Sorry, blackfin toolchain doesn't like me, so I can't test this myself. > Check

Re: bonnie++ benchmarks for ext2,ext3,ext4,jfs,reiserfs,xfs,zfs on software raid 5

On Mon, Jul 30, 2007 at 09:39:39PM +0200, Miklos Szeredi wrote: > > Extrapolating these %cpu number makes ZFS the fastest. > > > > Are you sure these numbers are correct? > > Note, that %cpu numbers for fuse filesystems are inherently skewed, > because the CPU usage of the filesystem process

[PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito

Add "L2 cache is separated? check flag" as read_mostly global variable. This add one memory reference to global variable to page faults of "executable" map in do_wp_page(page copy case), file-mapped page fault and some system calls which does memory map changes. But not so bad as calling

[PATCH] flush icache before set_pte take6. [3/4] add montecito brand name

Add Brand name "Montecito" to cpuinfo. Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> --- arch/ia64/kernel/setup.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: linux-2.6.23-rc1.test/arch/ia64/kernel/setup.c

[PATCH] flush icache before set_pte take6. [2/4] sync icache dcache

flush icache for ia64 take4. This patch is against 2.6.23-rc1. Changes V5 -> V6: - no changes. (added new patches to the patch set) Changes V4 -> V5: - removed sync_icache_dcache from do_wp_page() page reuse case. Changes v3 -> v4: - avoid implementing flush_(i)cache_pages(). - added

[PATCH] flush icache before set_pte take6. [1/4] migration fix

In migration, a new page should be cache flushed before set_pte() in some archs which have virtually-tagged cache.. V5 -> V6: * no changes (added new patches to the patch set) V4 -> V5: * changed flush_icache_page to flush_cache_page. Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>

Re: [PATCH 2/2] Debug handling of early spurious interrupts

On Mon, 2007-07-30 at 11:22 -0700, Andrew Morton wrote: > On Mon, 30 Jul 2007 18:58:14 +0900 > Fernando Luis V__zquez Cao <[EMAIL PROTECTED]> wrote: > > > > > > > So bad things might happen because of this change. And if they do, they > > > will take a lng time to be discovered, because

  1   2   3   4   5   6   7   8   9   10   >