Oleg Nesterov [EMAIL PROTECTED] writes:
On 12/05, Eric W. Biederman wrote:
This modifies do_wait and eligible_child to take a pair of
enum pid_type and struct pid *pid to precisely specify what
set of processes are eligible to be waited for, instead of the
raw pid_t value from sys_wait4.
On Tue, Dec 04, 2007 at 04:25:43PM -0500, Liam Howlett wrote:
This patch removes the rpc sigmask code and changes the
out_of_line_wait_on_bit and wait_on_bit calls in the sched.c file to
use TASK_KILLABLE. The result of this patch is the ability to kill
commands issued to a dead NFS mount by
On Thu, 6 Dec 2007 10:52:42 -0500 Rik van Riel [EMAIL PROTECTED] wrote:
On Thu, 6 Dec 2007 03:55:11 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
- We a-priori decide to limit a particular stack's peak memory usage to
1MB
- We empirically discover that the maximum amount of memory
Phillip Susi wrote:
Al Boldi wrote:
IOW, git currently only implements the server-side use-case, but fails
to deliver on the client-side. By introducing a git-client manager that
handles the transparency needs of a single user, it should be possible
to clearly isolate update semantics
On Thu, 6 Dec 2007 09:34:32 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
That's all rather handwavy and misses a lot of details and might be
inaccurate too. Probably sufficient to just work out by hand the amount of
memory which the network stack will need to allocate. I expect it'll be
two
On Thu, 2007-12-06 at 11:01 +0100, Jan Blunck wrote:
Rather than give each _dirent_ an offset, could we give each sub-mount
an offset? Let's say we have three members comprising a union mount
directory. The first has 100 dirents, the second 200, and the third
10,000. When the first
Andrew Morton wrote:
On Thu, 06 Dec 2007 09:21:53 +0100 Giacomo Catenazzi [EMAIL PROTECTED]
wrote:
Andrew Morton wrote:
On Mon, 3 Dec 2007 19:00:25 GMT Linux Kernel Mailing List
linux-kernel@vger.kernel.org wrote:
Gitweb:
Kamalesh Babulal wrote:
Hi Andrew,
The 2.6.24-rc4-mm1 kernel build fails with build failure,
CC drivers/char/hvcs.o
drivers/char/hvcs.c: In function ‘hvcs_open’:
drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation mark
make[2]: *** [drivers/char/hvcs.o] Error
This modifies do_wait and eligible child to take a pair of
enum pid_type and struct pid *pid to precisely specify what
set of processes are eligible to be waited for, instead of the
raw pid_t value from sys_wait4.
This fixes a bug in sys_waitid where you could not wait for children
in just
Hi all,
It's probably only me, but I can't connect to a kgdb host because
of bouncing ICMP unreachables. I'll be glad if you could take a look
to see if it's a bug or not.
Details:
- running a cloned version of kgdb_2.6.23 branch of Jason's
Hi David-
On Dec 5, 2007, at 8:22 PM, David Howells wrote:
Chuck Lever [EMAIL PROTECTED] wrote:
I don't see how persistent local caching means we can no longer
ignore (a)
and (b) above. Can you amplify this a bit?
How about I put it like this. There are two principal problems to
be
On Thu, Dec 06, 2007 at 08:22:15PM +0200, Ramagudi Naziir wrote:
Hi all,
It's probably only me, but I can't connect to a kgdb host because
of bouncing ICMP unreachables. I'll be glad if you could take a look
to see if it's a bug or not.
Details:
- running a cloned version of kgdb_2.6.23
Hi,
this mail sums up some discussion about special code for early initialisation
of OHCI-1394 controllers to enable their use for remote debugging over FireWire
using physical DMA. The thread started on linux-kernel and Stefan Richter
asked to Cc also linux1394-devel for the review of
Just forgot to mention:
dmesg gives nothing (/var/log/messages)
the global X log aswell
and in the users .xsession-errors I have:
amarokapp: Fatal IO error: client killed
kdesktop: Fatal IO error: client killed
konqueror: Fatal IO error: client killed
The application 'xchat' lost its connection
On 12/06, Eric W. Biederman wrote:
+static struct pid *task_pid_type(struct task_struct *task, enum pid_type
type)
+{
+ struct pid *pid = NULL;
+ if (type == PIDTYPE_PID)
+ pid = task-pids[type].pid;
+ else if (type PIDTYPE_MAX)
+ pid =
Hello!
Excuse my bad english, I am no native speaker. And please CC me, as I am
not subscribed!
I am running an amd64 system with a stable gentoo. Today I upgraded to
the kernel 2.6.22 and noticed many programs to disappear.
I use a kde desktop (3.5.7) and when amarok or kmail crash, normaly
Greg KH wrote:
On Thu, Dec 06, 2007 at 11:49:59PM +0530, Balbir Singh wrote:
Kamalesh Babulal wrote:
Hi Andrew,
The 2.6.24-rc4-mm1 kernel build fails with build failure,
CC drivers/char/hvcs.o
drivers/char/hvcs.c: In function ‘hvcs_open’:
drivers/char/hvcs.c:1180: error: wrong type
Holger Hoffstaette [EMAIL PROTECTED] :
[...]
Maybe turning off sendfile or NAPI just lead to random success - so far it
really looks like tso on the r8169 is the common cause.
TSO on the r8169 is the magic switch but the regression makes imvho more
sense from a VM pov:
- the corrupted file has
On Thu, Dec 06, 2007 at 03:37:46PM +0100, Richard Knutsson wrote:
Is it not an improvement to distinct booleans from actual values? Do you
use integers for ASCII characters too? It can also avoid some potential
bugs like the 'if (i == TRUE)'...
What is wrong with 'size_t' (since it is
Andreas Ericsson wrote:
Al Boldi wrote:
Phillip Susi wrote:
Al Boldi wrote:
IOW, git currently only implements the server-side use-case, but fails
to deliver on the client-side. By introducing a git-client manager
that handles the transparency needs of a single user, it should be
Al Boldi wrote:
Phillip Susi wrote:
Al Boldi wrote:
IOW, git currently only implements the server-side use-case, but fails
to deliver on the client-side. By introducing a git-client manager that
handles the transparency needs of a single user, it should be possible
to clearly isolate update
Greg KH wrote:
Why release the spinlock here? It's done after the count is incremented.
This patch does not seem correct.
Doh, you are correct, I'll make sure that I fix this up before applying
it.
thanks,
greg k-h
Hi, Greg,
I ran some tests with the fixed up version of this patch
Hi,
this is a series of patches that unify the struct desc_struct and friends
across x86_64 and i386. As usual, it provides paravirt capabilities as a
side-effect for x86_64.
I consider the main goal, namely, of unifying the desc_struct, an ongoing
effort, being this the beginning. A lot of old
This patch aims to make the access of struct desc_struct variables
equal across architectures. In this patch, I unify the i386 and x86_64
versions under an anonymous union, keeping the way they are accessed
untouched (a and b for 32-bit code, individual bit-fields for 64-bit).
This solution is
This variable is not used anywere, and is then removed
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/desc_64.h |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/include/asm-x86/desc_64.h b/include/asm-x86/desc_64.h
index
This patch changes the name of x86_64 macro used to access the per-cpu
gdt. It is now equal to the i386 version, which will allow code to be shared.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/setup64.c |2 +-
arch/x86/kernel/suspend_64.c |2 +-
this patch changes write_idt_entry signature. It now takes a gate_desc
instead of the a and b parameters. It will allow it to be later unified
between i386 and x86_64.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/paravirt_32.c |2 +-
arch/x86/xen/enlighten.c
This patch unifies struct desc_ptr between i386 and x86_64.
They can be expressed in the exact same way in C code, only
having to change the name of one of them. As Xgt_desc_struct
is ugly and big, this is the one that goes away.
There's also a padding field in i386, but it is not really
needed
To account for the differences in gate descriptor in i386 and x86_64
a gate_desc type is introduced.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/traps_32.c |3 ++-
include/asm-x86/desc_32.h | 15 ---
include/asm-x86/desc_64.h |4 ++--
this patch introduces ldt_desc type to account for the differences
in the ldt descriptor in x86_64 and i386
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/desc_64.h |2 +-
include/asm-x86/desc_defs.h |4 +++-
2 files changed, 4 insertions(+), 2
This patch introduces fill_ldt(), which populates a ldt descriptor
from a user_desc in once, instead of relying in the LDT_entry_a and
LDT_entry_b macros
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/ldt.c|3 +--
arch/x86/kernel/process_64.c |3
This patch modifies the write_ldt() function to make use
of the new struct desc_struct instead of entry_1 and entry_2
entries
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/ldt.c | 15 +++
1 files changed, 7 insertions(+), 8 deletions(-)
diff --git
This patch changes the write_gdt_entry function signature.
Instead of the old a and b parameters, it now receives
a pointer to a desc_struct, and the size of the entry being
handled. This is because x86_64 can have some 16-byte entries
as well as 8-byte ones.
Signed-off-by: Glauber de Oliveira
this patch moves constant definitions regarding descriptor types
from desc_32.h to desc_defs.h. The change from defines to enum
to comply with previous versions in desc_defs.h
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/desc_32.h |8
This patch unifies the non-paravirt part of desc_{32,64}.h into
desc.h. Most of it, is simply common code, that is moved to
the shared header. The only exception is the set_ldt_desc in desc_64.h,
which is changed - included its name - to accomodate for the way
the ldt is set up in i386.
Also,
This patch makes get_desc_base() receive a struct desc_struct,
and then uses its internal fields to compute the base address.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/tls.c |2 +-
arch/x86/mm/fault_32.c |2 +-
include/asm-x86/desc.h |8 ++--
This patch changes the type of tls_array in x86_64 to
a desc_struct. Now, both i386 and x86_64 tls_array have
the same type, and code accessing it can be shared.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/desc_64.h |2 +-
Provide a new type, tss_desc, to represent the tss descriptor
in a unified way accross x86_64 and i386
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/desc_defs.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/asm-x86/desc_defs.h
this patch changes the signature of write_ldt_entry.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/ldt.c |3 +--
arch/x86/xen/enlighten.c |4 ++--
include/asm-x86/desc_32.h |9 -
include/asm-x86/desc_64.h |7 ++-
With the types used to access descriptors in x86_64 and i386
now being the same, the code that effectively handles them can
now be easily shared. This patch moves the paravirt part of
desc_32.h into desc.h, and then, we get paravirt support in x86_64
for free.
Signed-off-by: Glauber de Oliveira
Old debugging hack sneaked back during x86 merge, this removes it.
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
diff --git a/arch/x86/kernel/acpi/wakeup_32.S b/arch/x86/kernel/acpi/wakeup_32.S
index a97313b..1e931aa 100644
--- a/arch/x86/kernel/acpi/wakeup_32.S
+++
On Thursday 06 December 2007 04:24:20 Carsten Otte wrote:
Nick Piggin wrote:
OK, thanks for taking a look at that. It will be helpful for testing
XIP with my new ramdisk driver (did you see the patch?).
I have'nt looked at it yet. I do appreciate it, I think it might
broaden the user-base
+ ehca_lock_hcalls = !(cur_cpu_spec-cpu_user_features
+ PPC_FEATURE_ARCH_2_05);
We already talked about this yesterday, but I still feel that checking the
instruction set of the CPU should not be used to determine whether a
specific
This patch unifies the set_tss_desc between i386 and x86_64,
which can now have a common implementation. After the old
functions are removed from desc_{32,64}.h, nothing important is
left, and the files can be removed.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
This patch moves _set_gate and its users to desc.h. We can now
use common code for x86_64 and i386.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/traps_32.c | 34
include/asm-x86/desc.h | 88 +++
On 12/6/07, Matt Mackall [EMAIL PROTECTED] wrote:
On Thu, Dec 06, 2007 at 08:22:15PM +0200, Ramagudi Naziir wrote:
It's probably only me, but I can't connect to a kgdb host because
of bouncing ICMP unreachables. I'll be glad if you could take a look
...
Hmmm, 6443 != 6433 (typo?) and 32785
Adrian Bunk wrote:
On Tue, Dec 04, 2007 at 12:41:25PM +0100, Marc Haber wrote:
While debugging Exim4's GnuTLS interface, I recently found out that
reading from /dev/urandom depletes entropy as much as reading from
/dev/random would. This has somehow surprised me since I have always
believed
On Thu, 06 Dec 2007 04:04:20 PST, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/
Something in here broke LVM support - an initrd that has worked fine for
quite some time suddenly couldn't mount /dev/VolGroup00/root so
Oleg Nesterov [EMAIL PROTECTED] writes:
On 12/06, Eric W. Biederman wrote:
+static struct pid *task_pid_type(struct task_struct *task, enum pid_type
type)
+{
+struct pid *pid = NULL;
+if (type == PIDTYPE_PID)
+pid = task-pids[type].pid;
+else if (type
On Fri, 2007-12-07 at 00:28 +0530, Balbir Singh wrote:
Greg KH wrote:
Why release the spinlock here? It's done after the count is incremented.
This patch does not seem correct.
Doh, you are correct, I'll make sure that I fix this up before applying
it.
thanks,
greg k-h
On Thu, Dec 06, 2007 at 08:52:29AM +0100, Hannes Reinecke wrote:
Alexey Dobriyan wrote:
git-scsi-misc.patch
Apologies for not looking into the problem earlier. See
http://marc.info/?t=11962802235r=1w=2
2.6.24-rc3-mm2: Result: hostbyte=0x01 driverbyte=0x00\nend_request: I/O
Attached is a patch that turns on INTR/QUIT/SUSP echoing in the N_TTY
line discipline (e.g. ctrl-C will appear as ^C if stty echoctl is set
and ctrl-C is set as INTR).
Linux seems to be the only unix-like OS (recently I've verified this on
Solaris, BSD, and Mac OS X) that does *not* behave this
Bernhard Kaindl wrote:
linux-2.6.24-rc4/drivers/Makefile:
...
-obj-$(CONFIG_IEEE1394)+= ieee1394/
+obj-y+= ieee1394/
...
The reason for adding it was that drivers/ieee1394/init_ohci1394_dma.c
does not get compiled if CONFIG_IEEE1394 is not set, but it's not really
Hi,
after summing up the discussion on previous patches, I'm now submitting the
patch below for formal review and adoption on branches for mainline inclusion.
As this patch is X86-only for now (might be extended for more architectures in
incremental patches tough), initially (that was in
Glauber de Oliveira Costa wrote:
This patch aims to make the access of struct desc_struct variables
equal across architectures. In this patch, I unify the i386 and x86_64
versions under an anonymous union, keeping the way they are accessed
untouched (a and b for 32-bit code, individual
Jaursch, Bill wrote:
The reason to even consider a driver for this Software only driver
was to start the work of writing a kernel space driver (loadable
module). So more specifically, I wanted to know if there is a way
to use calls to the kernel to access a loadable module that is
running
Your point is well taken.
I will probably end of with a system daemon (User Space), but pass
communication via a Kernel module (Kernel Space). The application can
call the kernel module, passing data back to the daemon (User Space).
Once I have hw, I may just use the kernel module.
Thanks
On Thu, Dec 06, 2007 at 02:18:08PM -0500, [EMAIL PROTECTED] wrote:
On Thu, 06 Dec 2007 04:04:20 PST, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/
Something in here broke LVM support - an initrd that has worked
On Thu, Dec 06, 2007 at 12:21:55PM -0700, Joe Peterson wrote:
I've used over the years as well. Bringing this to Linux also seems
like a good way to make it yet more compliant with standard unix-like
behavior.
The fix is pretty trivial. Let me know if you think this is a candidate
for
On Dec 6, 2007 5:24 PM, Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Glauber de Oliveira Costa wrote:
This patch aims to make the access of struct desc_struct variables
equal across architectures. In this patch, I unify the i386 and x86_64
versions under an anonymous union, keeping the way
On Thu, 6 Dec 2007 12:06:40 -0500
Jeff Dike [EMAIL PROTECTED] wrote:
Customize the hooks in tlb.h to optimize TLB flushing some more.
Add start and end fields to tlb_gather_mmu, which are used to limit
the address space range scanned when a region is unmapped.
The interfaces which just
Hi Boaz, Jens,
On Thu, 06 Dec 2007 11:24:44 +0200, Boaz Harrosh [EMAIL PROTECTED] wrote:
Index: 2.6.24-rc3-mm2/drivers/scsi/scsi_lib.c
===
--- 2.6.24-rc3-mm2.orig/drivers/scsi/scsi_lib.c
+++
On Thu, Dec 06, 2007 at 11:49:59PM +0530, Balbir Singh wrote:
Kamalesh Babulal wrote:
Hi Andrew,
The 2.6.24-rc4-mm1 kernel build fails with build failure,
CC drivers/char/hvcs.o
drivers/char/hvcs.c: In function ‘hvcs_open’:
drivers/char/hvcs.c:1180: error: wrong type
Daniel,
FYI: I am working on the conversion of the 2 sem-mutex in kernel/printk.c
Remy
2007/12/6, Daniel Walker [EMAIL PROTECTED]:
On Thu, 2007-12-06 at 11:23 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
The port_mutex is actually a semaphore, so easily converted
Chuck Lever [EMAIL PROTECTED] wrote:
Why not use the fsid as well? The NFS client already uses the fsid to detect
when it is crossing a server-side mount point.
Why use the FSID at all? The file handles are supposed to be unique per
server.
I also note the inclusion of server IP address in
On Thursday 06 December 2007 03:55, Andrew Morton wrote:
Consider an example.
- We a-priori decide to limit a particular stack's peak memory usage
to 1MB
Ah, this is the piece I was missing.
- We empirically discover that the maximum amount of memory which is
allocated by that stack on
On Thu, 06 Dec 2007 11:38:43 PST, Greg KH said:
Would I be remiss in hypothesising that something in gregkh-driver-kobject-*
changed something, and now we need a agk-dm-dm-kobject-fixupage.patch?
I don't know, it all depends on what is in the dm patches. Hopefully
everything that I have
El Thu, Dec 06, 2007 at 08:34:06AM -0800 Daniel Walker ha dit:
On Thu, 2007-12-06 at 11:23 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
The port_mutex is actually a semaphore, so easily converted to a
struct mutex.
Signed-off-by: Daniel Walker [EMAIL
Matt Mackall wrote:
On Tue, Dec 04, 2007 at 08:54:52AM -0800, Ray Lee wrote:
(Why hasn't anyone been cc:ing Matt on this?)
On Dec 4, 2007 8:18 AM, Adrian Bunk [EMAIL PROTECTED] wrote:
On Tue, Dec 04, 2007 at 12:41:25PM +0100, Marc Haber wrote:
While debugging Exim4's GnuTLS interface, I
(H. Peter Anvin was CC'd in the original message, but the lkml mailer
rejected it because of an html subpart... sorry)
Bear with me, because I'm no DHCP expert, nor any sort of kernel/networking
expert in any sense. (This is actually my first post to the lkml or to any
kernel developer.)
I found
Hello Matthias,
Which do you have exactly on your list? (good to know, it prevents
double work...)
Remy
2007/12/6, Matthias Kaehlcke [EMAIL PROTECTED]:
El Thu, Dec 06, 2007 at 08:34:06AM -0800 Daniel Walker ha dit:
On Thu, 2007-12-06 at 11:23 +0100, Ingo Molnar wrote:
* Daniel Walker
pages is NULL here, implying vma-vm_private_data was NULL. This is apparently
because init_vdso_vars() is __initcall and runs after the rootfs gets populated.
An experimental initrd containing an /sbin/hotplug binary caused this. Normally
we don't have that file in the initrd. Should vdso init be
Pavol Cvengros wrote:
Hello,
I am trying LKML to get some help on one linux kernel related problem.
Lately we got a machine with new HW from Intel. CPU is Intel Core2 Duo E6850
3GHz with 2GB of RAM. Motherboard is Intel DG33BU with G33 chipset.
After long fight with kernel crashes on
On Thu, Dec 06, 2007 at 11:46:42AM -0800, Andrew Morton wrote:
+void flush_tlb_mm(struct mm_struct *mm)
+{
+ struct vm_area_struct *vma = mm-mmap;
+
+ if (atomic_read(mm-mm_users) == 0)
+ return;
Under which circumstances does this test succeed?
Sigh, none. The other
Hi,
On Fri, 7 Dec 2007, Al Boldi wrote:
Andreas Ericsson wrote:
Al Boldi wrote:
By pulling the sources into a git-client manager mounted on some
dir, it should be possible to let the developer work
naturally/transparently in a readable/writeable manner, and only
require his
Bernhard Kaindl wrote:
after summing up the discussion on previous patches, I'm now submitting the
patch below for formal review and adoption on branches for mainline inclusion.
I will look a bit more into the details later; for now I have just a
quick comment on the documentation.
---
On Thu, 2007-12-06 at 21:01 +0100, Remy Bohmer wrote:
Daniel,
FYI: I am working on the conversion of the 2 sem-mutex in kernel/printk.c
I looked at the console_sem , but i was going to leave that as last..
The problem with the console_sem is that it can get locked from
interrupt context,
On Thu, 6 Dec 2007 12:04:14 -0800
Daniel Phillips [EMAIL PROTECTED] wrote:
Any idea
how to extend the accounting idea to all tasks involved in a particular
block device stack?
SMOP, I'd have thought. As long as each piece of code which handles data
for this stack knows that it's handling
On Fri, Dec 07, 2007 at 12:28:58AM +0530, Balbir Singh wrote:
Greg KH wrote:
Why release the spinlock here? It's done after the count is incremented.
This patch does not seem correct.
Doh, you are correct, I'll make sure that I fix this up before applying
it.
thanks,
greg
On Thu, 2007-12-06 at 21:12 +0100, Remy Bohmer wrote:
Hello Matthias,
Which do you have exactly on your list? (good to know, it prevents
double work...)
Here's my list so far (in no particular order).. Most aren't tested
fully yet.. I'll try to post them someplace eventually (later today
Andi Kleen wrote:
This document describes Linux Netlink, which is used in Linux both as
an intra-kernel messaging system as well as between kernel and user
space.
It can be used between user space daemons as well. In fact it is.
e.g. they often listen to each other's messages.
One
Brett Warden wrote:
On Dec 5, 2007 9:37 AM, Alan Cox [EMAIL PROTECTED] wrote:
Although I would suggest that aggressive may not be the best term - I'm
not such of a good one however - skip_passive ?
How about force_init?
Much more descriptive.
--
Bill Davidsen [EMAIL PROTECTED]
We have
Hello Daniel,
I looked at the console_sem , but i was going to leave that as last..
The problem with the console_sem is that it can get locked from
interrupt context, which is discouraged with mutex types.. I think it
will be complicated to convert..
At first it looked simple, but after I
The follow_hugetlb_page() fix I posted (merged as git commit
5b23dbe8173c212d6a326e35347b038705603d39) missed one case. If the pte is
present, but not writable and write access is requested by the caller to
get_user_pages(), the code will do the wrong thing. Rather than calling
hugetlb_fault to
* Daniel Walker [EMAIL PROTECTED] wrote:
cool. How far away are we from being able to remove all the
semaphore code? :-)
I wish my 7 patches made a dent, but it's hasn't done much. ;(
it's a beginning.
I would guess at least a week just to mop up the relatively easy
ones.. I've got
On Thursday 06 December 2007 20:44:46 Chuck Ebbert wrote:
pages is NULL here, implying vma-vm_private_data was NULL. This is apparently
because init_vdso_vars() is __initcall and runs after the rootfs gets
populated.
An experimental initrd containing an /sbin/hotplug binary caused this.
On Thursday, 6 of December 2007, Pavel Machek wrote:
Old debugging hack sneaked back during x86 merge, this removes it.
Yeah, good catch, thanks.
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
Acked-by: Rafael J. Wysocki [EMAIL PROTECTED]
diff --git a/arch/x86/kernel/acpi/wakeup_32.S
+/*
+ * FIXME: Acessing the desc_struct through its fields is more elegant,
+ * and should be the one valid thing to do. However, a lot of open code
+ * still touches the a and b acessors, and doing this allow us to do it
+ * incrementally. We keep the signature as a struct, rather than an
On Thu, Nov 08, 2007 at 08:45:01PM +0100, Jan Altenberg wrote:
Hi Sam,
commit 0b35786d77ba4037f181982cc8ca20a7a3bf0fd2
Author: Milton Miller [EMAIL PROTECTED]
Date: Fri Sep 21 18:09:02 2007 -0500
kbuild: call make once for all targets when O=.. is used
On Mon, Dec 03, 2007 at 03:34:59PM -0800, Andrew Morton wrote:
On Sun, 2 Dec 2007 14:48:42 +0100
Adrian Bunk [EMAIL PROTECTED] wrote:
On Sun, Dec 02, 2007 at 05:43:39PM +0900, Tetsuo Handa wrote:
mm/slub.c exports ksize(), but mm/slob.c and mm/slab.c don't. I don't
know why.
...
On Thu, Dec 06, 2007 at 10:02:48PM +0100, Adrian Bunk wrote:
On Mon, Dec 03, 2007 at 03:34:59PM -0800, Andrew Morton wrote:
On Sun, 2 Dec 2007 14:48:42 +0100
Adrian Bunk [EMAIL PROTECTED] wrote:
On Sun, Dec 02, 2007 at 05:43:39PM +0900, Tetsuo Handa wrote:
mm/slub.c exports
On 12/06/2007 03:51 PM, Andi Kleen wrote:
On Thursday 06 December 2007 20:44:46 Chuck Ebbert wrote:
pages is NULL here, implying vma-vm_private_data was NULL. This is
apparently
because init_vdso_vars() is __initcall and runs after the rootfs gets
populated.
An experimental initrd
Glauber de Oliveira Costa wrote:
the p parameter is an explicit memory reference, and is
enough to prevent gcc to being nasty here. The volatile
seems completely not needed.
The usual reason for these types of volatiles is to make type checking
happier, since volatile void * is compatible
On Thu, 6 Dec 2007, Markus wrote:
Just forgot to mention:
dmesg gives nothing (/var/log/messages)
the global X log aswell
and in the users .xsession-errors I have:
amarokapp: Fatal IO error: client killed
kdesktop: Fatal IO error: client killed
konqueror: Fatal IO error: client killed
Hi Pavel,
hi Rafael,
after a quick search i couldn't find anything dealing with the topic in the
subject line so here we go:
One sometimes can mix up (and by one i mean me) the
kernel images one boots after having suspended the machine previously. There can
be at least two reasons for that:
1.
fix trivial coding style issues found by checkpatch.pl:
- assignments in if conditions
- trailing whitespaces
- lines longer then 80 characters (only a couple of them)
- spaces instead of tabs
- spaces after !
- C99 comments
- other tiny changes
Signed-off-by: Marcin Ślusarz [EMAIL PROTECTED]
On Dec 6, 2007 6:54 PM, Andi Kleen [EMAIL PROTECTED] wrote:
+/*
+ * FIXME: Acessing the desc_struct through its fields is more elegant,
+ * and should be the one valid thing to do. However, a lot of open code
+ * still touches the a and b acessors, and doing this allow us to do it
+ *
applied.
thanks,
-len
On Thursday 06 December 2007 16:12, Rafael J. Wysocki wrote:
On Thursday, 6 of December 2007, Pavel Machek wrote:
Old debugging hack sneaked back during x86 merge, this removes it.
Yeah, good catch, thanks.
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
Latency was very
important, so we ended up doing essentially a multicast unix socket
rather than taking the extra penalty for UDP multicast.
What extra penalty? Local UDP shouldn't be much more expensive than Unix.
-Andi
--
To unsubscribe from this list: send the line unsubscribe
On Thursday, 6 of December 2007, Borislav Petkov wrote:
Hi Pavel,
hi Rafael,
after a quick search i couldn't find anything dealing with the topic in the
subject line so here we go:
One sometimes can mix up (and by one i mean me) the
kernel images one boots after having suspended the
601 - 700 of 854 matches
Mail list logo
