-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 16 January 2007 23:31, Alan Stern wrote:
> On Tue, 16 Jan 2007, Andrey Borzenkov wrote:
> > I have Toshiba Portege 4000 that almost always hangs dead resuming from
> > STR. This was better before 2.6.18, since then STR is unusable.
Robert P. J. Day wrote:
a couple random thoughts on the notion of obsolescence and
deprecation.
[...horrible example deleted...]
so is that ioctl obsolete or deprecated? those aren't the same
things, a good distinction being drawn here by someone discussing
devfs:
Eric, really good job!
Patches: 1-13, 15-24, 26-32, 34-44, 46-49, 52-55, 57 (all except below)
Acked-By: Kirill Korotaev <[EMAIL PROTECTED]>
14/59 - minor (extra space)
25/59 - minor note
33/59 - not sorted sysctl IDs
45/59 - typo
50/59 - copyright/file note
51/59 - copyright/file
1. I ask for not setting your authorship/copyright on the code which you just
copied
from other places. Just doesn't look polite IMHO.
2. please don't name files like ipc/ipc_sysctl.c
ipc/sysctl.c sounds better IMHO.
3. any reason to introduce CONFIG_SYSVIPC_SYSCTL?
why not simply do
If that was the case, would the port not show up in TIME_WAIT state?
Also, the kernel should only hold a closed socket in TIME_WAIT state for
2 minutes or so. These hung ports stay around until the machine is
rebooted.
This one time, at band camp, Jan Engelhardt wrote:
>> Last week I had a port
Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
> ---
> fs/xfs/linux-2.6/xfs_sysctl.c | 258
> 1 files changed, 180 insertions(+), 78 deletions(-)
Oh no, 100 more
Eric, though I personally don't care much:
1. I ask for not setting your authorship/copyright on the code which you just
copied
from other places. Just doesn't look polite IMHO.
2. I would propose to not introduce utsname_sysctl.c.
both files are too small and minor that I can't see much
On the Unisys ES7000/ONE system, we encountered a problem where
performing a kexec reboot or dump on any cell other than cell 0 causes
the system timer to stop working, resulting in a hang during timer
calibration in the new kernel.
We traced the problem to one line of code in disable_IO_APIC(),
IDs not sorted in enum. see below.
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> We need to have the the definition of all top level sysctl
> directories registers in sysctl.h so we don't conflict by
> accident and cause abi problems.
>
> Signed-off-by: Eric W. Biederman <[EMAIL
another small minor note.
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
> ---
> arch/frv/kernel/pm.c | 50
> +++---
> 1 files changed, 43 insertions(+), 7 deletions(-)
>
> diff
On 01/17, Srivatsa Vaddagiri wrote:
>
> On Wed, Jan 17, 2007 at 06:47:16PM +0300, Oleg Nesterov wrote:
> > > What do you mean by "currently" executing work? worker thread executing
> > > some work on the cpu? That is not possible, because all threads are
> > > frozen at this point. There cant be
a couple random thoughts on the notion of obsolescence and
deprecation.
first, there are places in the kernel (primarily Kconfig files) and
the documentation that unnecessarily conflate these two properties.
as a simple example, consider drivers/pcmcia/Kconfig:
>Last week I had a port (TCP:52557) that was mysteriously unavailable on
>my ubuntu machine (running kernel 2.6.15-27-k7 #1 SMP PREEMPT). If you
>tried to bind to it, it was unavailable. However, nmap (both to
>localhost and from an external host) reported the port closed. fuser,
>lsof, and
minor extra space in table below...
Kirill
> From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
>
> Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
> ---
> fs/xfs/linux-2.6/xfs_sysctl.c | 258
> 1 files changed, 180 insertions(+), 78
Sysfs.h uses definitions (e.g. struct list_head s_sibling) from list.h
but does not include it.
Signed-off-by: Frank Haverkamp <[EMAIL PROTECTED]>
---
include/linux/sysfs.h |1 +
1 file changed, 1 insertion(+)
--- ubi-2.6.git.orig/include/linux/sysfs.h
+++ ubi-2.6.git/include/linux/sysfs.h
Hello,
We've been seeing some nasty data corruption issues on some platforms.
We've been capturing PCI-E traces looking for something nasty but we
haven't found anything yet. One of the hardware guys if asking if there
is a call in Linux to issue a PME_Turn_Off broadcast message.
PME_Turn_Off
The recent discussion on LKML convinced me that a line discipline
is the correct way to layer a driver over a serial interface.
This means, however, that I'll need a (trivial) userspace daemon
which will hold the serial interface open after pushing the line
discipline onto it.
Which raises the
On Tue, 16 Jan 2007, Christoph Hellwig wrote:
> Fir4st I'd say thanks a lot for forward-porting this, it's really useful
> feature for all kinds of nasty debugging.
>
> I think you should split this into two patches, one for the debugreg
> infrastructure, and one for the actual kwatch code.
>
>
* Roland Dreier <[EMAIL PROTECTED]> wrote:
> And actually the lock stuff is OK, since it's not inlined -- it's the
> unlock stuff that goes directly to the __raw versions. But something
> like the following works for me; does it look OK to you?
yeah, it looks good to me too. Hopefully this
On Wed, Jan 17, 2007 at 06:47:16PM +0300, Oleg Nesterov wrote:
> Btw, I agree it is good to have a sleeping lock to protect cpu_online_map.
> But it should be separate from workqueue_mutex, and it is not needed for
> create/destroy/flush funcs.
Which is what lock_cpu_hotplug() attempted to
On Wed, 17 Jan 2007, Ingo Molnar wrote:
> * Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > From: Alan Stern <[EMAIL PROTECTED]>
> >
> > This patch (as839) implements the Kwatch (kernel-space hardware-based
> > watchpoints) API for the i386 architecture. The API is explained in
> > the kerneldoc
On Wed, Jan 17, 2007 at 06:47:16PM +0300, Oleg Nesterov wrote:
> > What do you mean by "currently" executing work? worker thread executing
> > some work on the cpu? That is not possible, because all threads are
> > frozen at this point. There cant be any ongoing flush_workxxx() as well
> > because
Last week I had a port (TCP:52557) that was mysteriously unavailable on
my ubuntu machine (running kernel 2.6.15-27-k7 #1 SMP PREEMPT). If you
tried to bind to it, it was unavailable. However, nmap (both to
localhost and from an external host) reported the port closed. fuser,
lsof, and netstat
Hello,
I got this text when I boot my linux :
--cut--
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind
Christoph Hellwig wrote:
Index: linux-2.6.19-rc6-arnd1+patches/arch/powerpc/platforms/cell/spufs/sched.c
===
---
linux-2.6.19-rc6-arnd1+patches.orig/arch/powerpc/platforms/cell/spufs/sched.c
2006-12-04 10:56:04.730698720
On 01/17, Srivatsa Vaddagiri wrote:
>
> On Tue, Jan 16, 2007 at 04:27:25PM +0300, Oleg Nesterov wrote:
> > > I meant issuing kthread_stop() in DOWN_PREPARE so that worker
> > > thread exits itself (much before CPU is actually brought down).
> >
> > Deadlock if work_struct re-queues itself.
>
>
On Tue, 16 Jan 2007, Pavel Machek wrote:
> Strange, I can't reproduce the hang any more.
>
> I found other weirdness while trying to hang it: if I move the mouse
> while suspending, it is _not_ completely powered off while machine is
> suspended. LED still shines, at half brightness...?!
dmesg
> i think the right way to fix it might be to define a _spin_unlock()
> within those #ifdef branches, and then to define spin_lock as:
>
> static inline void spin_lock(spinlock_t *lock) __acquires(lock)
I tried a similar approach, but what got me was that sparse doesn't
pay attention to the
Hi!
> This communicates with the machine control software via a registry
> residing in a controlling virtual machine. This allows dynamic
> creation, destruction and modification of virtual device
> configurations (network devices, block devices and CPUS, to name some
> examples).
>
>
Apply after "[PATCH] Fix NULL ->nsproxy dereference in /proc/*/mounts".
Similar to get_task_mm(): get a reference to task's mnt namespace if any.
Suggested by Pavel Emelianov.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
fs/proc/base.c | 15 ++-
Hi!
> drivers/xen/core/Makefile |2
> drivers/xen/core/gnttab.c | 422
> ++
> include/xen/gnttab.h | 105 +++
> 3 files changed, 528 insertions(+), 1 deletion(-)
...
>
Hi!
> This provides a bootstrap and ongoing emergency console which is
> intended to be available from very early during boot and at all times
> thereafter, in contrast with alternatives such as UDP-based syslogd,
> or logging in via ssh. The protocol is based on a simple shared-memory
> ring
Hi. Thanks Sorensen and Juergen.
I overlooked the restored to CCR3.
The bit4(0x10, MAPEN) of CCR3 is necessary to access advanced configuration
registers.
I'll repost patch.
- restore CCR3
- fix use 0x30 instead of 0x38.
--- linux-2.6.19.orig/arch/i386/kernel/cpu/cyrix.c 2006-11-30
Hi Roy,
I have added a different pagecache reclaim logic around your
sysctl interface. This would ensure that only pagecache pages are
reclaimed if the limit is exceeded.
--Vaidy
Pagecache pages in memory can be limited to a percentage of total
RAM using this patch.
New sysctl entry
On Wed, 17 Jan 2007, Andi Kleen wrote:
On Wednesday 17 January 2007 07:31, Chris Wedgwood wrote:
On Tue, Jan 16, 2007 at 08:52:32PM +0100, Christoph Anton Mitterer wrote:
I agree,... it seems drastic, but this is the only really secure
solution.
I'd like to here from Andi how he feels about
On Wed, 2007-01-17 at 15:29 +0100, Peter Zijlstra wrote:
> I was thinking that since the server needs to actually sync the page a
> commit might be quite expensive (timewise), hence I didn't want to flush
> too much, and interleave them with writing out some real pages to
> utilise bandwidth.
On Wed, Jan 17, 2007 at 07:21:42PM +0530, Suparna Bhattacharya ([EMAIL
PROTECTED]) wrote:
>
> Since you are implementing new APIs here, have you considered doing an
> aio_sendfilev to be able to send a header with the data ?
It is doable, but why people do not like corking?
With Linux less than
I think one problem with mmap/msync is that they can't maintain
i_size atomically like regular write does. so, one needs to
implement own i_size management in userspace.
thanks, Alex
> Side note: the only reason O_DIRECT exists is because database people are
> too used to it, because other
On Wed, 2007-01-17 at 08:50 -0500, Trond Myklebust wrote:
> On Wed, 2007-01-17 at 09:49 +0100, Peter Zijlstra wrote:
> > > They are certainly _not_ dirty pages. They are pages that have been
> > > written to the server but are not yet guaranteed to have hit the disk
> > > (they were only written
Harald Dunkel wrote:
> Hi Tejun,
>
> Tejun Heo wrote:
>> Hello,
>>
>> Please do the following and post the result.
>>
>> # strace mplayer -v dvd:// > out 2>&1
>>
>
> I had sent this out last week. Any news about this?
Okay, I just tested a number of dvds on x86-64 and x86. The error
pattern is
Fix compile warnings in r8169. It doesn't fix "real" bugs, only that
the driver compiles cleanly without warnings.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
r8169.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- linux-2.6.20-rc4.orig/drivers/net/r8169.c
On Jan 17 2007 16:06, Alon Bar-Lev wrote:
> On 1/17/07, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
>> Another obstacle would be to place the initramfs image on the same
>> partition as the kernel (normally, I dd kernel to /dev/mtd1).
>
> As far as I know you can embed the initramfs into the
Jan Engelhardt wrote:
The device is pretty small and has no keyboard, video card etc., so if it ever
happens to break (can be a disk failure, but also operator who messed with
startup scripts), it has to be opened (warranty!).
These all unpleasant tasks could be avoided if it was possible to
At Tue, 16 Jan 2007 22:37:56 +0800,
Yu-Chen Wu wrote:
>
> Hi all,
> Can a buffer allocated by "vmalloc( )" be used to make DMA transmission (the
> buffer will be used by BIO structure) on X86_64 platform?
> I need a big buffer (cache) maybe 64MB or bigger, so I call vmalloc to
> allocate the
On 1/17/07, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Another obstacle would be to place the initramfs image on the same
partition as the kernel (normally, I dd kernel to /dev/mtd1).
As far as I know you can embed the initramfs into the kernel image using
CONFIG_INITRAMFS_SOURCE.
Alon Bar-Lev wrote:
On 1/17/07, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Does this make sense?
Why not add this logic into your initramfs?
Because the kernel itself is on a small flash partition (RedBoot
executes the kernel from /dev/mtd1), which is only 1572864 bytes big.
So it
On Wed, Jan 17, 2007 at 07:00:48AM -0500, David Hollis wrote:
> > 'rmmod asix' takes a really long time (45-80s) with any setting, and
> > sometimes coincides with ksoftirqd pegging (99.9% CPU) for several
> > seconds.
>
> This I haven't seen before. Does it occur even when the device is able
>
On Wed, 2007-01-17 at 09:49 +0100, Peter Zijlstra wrote:
> > They are certainly _not_ dirty pages. They are pages that have been
> > written to the server but are not yet guaranteed to have hit the disk
> > (they were only written to the server's page cache). We don't care if
> > they are paged
Since you are implementing new APIs here, have you considered doing an
aio_sendfilev to be able to send a header with the data ?
Regards
Suparna
On Wed, Jan 17, 2007 at 09:30:35AM +0300, Evgeniy Polyakov wrote:
>
> Kevent based AIO (aio_sendfile()/aio_sendfile_path()).
>
>
> The device is pretty small and has no keyboard, video card etc., so if it ever
> happens to break (can be a disk failure, but also operator who messed with
> startup scripts), it has to be opened (warranty!).
>
> These all unpleasant tasks could be avoided if it was possible to have a
>
On 1/17/07, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Does this make sense?
Why not add this logic into your initramfs?
Best Regards,
Alon Bar-Lev.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
I have a Linux (ARM) device that normally starts from /dev/sda1.
It is configured to do so via a cmdline in a RedBoot bootloader:
root=/dev/sda1
The device is pretty small and has no keyboard, video card etc., so if
it ever happens to break (can be a disk failure, but also operator who
Eliminate arch specific memory_present calls for ia64 NUMA and x86_64 NUMA by
utilizing sparse_memory_present_with_active_regions. It was boot tested
for both arches.
Acked-by: Mel Gorman <[EMAIL PROTECTED]>
Signed-off-by: Bob Picco <[EMAIL PROTECTED]>
arch/ia64/mm/discontig.c | 36
Eric W. Biederman wrote:
> "Daniel Hokka Zakrisson" <[EMAIL PROTECTED]> writes:
>
>> The test-case at the bottom causes the following recursive Oopsing on
>> 2.6.20-rc5:
>
> A few more people added to the CC who might have a clue.
>
>>
>> BUG: unable to handle kernel NULL pointer dereference at
It will execute rdmsr and wrmsr only on the cpu we need.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
arch/i386/kernel/msr.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
--- a/arch/i386/kernel/msr.c
+++ b/arch/i386/kernel/msr.c
@@ -68,7 +68,6 @@ static inline
It will execure cpuid only on the cpu we need.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpuid.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
--- a/arch/i386/kernel/cpuid.c
+++ b/arch/i386/kernel/cpuid.c
@@ -48,7 +48,6 @@ static struct class
"Daniel Hokka Zakrisson" <[EMAIL PROTECTED]> writes:
> The test-case at the bottom causes the following recursive Oopsing on
> 2.6.20-rc5:
A few more people added to the CC who might have a clue.
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 0504
> printing
On Tue, Jan 16, 2007 at 04:27:40PM -0500, Mathieu Desnoyers wrote:
> Hi,
>
> I have looked at kprobes code and have some questions for you. I would really
> like to use it to patch dynamically my marker immediate value by doing code
> patching. Using an int3 seems like the right way to handle
Hi,
1) I'm using two 2.4 based kernel modules. The first module defines a
symbol but does not EXPORT_SYSMBOL() it. Would my second module be
able to use that symbol? In 2.4? In 2.6?
2) Also, in 2.4, is it OK if I start using my device memory before
request_mem_region()?
Thanks,
Rick
-
To
On Tue, 2007-01-16 at 09:33 -0700, Eric W. Biederman wrote:
> There has not been much maintenance on sysctl in years, and as a result is
> there is a lot to do to allow future interesting work to happen, and being
> ambitious I'm trying to do it all at once :)
s390 parts look good. Kernels boots
On Tue, 2007-01-16 at 17:59 -0500, Eric Buddington wrote:
> On Mon, Jan 15, 2007 at 08:32:17PM +, David Hollis wrote:
> > Interesting. It would really be something if your devices happen to
> > work better with 0. Wouldn't make much sense at all unfortunately. If
> > 0 works, could you also
On Wed, Jan 17, 2007 at 11:26:54AM +, Seetharam Dharmosoth wrote:
> Is Linux having 'non-break interface for serial
> console' ?
No idea. Could you explain what a 'non-break interface for serial
console' is?
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab
On Wed, Jan 17, 2007 at 11:09:21AM +0100, Turbo Fredriksson wrote:
> Quoting Ken Moffat <[EMAIL PROTECTED]>:
> > Certainly, fdisk from util-linux doesn't know about mac disks, and
> > I thought the same was true for cfdisk and sfdisk. Many years ago
> > there was mac-fdisk, I think also known as
Hi all,
Is Linux having 'non-break interface for serial
console' ?
I am currently using Kernel 2.6.7.
how do we know this feature?
Thanks
Seetharam
__
Yahoo! India Answers: Share what you know. Learn something new
Hi all,
Is Linux having 'non-break interface for serial
console' ?
I am currently using Kernel 2.6.7.
how do we know this feature?
Thanks
Seetharam
__
Yahoo! India Answers: Share what you know. Learn something new
Ingo,
I see that this patch made it into -mm, so i am hoping it will
also show up in mainline fairly soon.
Thanks.
On Fri, Dec 22, 2006 at 01:19:20PM +0100, Ingo Molnar wrote:
>
> * Stephane Eranian <[EMAIL PROTECTED]> wrote:
>
> > The perfmon subsystems needs to compute per-CPU duration. It
The test-case at the bottom causes the following recursive Oopsing on
2.6.20-rc5:
BUG: unable to handle kernel NULL pointer dereference at virtual address
0504
printing eip:
c02292d4
*pde =
Oops: 0002 [#1]
PREEMPT SMP
Modules linked in:
CPU:0
EIP:0060:[]Not tainted VLI
On 1/17/07, Matheus Izvekov <[EMAIL PROTECTED]> wrote:
I just tried the firmwarekit, and here are the results, attached.
TYVM, thats a very useful tool.
I do suspect ACPI issues on my new DG965WH MOBO:-
http://www.intel.com/products/motherboard/DG965WH/index.htm
Tried with Linux-2.6.19.2.
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> Making it dependent upon CONFIG_PREEMPT seems a bit sucky. Perhaps
> pass in some "you were called from /proc/sysrq-trigger" notification?
looks quite invasive to the whole sysrq interfaces, it trickles all the
way down into sysrq.c's handler
Hello,
Since 2.6.19, I get the following Oops once a day, always with the same
process, newspipe[1] which use a lot of CPU, threads and I/O.
The kernel is patched by Grsecurity. The ext3 filesystem is on a
software RAID device (the two disks are SATA2). I tested the
hardware (RAM, SMART disks)
Hi!
I have discovered a problem with the changes applied to smbfs in 2.4.34 and
in the security backports like last Debian's 2.4 kernel update these changes
seem to be made to solve CVE-2006-5871 and they have broken symbolic links
and changed the way that special files (like devices) are seen.
Quoting Ken Moffat <[EMAIL PROTECTED]>:
> On Tue, Jan 16, 2007 at 02:27:06PM +0100, Turbo Fredriksson wrote:
>> A couple of weeks ago my 400Gb SATA disk crashed. I just
>> got the replacement, but I can't seem to be able to create
>> a filesystem on it!
>>
>> This is a PPC (Pegasos), running
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> So i think we should do the patch below - this makes reboot work even
> in atomic contexts. [...]
hm, this causes problems if KVM is not active on a VT-capable CPU: even
on CPUs with VT supported, if a VT context is not actually activated, a
vmxoff
> On Wed, 17 Jan 2007 10:39:17 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Russell King <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Jan 17, 2007 at 10:13:19AM +0100, Ingo Molnar wrote:
> > > we dont call the reboot notifiers during emergency reboot mainly because
> > > it could be called
AIO completion signal notification
The current 2.6 kernel does not support notification of user space via
an RT signal upon an asynchronous IO completion. The POSIX specification
states that when an AIO request completes, a signal can be delivered to
the application as
compat_sys_io_submit() cleanup
Cleanup compat_sys_io_submit by duplicating some of the native syscall
logic in the compat layer and directly calling io_submit_one() instead
of fooling the syscall into thinking it is called from a native 64-bit
caller.
This eliminates:
-
Make good_sigevent() non-static
Move good_sigevent() from posix-timers.c to signal.c where it belongs,
and make it non-static so that it can be used by other subsystems.
include/linux/signal.h |1 +
kernel/posix-timers.c | 17 -
kernel/signal.c
Fix the double inclusion of linux/uio.h in linux/aio.h
aio.h |1 -
1 file changed, 1 deletion(-)
Signed-off-by: Sébastien Dugué <[EMAIL PROTECTED]>
Index: linux-2.6.20-rc4-mm1/include/linux/aio.h
===
---
From: Bharata B Rao <[EMAIL PROTECTED]>
This patch provides POSIX listio support by means of a new system call.
long lio_submit(aio_context_t ctx_id, int mode, long nr,
struct iocb __user * __user *iocbpp, struct sigevent __user *event)
This system call is similar to the io_submit()
Hi,
Andrew, would you consider including this patchset in -mm for some more
testing. At least patches 1 - 4.
Patch 5 is the new listio syscall approach from Bharata B Rao which is much
cleaner than overloading sys_io_submit() with a new opcode but maybe needs some
more discussion before
> On Wed, 17 Jan 2007 00:01:58 -0800 Paul Jackson <[EMAIL PROTECTED]> wrote:
> Andrew wrote:
> > - consider going off-cpuset for critical allocations.
>
> We do ... in mm/page_alloc.c:
>
> * This is the last chance, in general, before the goto nopage.
> * Ignore cpuset if
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> Subject: [patch] call reboot notifier list when doing an emergency reboot
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> my laptop (Lenovo T60) hangs during reboot if the shutdown notifiers are
> not called. So the following command, which on other
* Alan Stern <[EMAIL PROTECTED]> wrote:
> From: Alan Stern <[EMAIL PROTECTED]>
>
> This patch (as839) implements the Kwatch (kernel-space hardware-based
> watchpoints) API for the i386 architecture. The API is explained in
> the kerneldoc for register_kwatch() in arch/i386/kernel/kwatch.c.
* Russell King <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 17, 2007 at 10:13:19AM +0100, Ingo Molnar wrote:
> > we dont call the reboot notifiers during emergency reboot mainly because
> > it could be called from atomic context and reboot notifiers are a
> > blocking notifier list. But actually
Hi,
On Tue, 2007-01-09 at 23:52 +0300, Sergey Vlasov wrote:
[snip excellent analysis]
> Seems that grabbing i_mutex in ntfs_put_inode() is not safe after all
> (and lockdep cannot see this deadlock possibility, because one of
> waits is __wait_on_freeing_inode - not a standard locking primitive).
[EMAIL PROTECTED] wrote:
[...]
> +Tips on when/where to use the above attributes:
> + o The module_init()/module_exit() functions (and all
> + initialization functions called _only_ from these)
> + should be marked __init/__exit.
> +
> + o Do not mark the struct pci_driver.
> +
On Wed, 2007-01-17 at 10:12 +0100, Pavel Machek wrote:
> Hi!
>
> > These patches implement the basic infrastructure to allow swap over
> > networked
> > storage.
> >
> > The basic idea is to reserve some memory up front to use when regular memory
> > runs out.
> >
> > To bound network
On Wed, Jan 17, 2007 at 10:13:19AM +0100, Ingo Molnar wrote:
> we dont call the reboot notifiers during emergency reboot mainly because
> it could be called from atomic context and reboot notifiers are a
> blocking notifier list. But actually the kernel is often perfectly
> reschedulable in
Subject: [patch] call reboot notifier list when doing an emergency reboot
From: Ingo Molnar <[EMAIL PROTECTED]>
my laptop (Lenovo T60) hangs during reboot if the shutdown notifiers are
not called. So the following command, which on other systems i use as a
quick way to reboot into a new kernel:
Hi!
> These patches implement the basic infrastructure to allow swap over networked
> storage.
>
> The basic idea is to reserve some memory up front to use when regular memory
> runs out.
>
> To bound network behaviour we accept only a limited number of concurrent
> packets and drop those
The code that enables ACPI mode hasn't really changed since before 2.6.12 --
unless udelay() has changed beneath us...
So if you are going to test an old version of Linux, you should start before
then.
Perhaps you can try this debug patch on top of 2.6.19 and send along the dmesg?
(also, please
On Wed, 2007-01-17 at 07:54 +0300, Evgeniy Polyakov wrote:
> On Tue, Jan 16, 2007 at 05:08:15PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
> wrote:
> > On Tue, 2007-01-16 at 18:33 +0300, Evgeniy Polyakov wrote:
> > > On Tue, Jan 16, 2007 at 02:47:54PM +0100, Peter Zijlstra ([EMAIL
> > >
Hi,
This latest patch is an adaptation of the sys_futex64 syscall provided in -rt
patch (originally written by Ingo). It allows the use of 64bit futex.
I have re-worked most of the code to avoid the duplication of the code.
It does not provide the functionality for all architectures, and thus,
Hi,
This patch provides the futex_requeue_pi functionality.
This provides an optimization, already used for (normal) futexes, to be used for
PI-futexes.
This optimization is currently used by the glibc in pthread_broadcast, when
using "normal" mutexes. With futex_requeue_pi, it can be used
> i think your patches #1...#7 are must-haves for v2.6.20, while #8-#11
> could be delayed to v2.6.21?
Indeed 1-7 are fixes while 8-11 are only cleanups not changing behavior.
Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi,
This patch modifies futex_wait() to use an hrtimer + schedule() in place of
schedule_timeout() in an RT kernel.
More details in the patch header.
This patch modifies futex_wait() to use an hrtimer +
Hi,
Today, all threads waiting for a given futex are woken in FIFO order (first
waiter woken first) instead of priority order.
This patch makes use of plist (pirotity ordered lists) instead of simple list in
futex_hash_bucket.
All non-RT threads are stored with priority MAX_RT_PRIO, causing
Hi,
Today, there are several functionalities or improvements about futexes
included
in -rt kernel tree, which, I think, it make sense to have in mainline.
Among them, there are:
* futex use prio list : allows RT-threads to be woken in priority order
instead of FIFO order.
*
On Wed, January 17, 2007 06:31, Ingo Molnar wrote:
>
> * Rui Nuno Capela <[EMAIL PROTECTED]> wrote:
>
>> Building this already with -rt5, still gives:
>> ...
>> LD arch/i386/boot/compressed/vmlinux
>> OBJCOPY arch/i386/boot/vmlinux.bin
>> BUILD arch/i386/boot/bzImage
>> Root device is (3,
On Wed, 2007-01-17 at 01:15 -0500, Trond Myklebust wrote:
> On Wed, 2007-01-17 at 03:41 +0100, Peter Zijlstra wrote:
> > On Tue, 2007-01-16 at 17:27 -0500, Trond Myklebust wrote:
> > > On Tue, 2007-01-16 at 23:08 +0100, Peter Zijlstra wrote:
> > > > Subject: nfs: fix congestion control
> > > >
>
101 - 200 of 414 matches
Mail list logo
