On Apr 10 2007 11:22, Tom Strader wrote:
console::sysinit:/etc/init.d/rcS
console::respawn:/sbin/getty -L 115200 /dev/ttyS0 vt100
Now I can type on the console and characters are echoed back, pressing
ctrl-c echoes: uart_flush_buffer(0) called so the code is still
running, but I am not sure
On Apr 11 2007 20:58, Milind Arun Choudhary wrote:
remove SPIN_LOCK_UNLOCKED, use DEFINE_SPINLOCK instead
Don't we have some more places where spinlocks could be janitorified?
Otherwise, ok!
Jan
--
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Jan == Jan Engelhardt [EMAIL PROTECTED] writes:
Jan On Apr 10 2007 23:54, Gene Heskett wrote:
So fix tar to not do silly things.
Kernel major:minor numbers are not stable.
YOU Tell that to the tar/star people, they are flabbergasted that its
not stable. It apparently is for every other
Eric Dumazet wrote:
Please check kernel/sys.c:k_getrusage() to see how getrusage() has to
sum *lot* of individual fields to get precise process numbers (even
counting stats for dead threads)
Thanks for helping me and for this link. But it is not enough clear for
me what do you mean at
[EMAIL PROTECTED] wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Fix a deadlock when the interface s configured down and
the watchdog tack is sleeping on rtnl_lock.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/cxgb3/cxgb3_main.c |4 +++-
1 files changed, 3 insertions(+), 1
Bill Davidsen wrote:
[snip]
Your description is not very clear about the semantic of your stats.
You currently returns stats only for thread(s) (not process as you
claimed)
I'm not sure if you were confused by his use of thread in parenthesis,
but isn't the whole point of this to see
Nope. Terminal is set correctly, the kernel is outputting messages, the
command line arguments sent to the kernel have 115200 set. What would
happen if the getty was not started correctly? Would the echoes in rcS
still appear? I feel like it may be related to the getty and userspace
prints due
On Wed, 11 Apr 2007, Jan Engelhardt wrote:
On Apr 11 2007 05:47, Robert P. J. Day wrote:
On Apr 11 2007 05:25, Robert P. J. Day wrote:
On Wed, 11 Apr 2007, Jan Engelhardt wrote:
On Apr 11 2007 03:58, Robert P. J. Day wrote:
A CONFIG_EMBEDDED bug. This should perhaps be changed.
On Wed, Apr 11, 2007 at 12:30:48PM +0400, Ivan Kokshaysky wrote:
+VGA_MAP_MEM(unsigned long xaddr, unsigned int size)
+{
+ /* Create a new VGA ioport resource WRT the hose it is on. */
+ if (pci_vga_hose pci_vga_hose-index) {
+ static struct resource alpha_vga =
+
Dump core after a panic. This will provide better debugging
information than is currently available.
Signed-off-by: Jeff Dike [EMAIL PROTECTED]
--
arch/um/include/os.h |1 +
arch/um/kernel/um_arch.c |2 +-
arch/um/os-Linux/util.c |6 ++
3 files changed, 8 insertions(+), 1
Code running on the initial UML stack can't receive or process signals
since current must be valid when IRQs are handled, and there is no
current for this stack.
So, instead of using UML_LONGJMP and UML_SETJMP, which are careful
to save and restore signal state, and, as a side-effect, handle any
These are 2.6.22 material. Two of them are improvements to the block
driver, one causes UML to dump core on a panic, and the other is a bug
fix.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line unsubscribe
Instead of writing entire structures between UML and the I/O thread,
we send pointers. This cuts down on the amount of data being copied
and possibly allows more requests to be pending between the two.
This requires that the requests be kmalloced and freed instead of
living on the stack.
Send as many I/O requests to the I/O thread as possible, even though
it will still only handle one at a time. This provides an opportunity
to reduce latency by starting one request before the previous one has
been finished in the driver.
Request handling is somewhat modernized by requesting sg
Zhao Forrest wrote:
On 4/11/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
On Wed, 2007-04-11 at 02:53 -0700, Paul Jackson wrote:
I'm confused - which end of ths stack is up?
cpuset_exit doesn't call do_exit, rather it's the other
way around. But put_files_struct doesn't call do_exit,
Oleg Nesterov [EMAIL PROTECTED] writes:
On 04/10, Eric W. Biederman wrote:
static int kthread(void *_create)
{
struct kthread_create_info *create = _create;
int (*threadfn)(void *data);
void *data;
-sigset_t blocked;
int ret = -EINTR;
-
On Apr 11 2007 08:57, Tom Strader wrote:
Nope. Terminal is set correctly, the kernel is outputting messages, the
command line arguments sent to the kernel have 115200 set. What would
happen if the getty was not started correctly?
I'd say you have no login prompt then after rcS finished.
Thanks
Oleg Nesterov [EMAIL PROTECTED] writes:
On 04/10, Eric W. Biederman wrote:
+int kthreadd(void *unused)
+{
+/* Setup a clean context for our children to inherit. */
+kthreadd_setup();
+
+current-flags |= PF_NOFREEZE;
+
+for (;;) {
+
GM == Gerhard Mack [EMAIL PROTECTED] writes:
GM On Wed, 4 Apr 2007, Alan Cox wrote:
You don't get machines with 64 ethernet ports on add-in cards.
There are good reasons for the naming schemes in use.
GM If they made them I'd build one.
Indeed, port density is disappointingly poor in modern
Coming from a simplify things pov:
On Fri, Apr 06, 2007 at 04:32:24PM -0700, [EMAIL PROTECTED] wrote:
struct container {
unsigned long flags;/* unsigned long so bitops work */
/*
- * Count is atomic so can incr (fork) or decr (exit) without a lock.
- */
Hi Adrian,
first front off: thanks for the phantastic 2.6.16 stable maintenance.
Currently I wonder if you have any plan for doing the 2.6.16 review
for let's say years, or if you soon pick some new series such as
2.6.20 or so for long-term maintenance.
I ask because I wonder if I should wait a
On 4/11/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
On Wed, 2007-04-11 at 17:53 +0800, Zhao Forrest wrote:
I got some new information:
Before soft lockup message is out, we have:
[EMAIL PROTECTED] home]# cat /proc/slabinfo |grep buffer_head
buffer_head 10927942 10942560120 32
The locking of the xtime_lock around the cpu notifier is unessesary now. At one
time the tsc was used after a frequency change for timekeeping, but the re-write
of timekeeping no longer uses the TSC unless the frequency is constant.
The variables that are changed in this section of code had also
On Wed, Apr 11, 2007 at 12:28:41PM +0400, Ivan Kokshaysky wrote:
- __asm__(ctlz %1, %0 : =r(vector) : r(mask));
+ __asm__(.arch ev67; ctlz %1, %0 : =r(vector) : r(mask));
This should use __kernel_ctlz, and we should use
#ifdef __alpha_cix__
# if __GNUC__ == 3
John Anthony Kazos Jr. [EMAIL PROTECTED] writes:
I think that's especially true. If a user begins with a single full disk
for their entire filesystem, uses tar to backup, and then later adds a
second disk, copies everything from /usr and /home onto partitions there
(making sure to preserve
On Wed, 2007-04-11 at 18:10 +0800, Zhao Forrest wrote:
On 4/11/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
On Wed, 2007-04-11 at 02:53 -0700, Paul Jackson wrote:
I'm confused - which end of ths stack is up?
cpuset_exit doesn't call do_exit, rather it's the other
way around. But
Thanks.
However, the PRIO qdisc still uses the priority in the bands for
dequeueing priority, and will feed the queues on the NIC.
The e1000, and any other multiqueue NIC, will schedule Tx
based on how
the PRIO qdisc feeds the queues. So the only priority here is the
dequeuing
Jan Engelhardt wrote:
On Apr 11 2007 07:42, Al Boldi wrote:
Also, I don't think it's necessary to touch any of the depends on; keep
them as is, as they don't hurt staying that way, and may actually be
necessary under certain circumstances. (see EMBEDDED)
Simplifying the depends lines is a
On 4/10/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Tue, 10 Apr 2007 16:53:53 -0700 (PDT) [EMAIL PROTECTED] (Ken Chen) wrote:
+ } while (head != cmpxchg(ring-head, head, head + 1));
A hasty grep indicates that only 14 out of 23 architectures implement
cmpxchg().
Sorry I wasn't
Waskiewicz Jr, Peter P wrote:
Packets will only be dequeued from a band if the associated
subqueue is active, which moves the decision from prio to the
driver, no?
What policy does e1000 use for scheduling its internal queues?
E1000 is handed the skb's from PRIO to whichever queue the PRIO
On Apr 11 2007 18:53, Stefan Richter wrote:
Jan Engelhardt wrote:
On Apr 11 2007 07:42, Al Boldi wrote:
Also, I don't think it's necessary to touch any of the depends on; keep
them as is, as they don't hurt staying that way, and may actually be
necessary under certain circumstances. (see
On Apr 11 2007 18:43, Krzysztof Halasa wrote:
John Anthony Kazos Jr. [EMAIL PROTECTED] writes:
I think that's especially true. If a user begins with a single full disk
for their entire filesystem, uses tar to backup, and then later adds a
second disk, copies everything from /usr and /home
On Wed, Apr 11, 2007 at 06:53:37PM +0200, Stefan Richter wrote:
Jan Engelhardt wrote:
On Apr 11 2007 07:42, Al Boldi wrote:
Also, I don't think it's necessary to touch any of the depends on; keep
them as is, as they don't hurt staying that way, and may actually be
necessary under certain
Richard Henderson wrote:
On Wed, Apr 11, 2007 at 12:30:48PM +0400, Ivan Kokshaysky wrote:
+VGA_MAP_MEM(unsigned long xaddr, unsigned int size)
+{
+ /* Create a new VGA ioport resource WRT the hose it is on. */
+ if (pci_vga_hose pci_vga_hose-index) {
+ static
Here are some USB fixes against 2.6.21-rc6.
They fix a reported regression with the ehci driver, and allow a new
device to work properly with the usb-storage driver.
The usb-storage patch has been in the -mm releases.
Please pull from:
* Russell King ([EMAIL PROTECTED]) wrote:
On Tue, Apr 10, 2007 at 06:36:58PM -0400, Mathieu Desnoyers wrote:
Defines the linker marcro EXTRA_RWDATA for marker data section. It
puts the marker data in a separate section that will not pollute the
normal .data section, which minimize the cache
On Wed, 2007-04-11 at 11:05 -0400, Jeff Mahoney wrote:
Commit f50b6f8691cae2e0064c499dd3ef3f31142987f0 introduced a
race in autofs4 between autofs_lookup_unhashed() and
autofs_dentry_release().
autofs_dentry_release() ends up clearing the -dentry and -inode
members of autofs_info
SPIN_LOCK_UNLOCKED cleanup,use DEFINE_SPINLOCK instead
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
---
ieee1394_transactions.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ieee1394/ieee1394_transactions.c
b/drivers/ieee1394/ieee1394_transactions.c
The recent patch cleanup up, among other things, msr.h, used a script
to canonicalize the formatting. Unfortunately it also formatted the
EFER bit numbers as 32-bit expanded hex, which is ridiculous. Clean up.
Signed-off-by: H. Peter Anvin [EMAIL PROTECTED]
diff -urN --exclude 'o.*' --exclude
On Wed, Apr 11, 2007 at 06:34:32PM +0200, Rene Rebe wrote:
Hi Adrian,
Hi René,
first front off: thanks for the phantastic 2.6.16 stable maintenance.
Currently I wonder if you have any plan for doing the 2.6.16 review
for let's say years, or if you soon pick some new series such as
2.6.20
First, I'll NAK this and all AIO patches until the patch description
says that it's been run through the regression tests that we've started
collecting in autotest. They're trivial to run, never fear:
cd /usr/local
svn checkout svn://test.kernel.org/autotest/trunk/client autotest
cd autotest
On Thu, 2007-04-12 at 01:49 +0800, Ian Kent wrote:
On Wed, 2007-04-11 at 11:05 -0400, Jeff Mahoney wrote:
Commit f50b6f8691cae2e0064c499dd3ef3f31142987f0 introduced a
race in autofs4 between autofs_lookup_unhashed() and
autofs_dentry_release().
autofs_dentry_release() ends up
On Wed, 11 Apr 2007 13:51:11 -0400
Mathieu Desnoyers [EMAIL PROTECTED] wrote:
What's this marker stuff about?
Hi Russel,
Here is an overview :
I am told that the systemtap developers plan to (or are) using this
infrastructure.
If correct: what is their reason for preferring it over
[EMAIL PROTECTED] napisał(a):
The mm snapshot broken-out-2007-04-11-02-24.tar.gz has been uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-04-11-02-24.tar.gz
It contains the following patches against 2.6.21-rc6:
After a few seconds of running
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-linus
to receive the following updates:
drivers/net/cxgb3/common.h |7 +-
drivers/net/cxgb3/cxgb3_main.c | 16 ++--
On Thu, 2007-04-12 at 02:00 +0800, Ian Kent wrote:
On Thu, 2007-04-12 at 01:49 +0800, Ian Kent wrote:
On Wed, 2007-04-11 at 11:05 -0400, Jeff Mahoney wrote:
Commit f50b6f8691cae2e0064c499dd3ef3f31142987f0 introduced a
race in autofs4 between autofs_lookup_unhashed() and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Kent wrote:
On Thu, 2007-04-12 at 02:00 +0800, Ian Kent wrote:
On Thu, 2007-04-12 at 01:49 +0800, Ian Kent wrote:
On Wed, 2007-04-11 at 11:05 -0400, Jeff Mahoney wrote:
Commit f50b6f8691cae2e0064c499dd3ef3f31142987f0 introduced a
race in
On Wed, 2007-04-11 at 14:13 -0400, Jeff Mahoney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Kent wrote:
On Thu, 2007-04-12 at 02:00 +0800, Ian Kent wrote:
On Thu, 2007-04-12 at 01:49 +0800, Ian Kent wrote:
On Wed, 2007-04-11 at 11:05 -0400, Jeff Mahoney wrote:
Commit
On Wed, 11 Apr 2007 12:39:05 +0200
Andi Kleen [EMAIL PROTECTED] wrote:
The next kernel patch for Perfmon will not make use of the idle notification
anymore on any platform.
What do you use instead?
I've been actually thinking to add idle notifier support to oprofile to
correct
for
Sorry I wasn't thorough enough. And partially because I was worried
about changing structure type for user space facing struct aio_ring.
Now that I looked through all arches, it looks safe as all arch's
atomic_t has the same size as int.
Here is the updated patch.
@@ -144,7 +144,7 @@
Jiri Slaby wrote:
Corentin CHARY napsal(a):
Le Wednesday 11 April 2007 11:33:48 Jiri Slaby, vous avez écrit :
asus_acpi, support F2JE model
Just use the new asus-laptop driver =)
(see acpi4asus-0.40)
code seems good, but this is not so good:
#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,20)
SPIN_LOCK_UNLOCKED cleanup,use DEFINE_SPINLOCK or
__SPIN_LOCK_UNLOCKED where ever appropriate.
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
--
kernel/irq.c |2 +-
kernel/rtas.c |2 +-
oprofile/op_model_cell.c |2 +-
platforms/cell/spu_base.c |
Andrew Morton [EMAIL PROTECTED] writes:
argh. Your description freely confuddles the terms kernel thread and
kthread. Can we not do that? Henceforth the term kernel thread refers
to something which was started with kernel_thread() and kthread refers to
something which was created by
Hi,
I send a reworked version of the patch.
Removed from the first version:
- any sign of '.' as substitute glyph
- don't ignore zero-width characters (except for a few zero-width spaces
that are ignored in the current kernel too). However, I kept the code
organized and commented so
Jan Engelhardt wrote:
On Apr 11 2007 07:42, Al Boldi wrote:
Jan Engelhardt wrote:
Correct, no oversight here; but it may be more meaningful, if you could
default select child-options based on the parent-state, like HW_RANDOM.
A symbol will already have the 'magic' you describe if its
On 4/11/07, Zach Brown [EMAIL PROTECTED] wrote:
Sorry I wasn't thorough enough. And partially because I was worried
about changing structure type for user space facing struct aio_ring.
Now that I looked through all arches, it looks safe as all arch's
atomic_t has the same size as int.
On Wed, 2007-04-11 at 12:44 +0200, Miklos Szeredi wrote:
1. clone the master namespace.
2. in the new namespace
move the tree under /share/$me to /
for each ($user, $what, $how) {
move /share/$user/$what to /$what
if ($how == slave) {
Currently there is a circular reference between work queue initialization
and kthread initialization. This prevents the kthread infrastructure from
initializing until after work queues have been initialized.
We want the properties of tasks created with kthread_create to be as close
as possible
On Mittwoch, 11. April 2007, Danny Kukawka wrote:
Jiri Slaby wrote:
Corentin CHARY napsal(a):
Le Wednesday 11 April 2007 11:33:48 Jiri Slaby, vous avez écrit :
asus_acpi, support F2JE model
Just use the new asus-laptop driver =)
(see acpi4asus-0.40)
code seems good, but this is not
On 03-Apr-07, John Stoffel wrote:
Sorry, I've been away for the past 10+ days and not reading email at
all.
NP. Happens to me too (as you can see).
Olaf Try changing the order of the console= parameters:
Olaf kernel ... console=ttyS1,96008N1 console=tty0
This isn't good for me,
Egmont Koblinger wrote:
+static int is_zero_width(long ucs)
+{
+ static const struct interval zero_width[] = {
/* lots */
+ };
I'm still unhappy about these large search tables in the kernel, not
because they take a huge amount of space (it's not that much), but
because they're
When using either the unpatched 2.6.21_rc5 or SUSEs patched
2.6.21_rc6_git3-20070410174235 on a SUSE-10.2 x86_64 system the parallel port
doesn't work right. If I cat some_asciifile /dev/lp0 the output on my
Epson Stylus Color 880 is unreadable. cat /dev/zero /dev/lp0 creates
random
Uytterhoeven, Geert wrote:
Hi,
Documentation/ioctl/hdio.txt says:
| This document attempts to describe the ioctl(2) calls supported by
| the HD/IDE layer. These are by-and-large implemented (as of Linux 2.6)
| in drivers/ide/ide.c and drivers/block/scsi_ioctl.c
However,
On Wed, 11 Apr 2007 19:02:27 +0400
Pavel Emelianov [EMAIL PROTECTED] wrote:
Provides a per-container statistics concerning the numbers of tasks
in various states, system and user times, etc. Patch is inspired
by Paul's example of the used CPU time accounting. Although this
patch is
When a kernel thread calls daemonize, instead of reparenting the thread to
init reparent the thread to kthreadd next to the threads created by
kthread_create.
This is really just a stop gap until daemonize goes away, but it does
ensure no kernel threads are under init and they are all in one
Andrew Morton wrote:
On Wed, 11 Apr 2007 09:55:49 +0200 (MEST) Jan Engelhardt [EMAIL PROTECTED]
wrote:
Any hints who should get it, or would you take care of it?
Send it to me. Send everything to me, if you actually want it applied :(
I'll get this stuff off lkml, when I get that far.
Linux Kernel Markers documentation fix typo and use ARRAY_SIZE
Following comments from Randy Dunlap. Applies on top of the
linux-kernel-markers-documentation-markers-update-documentation patch.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
--- a/Documentation/marker.txt
+++
On Apr 11 2007 20:28, Egmont Koblinger wrote:
I send a reworked version of the patch.
Removed from the first version:
- any sign of '.' as substitute glyph
- don't ignore zero-width characters (except for a few zero-width spaces
that are ignored in the current kernel too). However, I
These patches build on the patchset labelled AF_RXRPC socket family and AFS
rewrite. The patches are also available for http download.
Firstly, the patches fix a number of bugs in AF_RXRPC:
http://people.redhat.com/~dhowells/rxrpc/09-af_rxrpc-own-workqueues.diff
Fix a deadlock in the give-up-callback aggregator dispatcher work item whereby
the aggregator runs on keventd as does timed autounmount, thus leading to the
unmount blocking keventd whilst waiting for keventd to run the aggregator when
the give-up-callback buffer is full.
Signed-Off-By: David
Make a couple of fixes to AF_RXRPC:
(1) The dead call timeout is shortened to 2 seconds. Without this, each
completed call sits around eating up resources for 10 seconds. The calls
need to hang around for a little while in case duplicate packets appear,
but 10 seconds is
Make the AF_RXRPC module use its own workqueues with their own per-CPU threads.
Currently it uses keventd to do the following tasks, amongst others:
(*) Security negotiation
(*) Packet encryption and decryption
(*) Packet resending
(*) ACK, abort and busy packet generation
(*) Timeout
Make two changes to the AF_RXRPC key handling to make it easier for AFS to
use:
(1) Export key_type_rxrpc so that AFS can request keys of this type.
(2) Make it possible to have keys that represent no security. These are
created by instantiating the keys with no data.
Signed-Off-By:
Handle multiple mounts of an AFS superblock correctly, checking to see whether
the superblock is already initialised after calling sget() rather than just
unconditionally stamping all over it.
Also delete the silent parameter to afs_fill_super() as it's not used and
can, in any case, be obtained
Permit a key to be cached in the nameidata struct so that it only needs to be
looked up once when doing the sequence of d_revalidate(), permission(),
follow_link() and lookup() calls involved in a pathwalk.
This is used by the AFS filesystem to avoid repeatedly having to call
request_key(). Once
On Wed, 11 Apr 2007 11:00:38 -0700
Zach Brown [EMAIL PROTECTED] wrote:
- /* Compensate for the ring buffer's head/tail overlap entry */
- nr_events += 2; /* 1 is required, 2 for good luck */
+ /* round nr_event to next power of 2 */
+ nr_events = roundup_pow_of_two(nr_events);
Correctly alter the relocation state after update is complete by switching it
from Updating to Valid.
Also display the record state in the vlocation database proc file.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
fs/afs/proc.c | 15 +--
fs/afs/vlocation.c |4 +++-
On Wed, 11 Apr 2007 20:03:17 +0200
Michal Piotrowski [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] napisa__(a):
The mm snapshot broken-out-2007-04-11-02-24.tar.gz has been uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-04-11-02-24.tar.gz
It
On Wed, 11 Apr 2007 12:27:59 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
+ strcpy(tsk-comm, kthreadd);
We have this dopey set_task_comm() thing which is there to avoid
races when userspace is looking at this task's name via /proc.
It obviously doesn't matter in this case, but I
Danny Kukawka napsal(a):
On Mittwoch, 11. April 2007, Danny Kukawka wrote:
Jiri Slaby wrote:
Corentin CHARY napsal(a):
Le Wednesday 11 April 2007 11:33:48 Jiri Slaby, vous avez écrit :
asus_acpi, support F2JE model
Just use the new asus-laptop driver =)
(see acpi4asus-0.40)
code seems
Maxim Uvarov a écrit :
Eric Dumazet wrote:
Please check kernel/sys.c:k_getrusage() to see how getrusage() has to
sum *lot* of individual fields to get precise process numbers (even
counting stats for dead threads)
Thanks for helping me and for this link. But it is not enough clear for
On Wednesday, 11 April 2007 00:20, Venki Pallipadi wrote:
On Mon, Apr 09, 2007 at 07:40:52PM +0200, Rafael J. Wysocki wrote:
On Monday, 9 April 2007 18:14, Pallipadi, Venkatesh wrote:
-Original Message-
From: Rafael J. Wysocki [mailto:[EMAIL PROTECTED]
Sent: Monday, April
* Andrew Morton ([EMAIL PROTECTED]) wrote:
On Wed, 11 Apr 2007 13:51:11 -0400
Mathieu Desnoyers [EMAIL PROTECTED] wrote:
What's this marker stuff about?
Hi Russel,
Here is an overview :
I am told that the systemtap developers plan to (or are) using this
infrastructure.
On 04/11, Eric W. Biederman wrote:
@@ -435,8 +436,12 @@ static void __init setup_command_line(char *command_line)
static void noinline rest_init(void)
__releases(kernel_lock)
{
+ int pid;
kernel_thread(init, NULL, CLONE_FS | CLONE_SIGHAND);
numa_default_policy();
On 4/11/07, Zach Brown [EMAIL PROTECTED] wrote:
First, I'll NAK this and all AIO patches until the patch description
says that it's been run through the regression tests that we've started
collecting in autotest. They're trivial to run, never fear:
OK. I will run those regression tests.
On Wednesday, 11 April 2007 16:36, Oleg Nesterov wrote:
On 04/11, Gautham R Shenoy wrote:
On Wed, Apr 11, 2007 at 03:48:05PM +0400, Oleg Nesterov wrote:
On 04/11, Gautham R Shenoy wrote:
On Wed, Apr 11, 2007 at 12:13:34PM +0200, Rafael J. Wysocki wrote:
It should be
Ken uses the other (superior!) way of implementing ringbuffers: the head
and tail pointers (the naming of which AIO appears to have reversed) are
not constrained to the ringsize - they are simply allowed to wrap through
0xfff.
A-ha! That sure sounds great.
I'd be happy to see the kernel
On Wednesday 11 April 2007, John Stoffel wrote:
Jan == Jan Engelhardt [EMAIL PROTECTED] writes:
Jan On Apr 10 2007 23:54, Gene Heskett wrote:
So fix tar to not do silly things.
Kernel major:minor numbers are not stable.
YOU Tell that to the tar/star people, they are flabbergasted that
its
After suffering some days from a not|mis configured tmpfs,
As the OOM killer is not Posix,
Better than to kill processes would be to resize tmpfs, to use tmpfs empty
space.
I'm using kernel 2.6.20.4. If someone ask I'll send a test application.
-
To unsubscribe from this list: send the
On Wed, Apr 11, 2007 at 08:10:37PM +0100, David Howells wrote:
Add security support to the AFS filesystem. Kerberos IV tickets are
added as RxRPC keys are added to the session keyring with the klog
program. open() and other VFS operations then find this ticket with
request_key() and either
On Wednesday 11 April 2007, Jan Engelhardt wrote:
On Apr 10 2007 23:54, Gene Heskett wrote:
So fix tar to not do silly things.
Kernel major:minor numbers are not stable.
YOU Tell that to the tar/star people, they are flabbergasted that its
not stable. It apparently is for every other OS tar can
Oleg Nesterov [EMAIL PROTECTED] writes:
On 04/11, Eric W. Biederman wrote:
@@ -435,8 +436,12 @@ static void __init setup_command_line(char
*command_line)
static void noinline rest_init(void)
__releases(kernel_lock)
{
+int pid;
kernel_thread(init, NULL, CLONE_FS |
On Mittwoch, 11. April 2007, Jiri Slaby wrote:
Danny Kukawka napsal(a):
Btw. looks as if a new version of the driver (v0.41) is already in the
mm-tree.
Good to hear, I've got a look only to .21-rc6-mm1, where are no changes like
this (there is 0.30).
found in the latest mm snapshot
On Wed, Apr 11, 2007 at 12:28:26PM -0700, Ken Chen wrote:
I have mixed feelings. I think the userspace getevents support was
poorly designed and the simple fact that we've gone this long without it
says just how desperately the feature isn't needed.
I kept on getting requests from
I have mixed feelings. I think the userspace getevents support was
poorly designed and the simple fact that we've gone this long without it
says just how desperately the feature isn't needed.
I kept on getting requests from application developers who want that
feature. My initial patch
On Wed, Apr 11, 2007 at 02:23:31AM -0300, Pedro wrote:
After suffering some days from a not|mis configured tmpfs,
As the OOM killer is not Posix,
Better than to kill processes would be to resize tmpfs, to use tmpfs empty
space.
Will not work, because tmpfs does not use any memory
Hi!
I hope you like it. :)
Well, more or less... but you need signed-off-by line, and
@@ -70,6 +70,16 @@
* malformed UTF sequences represented as sequences of replacement glyphs,
* original codes or '?' as a last resort if replacement glyph is undefined
* by Adam Tla/lka [EMAIL
2.6.21-rc6-mm1 locks up during boot.
The last message is:
usbcore: registered new interface driver hiddev
Then it hangs so hard that not even sysrq+B have any effect.
With 2.6.18-rc5-mm1, the next messages I normally get are:
usbcore: registered new interface driver usbhid
On 04/11, Eric W. Biederman wrote:
Oleg Nesterov [EMAIL PROTECTED] writes:
On 04/11, Eric W. Biederman wrote:
@@ -435,8 +436,12 @@ static void __init setup_command_line(char
*command_line)
static void noinline rest_init(void)
__releases(kernel_lock)
{
+ int pid;
On Wed, 11 Apr 2007 09:55:18 -0400
Joseph Fannin [EMAIL PROTECTED] wrote:
On Tue, 2007-04-10 at 15:00 -0400, Reiner Sailer wrote:
Joseph,
we cannot reproduce the BUG you report. We have identified a potential
source (spinlock around mutex_init). I have attached a small patch that
601 - 700 of 866 matches
Mail list logo
