On Thu, 8 Feb 2007 08:49:41 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > This panic(hang) was found by a numa test-set on a system with 3 nodes,
> > where
> > node(2) was memory-less-node.
>
> I still think it's the wrong fix -- just get rid of the memory less node.
"Let's break it even m
On Thursday 08 February 2007 09:00, Andrew Morton wrote:
> On Thu, 8 Feb 2007 08:49:41 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> >
> > > This panic(hang) was found by a numa test-set on a system with 3 nodes,
> > > where
> > > node(2) was memory-less-node.
> >
> > I still think it's the w
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> The softlock detector has a long history of false positives and
> precious few true positives, in my experience.
hm, not so the latest & lamest in my experience. The commit that made it
quite robust was 6687a97d4041f996f725902d2990e5de6ef5cbe5, as o
On Thu, 8 Feb 2007 09:03:46 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Thursday 08 February 2007 09:00, Andrew Morton wrote:
> > On Thu, 8 Feb 2007 08:49:41 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > > This panic(hang) was found by a numa test-set on a system with 3 nodes,
On Thu, 8 Feb 2007 09:06:44 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > The softlock detector has a long history of false positives and
> > precious few true positives, in my experience.
>
> hm, not so the latest & lamest in my experience.
On Thu, 8 Feb 2007 08:49:41 +0100
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > This panic(hang) was found by a numa test-set on a system with 3 nodes,
> > where
> > node(2) was memory-less-node.
>
> I still think it's the wrong fix -- just get rid of the memory less node.
> I expect you'll likel
On Thursday 08 February 2007 09:08, Andrew Morton wrote:
> On Thu, 8 Feb 2007 09:03:46 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > On Thursday 08 February 2007 09:00, Andrew Morton wrote:
> > > On Thu, 8 Feb 2007 08:49:41 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
> > >
> > > >
> > > > >
On Thu, 8 Feb 2007 09:19:16 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
> The reason we present nodes to user space is that we can tell the user
> where the memory is. You seem to try to promote it to some abstract entity
> beyond that, but that doesn't seem particularly fruitful to me. I think
>
On Wed, Feb 07, 2007 at 02:31:57PM -0800, Zachary Amsden wrote:
> Dmitry Torokhov wrote:
> >
> >I am confused - does i8042 talk to a virtual or real hardware here? In
> >any case I think you need to fix kernel/panic.c to have proper
> >(m)delay, not mess with i8042.
>
> I think I need to fix both
On Tue, 6 Feb 2007, Mark Lord wrote:
I'm with Linus 100% here.
It's really irritating to upgrade to a newer kernel,
using the same old .config file, and then discover that
my MythTV box no longer auto-boots to record programs.
The reason being, that /proc/acpi/alarm no longer exists,
and the k
On 02/08, Horms wrote:
>
> On Wed, Feb 07, 2007 at 08:43:55PM +0300, Oleg Nesterov wrote:
> >
> > I think we have another problem with delayed_works.
> >
> > cancel_rearming_delayed_workqueue() doesn't garantee that the ->func() is
> > not
> > running upon return. I don't know if it is bug or no
Hi, thank you for reviewing. this is take3.
(very sorry for sending twice)
-Kame
following is back trace of NULL pointer access in slab_node().
This patch fix this.
== backtrace from crash (linux-2.6.20) ==
#0 [BSP:e00121f412d8] schedule at a0010061ccc0
#1 [BSP:e00121f41280] rws
On Thu, 8 Feb 2007 11:35:39 +0300 Oleg Nesterov <[EMAIL PROTECTED]> wrote:
> On 02/08, Horms wrote:
> >
> > On Wed, Feb 07, 2007 at 08:43:55PM +0300, Oleg Nesterov wrote:
> > >
> > > I think we have another problem with delayed_works.
> > >
> > > cancel_rearming_delayed_workqueue() doesn't garan
On Wed, 7 Feb 2007, Arjan van de Ven wrote:
Marc Donner wrote:
501: 215717 209388 209430 202514 PCI-MSI-edge eth10
502:927 1019 1053888 PCI-MSI-edge eth11
this is odd, this is not an irq distribution that irqbalance should give you
1
Kfifo is a ring-buffer in kernel which can be used as a lock-free way
for concurrent read/write when there are only one producer and one
consumer. Details of its design can be found in kernel/kfifo.c and
include/linux/kfifo.h.
You will find that the 'in' and 'out' fields of 'struct kfifo' are
bot
Andi Kleen wrote:
On Wed, Feb 07, 2007 at 02:31:57PM -0800, Zachary Amsden wrote:
Dmitry Torokhov wrote:
I am confused - does i8042 talk to a virtual or real hardware here? In
any case I think you need to fix kernel/panic.c to have proper
(m)delay, not mess with i8042.
I think I
On Thursday 08 February 2007 09:06, Ingo Molnar wrote:
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
> > The softlock detector has a long history of false positives and
> > precious few true positives, in my experience.
>
> hm, not so the latest & lamest in my experience. The commit that made it
> q
Hi Greg,
>> I've been working through trying to
>> create a virtual bus.
>How does this differ from a "real" bus?
None, just there wasn't a real hardware
bus (O'Reilly's Linux Device Drivers 3
chapter 14 page 377).
>> I've successfuly made it work for a
>> single instance but wanted to confirm
On Wed 07-02-07 20:45:26, Frank Hartmann wrote:
> you are the first to react on my message. I did not try 2.6.20 uptonow.
>
> What I did in the meantime:
>
> Switched to 2.6.19.2
>
> I run extensivly memtest+ and started something called smrtctl which
> should give more information on my hardd
On Thu, 8 Feb 2007 17:07:28 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
> Kfifo is a ring-buffer in kernel which can be used as a lock-free way
> for concurrent read/write when there are only one producer and one
> consumer. Details of its design can be found in kernel/kfifo.c and
> include/linux
Hi folks,
We know this is a large one and really appreciate anyone who is interested can
review it.
For any issues. We'll try to fix them ASAP.
Thank you!
-Bryan Wu
On Mon, 2007-02-05 at 21:11 -0500, Wu, Bryan wrote:
> Hi everyone,
>
> This is the Blackfin architecture patch against Linux ker
On 02/08, Andrew Morton wrote:
>
> On Thu, 8 Feb 2007 11:35:39 +0300 Oleg Nesterov <[EMAIL PROTECTED]> wrote:
>
> > Andrew, do you think it is worth to tweak delayed works so it would be
> > possible to use flush_work(dwork->work) ?
> >
>
> I've completely lost track of what you've been doing in
Vivek Goyal wrote:
> > Etienne Lorrain wrote:
> > Yes, any PT_LOAD below 64 Kbytes can only be real mode, and real-mode
> > cannot be loaded higher, and cannot be bigger than 640 Kbytes, anything
> > different (like with virtual address at 0xC000) is Linux protected mode.
> > Considering the l
* Eric Dumazet <[EMAIL PROTECTED]> wrote:
> This reminds me the current problem in close_files()
> code, where we trigger soft lockup quite regularly.
>
> Is there any chance/interest we can solve the issue Andrew had with
> this patch ?
>
> http://lkml.org/lkml/2006/5/2/273
yes - the -rt pa
On Thu, 8 Feb 2007 10:56:12 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Eric Dumazet <[EMAIL PROTECTED]> wrote:
>
> > This reminds me the current problem in close_files()
> > code, where we trigger soft lockup quite regularly.
> >
> > Is there any chance/interest we can solve the issue
On Tue, Feb 06, 2007 at 02:23:33PM +0100, Christoph Hellwig wrote:
> Iterate over sb->s_inodes instead of sb->s_files in add_dquot_ref.
> This reduces list search and lock hold time aswell as getting rid of
> one of the few uses of file_list_lock which Ingo identified as a
> scalability problem.
C
On Tue, 6 February 2007 10:16:17 -0500, Mark Lord wrote:
>
> That interface is driven entirely backwards.
> The funtionality option should always be visible,
You are absolutely correct. The _interface_ is horrible. And changing
the config language won't change that fact one bit.
Make *config i
Hi Pavel,
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi1
>
>> >> >> +module_param_named(protect_method, libata_protect_method, int, 0444);
>> >> >> +MODULE_PARM_DESC(protect_method, "hdaps disk protection method
>> >> >> (0=autodetect, 1=unload, 2=standby)");
>> >> >
>> >> > Should this be config
On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> was ufs_fs.h purposefully not exported to userspace or did it just slip
> through the cracks ? assuming the latter scenario, the attached patch
> touches up the relationship between ufs_fs.h and its sub headers (like
> ufs_fs_sb.h) so t
Hi All,
I had written an additional input_handler :
static struct input_device_id pcraw_ids[] = {
{
.flags = INPUT_DEVICE_ID_MATCH_EVBIT,
.evbit = { BIT(EV_MSC) },
},
{ },/* Terminating entry */
};
to
Linus, things still fail for me even with the $(strip ...) construct
you added works properly.
For some reason things like $(call cc-option-yn...) still fail.
My make version 3.81beta4 has the space problem, and with your
change it just returns a space. :-) Without your change it
gives the prob
Etienne Lorrain <[EMAIL PROTECTED]> writes:
>> Currently relocation information is extracted from vmlinux and packed in
>> final bzImage after some processing. After execution of real mode code
>> and once the image is decompressed, all the relocations are performed and
>> then control is transfer
Hello,
I've noticed that extending a file using direct IO fails for FAT with
EINVAL. It's basically because of the following code in fat_direct_IO():
if (rw == WRITE) {
/*
* FIXME: blockdev_direct_IO() doesn't use
* ->prepare_write(),
* so we need to update
On Wed, 2007-02-07 at 07:40 -0500, Jeff Garzik wrote:
> Conke Hu wrote:
> > Hi,
> >TEST_UNIT_READY in get_capabilities (drivers/scsi/sr.c line 743, or
> > see below) always returns error.
> >
> > code begin -
> > retries = 0;
> > do {
> >
On 2/8/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> was ufs_fs.h purposefully not exported to userspace or did it just slip
> through the cracks ? assuming the latter scenario, the attached patch
> touches up the relationship between
On Feb 8 2007 07:43, Oleg Verych wrote:
>> >>
>> >> > If that matter, `type -path' is bashizm (BloAted SHell), and "blackbox"
>> >> > with "dash" (very good `sh' equivalents) will fail.
>> >>
>> >> Does the kernel presently build with that shell?
>> >
>> >build - yes, with dash being `$(shell)'. A
Commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 breaks the build on
64-bit powerpc because we no longer get the -m64 flag passed to gcc.
There is code in arch/powerpc/Makefile which adds (or used to add)
-m64 to AS, LD and CC if we are running on a 64-bit machine (which I
am) and have a biarch tool
On Thu, Feb 08, 2007 at 09:48:31AM +, Etienne Lorrain wrote:
> Vivek Goyal wrote:
> > > Etienne Lorrain wrote:
> > > Yes, any PT_LOAD below 64 Kbytes can only be real mode, and real-mode
> > > cannot be loaded higher, and cannot be bigger than 640 Kbytes, anything
> > > different (like with vi
Andrew Morton wrote:
> On Wed, 07 Feb 2007 10:55:23 +0530
> Srinivasa Ds <[EMAIL PROTECTED]> wrote:
>
>> --- linux-2.6.20.orig/fs/debugfs/inode.c
>> +++ linux-2.6.20/fs/debugfs/inode.c
>> @@ -25,6 +25,7 @@
>>
>> if (retval)
>> subsystem_unregister(&debug_subsys);
>> +debugf
Ingo Molnar <[EMAIL PROTECTED]> writes:
> * Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>
>> Ingo would it be reasonable to get a wait queue so I can wait for an
>> irq that needs the delayed disable action to actually become masked?
>
> that might make sense, but what will do the wakeup - incid
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Thu, 8 Feb 2007 22:10:54 +1100
> Commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 breaks the build on
> 64-bit powerpc because we no longer get the -m64 flag passed to gcc.
> There is code in arch/powerpc/Makefile which adds (or used to add)
> -m64 to
From: David Miller <[EMAIL PROTECTED]>
Date: Thu, 08 Feb 2007 03:05:31 -0800 (PST)
> define test1
> $(shell echo "str1")
> endef
>
> define test2
> $(call test1)
> endef
Someone just privately explained that my test case is broken
because of the spaces before the "$(shell " in the defines.
R
Vivek Goyal <[EMAIL PROTECTED]> writes:
> Kexec as a boot loader allows to load both ELF vmlinux file or bzImage.
> Hence for kdump, a user got the flexibility to either use vmlinux or
> bzImage for dump captruing purposes. Hence I am concerned about both.
>
> If real mode code is linked with vm
From: David Miller <[EMAIL PROTECTED]>
Date: Thu, 08 Feb 2007 04:10:04 -0800 (PST)
> Removing them makes the spaces go away.
FWIW, this patch below seems to fix the sparc64 build for me.
Paul, does it work for you on powerpc too?
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
inde
On Feb 7 2007 17:34, Jack Bauer wrote:
>
> As you might imagine I have to alter the syn,synack and ack packets
> and fill it with authentification information of the user who
> initiated the new TCP connection. These information are stored in
> config files on the client/user host (for example a c
On Thu, Feb 08, 2007 at 04:00:03AM -0800, David Miller wrote:
> From: Paul Mackerras <[EMAIL PROTECTED]>
> Date: Thu, 8 Feb 2007 22:10:54 +1100
[]
> Linus and Oleg tried to fix it with various subsequent changes
> to scripts/Kbuild.include, but it's still broken.
And Roland McGrath, but it turned
Well, the cable is OK, of course I checked.
On Wed, 7 Feb 2007, Robert Hancock wrote:
Date: Wed, 07 Feb 2007 22:36:58 -0600
From: Robert Hancock <[EMAIL PROTECTED]>
To: Alan <[EMAIL PROTECTED]>,
linux-kernel
Cc: Luigi Genoni <[EMAIL PROTECTED]>
Subject: Re: [BUG?] ata disk running maximum
On Thu, Feb 08 2007, Nigel Cunningham wrote:
> On Wed, 2007-02-07 at 23:18 -0200, Otavio Salvador wrote:
> > Nigel Cunningham <[EMAIL PROTECTED]> writes:
> >
> > > - for (tracedata = &__tracedata_start ; tracedata < &__tracedata_end ;
> > > tracedata += 6) {
> > > + for (tracedata = &__tracedata_
On Thu, Feb 08, 2007 at 10:10:54PM +1100, Paul Mackerras wrote:
> Commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 breaks the build on
> 64-bit powerpc because we no longer get the -m64 flag passed to gcc.
> There is code in arch/powerpc/Makefile which adds (or used to add)
> -m64 to AS, LD and CC i
On Thu, 8 Feb 2007, David Miller wrote:
> From: David Miller <[EMAIL PROTECTED]>
> Date: Thu, 08 Feb 2007 04:10:04 -0800 (PST)
>
> > Removing them makes the spaces go away.
>
> FWIW, this patch below seems to fix the sparc64 build for me.
>
> Paul, does it work for you on powerpc too?
Thx, it s
On Thu, 8 Feb 2007, Geert Uytterhoeven wrote:
> On Thu, 8 Feb 2007, David Miller wrote:
> > From: David Miller <[EMAIL PROTECTED]>
> > Date: Thu, 08 Feb 2007 04:10:04 -0800 (PST)
> >
> > > Removing them makes the spaces go away.
> >
> > FWIW, this patch below seems to fix the sparc64 build for me
Hiroyuki KAMEZAWA wrote:[Wed Feb 07 2007, 03:36:47AM EST]
> On Wed, 7 Feb 2007 00:04:41 -0800 (PST)
> Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 7 Feb 2007, KAMEZAWA Hiroyuki wrote:
> >
> > > > Hmmm... Remove the node from the node_online_map instead?
> > > >
> > > Changi
Hello.
Marc St-Jean wrote:
Fourth attempt at the serial driver patch for the PMC-Sierra MSP71xx device.
There are three different fixes:
1. Fix for DesignWare THRE errata
- Dropped our fix since the "8250-uart-backup-timer.patch" in the "mm"
tree also fixes it. This patch needs to be applied on
There is a small problem in handling page bounce.
At the moment blk_max_pfn equals max_pfn, which is in fact
not maximum possible _number_ of a page frame, but the _amount_
of page frames. For example for the 32bit x86 node with 4Gb RAM,
max_pfn = 0x10, but not 0x.
request_queue structur
Good day,
I don't recive mail from LKML
I am very sorry that I did't ask this before,
Before lot of time (about half a year) I lost password to my email box.
But I managed to find it in old notebook, after about three months, and I found
that my mailbox
ceased to recive mail from LKML.
Then
> > I assume you care about this ELF header because you are also a user of
> > the ELF file vmlinux, aren't you?
>
> Yes I am. I use kexec boot loader which has capability to load ELF kernel
> images (vmlinux). That's why I am concerned about linking real mode code
> in vmlinux as for kdump case I
Fed up with verifying various barrier-based schemes, this version uses
spinlock.
---
Current /proc creation interfaces suffer from at least two types of races:
1. Write
From: Levitsky Maxim <[EMAIL PROTECTED]>
Date: Thu, 8 Feb 2007 05:09:25 -0800 (PST)
> But now things changed, cause I wrote number of patches, and it is
> very difficult to send patches without subscription.
You don't need to be subscribed in order to send postings to the
mailing list.
-
To unsub
From: Oleg Verych <[EMAIL PROTECTED]>
Date: Thu, 8 Feb 2007 13:47:56 +0100
> On Thu, Feb 08, 2007 at 10:10:54PM +1100, Paul Mackerras wrote:
> > Commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 breaks the build on
> > 64-bit powerpc because we no longer get the -m64 flag passed to gcc.
> > There is
Still no independent confirmation as to whether this is a problem or not.
Updated some comments, added diffstats to patches, don't use __SetPageUptodate
as an internal page-flags.h private function.
I would like to eventually get an ack from Hugh regarding the anon memory
and especially swap side
After running SetPageUptodate, preceeding stores to the page contents to
actually bring it uptodate may not be ordered with the store to set the page
uptodate.
Therefore, another CPU which checks PageUptodate is true, then reads the
page contents can get stale data.
Fix this by ensuring SetPageUp
__block_write_full_page is calling SetPageUptodate without the page locked.
This is unusual, but not incorrect, as PG_writeback is still set.
However with the previous patch, this is now a problem: so don't bother
setting the page uptodate in this case (it is weird that the write path
does such a
Ensure pages are uptodate after returning from read_cache_page, which allows
us to cut out most of the filesystem-internal PageUptodate_NoLock calls.
I didn't have a great look down the call chains, but this appears to fixes 7
possible use-before uptodate in hfs, 2 in hfsplus, 1 in jfs, a few in e
On Thu, Feb 08, 2007 at 01:08:14AM -0800, Zachary Amsden wrote:
> Andi Kleen wrote:
> >On Wed, Feb 07, 2007 at 02:31:57PM -0800, Zachary Amsden wrote:
> >
> >>Dmitry Torokhov wrote:
> >>
> >>>I am confused - does i8042 talk to a virtual or real hardware here? In
> >>>any case I think you need
Date: Feb 08, 2007 at 05:17:06AM -0800
From: David Miller
> From: Oleg Verych <[EMAIL PROTECTED]>
> Date: Thu, 8 Feb 2007 13:47:56 +0100
>
[]
> > As i have refactored some CC checking code in Kbuild.include, it
> > turned, that some versions of `make' after calling nested functions,
> > add (or l
> From: [EMAIL PROTECTED]
> Newsgroups: gmane.linux.kernel.commits.mm
> Subject: + search-a-little-harder-for-mkimage.patch added to -mm tree
> Date: Wed, 07 Feb 2007 22:07:38 -0800
[]
> --
> Subject: search a little harder for mkimage
> From: "Mi
Isn't the extra space there because you've included it in the definition
of "test"? The attempt at introducing indentation introduces the extra
space character. Defining test without the internal indentation should
produce the results you are looking for.
--
Michal Ostrowski <[EMAIL PROTECTED]
--- David Miller <[EMAIL PROTECTED]> wrote:
> From: Levitsky Maxim <[EMAIL PROTECTED]>
> Date: Thu, 8 Feb 2007 05:09:25 -0800 (PST)
>
> > But now things changed, cause I wrote number of patches, and it is
> > very difficult to send patches without subscription.
>
> You don't need to be subscrib
On 2/8/07, Oleg Verych <[EMAIL PROTECTED]> wrote:
proposition is to substitute:
"$(CONFIG_SHELL) $(MKIMAGE)"
with
"mkimage"
this isnt a one-to-one change ... let's look at the typical
mkimage-missing scenario ...
with mkuboot.sh you'd get output like:
...
UIMAGE arch/blackfin/boot/
Junio C Hamano wrote:
Jeff Garzik <[EMAIL PROTECTED]> writes:
mode change 100644 => 100755 drivers/net/qla3xxx.c
mode change 100644 => 100755 drivers/net/qla3xxx.h
Did you mean to have these? Commit bd36b0ac appears to have
brought the mode bits change in.
Not trying to nitpick --- I am t
On 8 Feb 2007 14:33:21 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
On Thu, Feb 08, 2007 at 01:08:14AM -0800, Zachary Amsden wrote:
> Andi Kleen wrote:
> >On Wed, Feb 07, 2007 at 02:31:57PM -0800, Zachary Amsden wrote:
> >
> >>Dmitry Torokhov wrote:
> >>
> >>>I am confused - does i8042 talk to a
On 2/7/07, Rusty Russell <[EMAIL PROTECTED]> wrote:
On Wed, 2007-02-07 at 12:35 +, Pavel Machek wrote:
> Ugh, it sounds like paravirt is more b0rken then I thought. It should
> always to the proper delay, then replace those udelays that are not
> needed on virtualized hardware with something
Just did a pull for the first time since 2.6.20, and a /megaton/ of new
warnings have appeared, on Fedora Core 6/x86-64 "make allyesconfig".
All of the new warnings spew appear to be "pointers differ in
signedness" warning. Granted, we should care about these, but even a
"silent" build (make
On Feb 6, 2007, at 5:02 PM, Carl Love wrote:
This is the first update to the patch previously posted by Maynard
Johnson as "PATCH 4/4. Add support to OProfile for profiling CELL".
This repost fixes the line wrap issue that Ben mentioned. Also the
kref
handling for the cached info has been f
Michael,
Thanks very much for the advice. Both issues have been solved now, with
your help.
-Maynard
Michael Ellerman wrote:
On Wed, 2007-02-07 at 09:41 -0600, Maynard Johnson wrote:
Carl Love wrote:
Subject: Add support to OProfile for profiling Cell BE SPUs
From: Maynard Johns
On Wed, 2007-02-07 at 18:57 -0700, Eric W. Biederman wrote:
> Stephen Smalley <[EMAIL PROTECTED]> writes:
>
> >
> > One related but separate issue is that the /proc/sys inode labeling is
> > also affected by the sysctl patch series. Those inodes used to be
> > labeled by selinux_proc_get_sid (fro
On Wed, 2007-02-07 at 15:21 -0700, Eric W. Biederman wrote:
> Stephen Smalley <[EMAIL PROTECTED]> writes:
>
> > Actually, on further inspection, it looks like the real issue is the
> > "path" name generation; "cat /proc/sys/kernel/modprobe" yields a call to
> > security_genfs_sid() with just "/mod
On 2/8/07, Frank Salomon <[EMAIL PROTECTED]> wrote:
Hi All,
I had written an additional input_handler :
static struct input_device_id pcraw_ids[] = {
{
.flags = INPUT_DEVICE_ID_MATCH_EVBIT,
.evbit = { BIT(EV_MSC) },
},
On Thursday 08 February 2007, Arjan van de Ven wrote:
> On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> > was ufs_fs.h purposefully not exported to userspace or did it just slip
> > through the cracks ? assuming the latter scenario, the attached patch
> > touches up the relationship bet
===
[ INFO: possible circular locking dependency detected ]
2.6.20 #2
---
soffice.bin/29030 is trying to acquire lock:
(sk_lock-AF_INET){--..}, at: [<78259420>] tcp_sendmsg+0x16/0xafa
but task
After looking at the scheduler timing I was thinking it might be a fair
trade off to convert sched_clock to return cycles instead of converting
to nanosecond each time it reads ..
I'm just probing for anyone thoughts on this ..
I'm not promoting a specific implementation, but I would think the
I have some patches that move the backlight away from using the class
stuff. The only problem is the patch requires all backlight devices
to be linked to a real struct device. Right now the acpi backligths are
not.
Signed-Off: James Simmons <[EMAIL PROTECTED]>
diff --git a/drivers/video/backl
Change __init to __devinit in rtc drivers' probe functions.
Resolves MODPOST warnings:
WARNING: drivers/rtc/rtc-ds1553.o - Section mismatch: reference to
.init.text:ds1553_rtc_probe from .data.rel between 'ds1553_rtc_driver' (at
offset 0x0) and 'ds1553_nvram_attr'
WARNING: drivers/rtc/rtc-ds1742.
Jan Kara <[EMAIL PROTECTED]> writes:
> Hello,
Hello,
> I've noticed that extending a file using direct IO fails for FAT with
> EINVAL. It's basically because of the following code in fat_direct_IO():
>
> if (rw == WRITE) {
> /*
> * FIXME: blockdev_direct_IO() doesn't use
>
Change __init to __devinit for isp116x_probe.
Resolves MODPOST warning:
WARNING: drivers/usb/host/isp116x-hcd.o - Section mismatch: reference to
.init.text:isp116x_probe from .data.rel.local between 'isp116x_driver' (at
offset 0x0) and 'isp116x_hc_driver'
Signed-off-by: Prarit Bhargava <[EMAIL P
On Wed, Feb 07, 2007 at 03:52:54PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 8 Feb 2007, Roman Zippel wrote:
> >
> > Sorry, it needs more changes, the patch simply wasn't ready.
>
> One problem I find very problematic with all the Kbuild setup is that
> people tend to be very quiet about any
While porting over a few class_devices I discovered a problem with
device_destroy. It uses a dev_t which several classes don't use.
Should all classes require a dev_t or should we just pass in the device
itself?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On Wed, 7 Feb 2007, Andrew Morton wrote:
On Thu, 8 Feb 2007 00:02:10 +0100 (CET) Lukasz Trabinski <[EMAIL PROTECTED]>
wrote:
Hello
On 2.6.19 I had about 60 days uptime, on 2.6.20 2 days :(
Did the machine actually fail? Or did it just print these messages and
keep going?
Was message fr
Philippe De Muyter wrote:
On Tue, Feb 06, 2007 at 10:41:30PM +0200, Ahmed S. Darwish wrote:
On Tue, Feb 06, 2007 at 09:52:17AM -0800, Joe Perches wrote:
On Tue, 2007-02-06 at 18:04 +0200, Ahmed S. Darwish wrote:
A patch to use ARRAY_SIZE macro already defined in kernel.h
Signed-off-by: Ahmed S
On Thu, 2007-02-08 at 10:10 -0500, Mike Frysinger wrote:
> On Thursday 08 February 2007, Arjan van de Ven wrote:
> > On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> > > was ufs_fs.h purposefully not exported to userspace or did it just slip
> > > through the cracks ? assuming the latter
On Fri 09-02-07 00:44:06, OGAWA Hirofumi wrote:
> Jan Kara <[EMAIL PROTECTED]> writes:
Hello,
> > I've noticed that extending a file using direct IO fails for FAT with
> > EINVAL. It's basically because of the following code in fat_direct_IO():
> >
> > if (rw == WRITE) {
> > /*
> >
Hi All,
Did the migration of the git stuff to a new dedicated server on
kernel.org ever happen? IIRC, it was supposed to happen the 5th of
Feb. or so.
josh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Thursday 08 February 2007, Arjan van de Ven wrote:
> On Thu, 2007-02-08 at 10:10 -0500, Mike Frysinger wrote:
> > On Thursday 08 February 2007, Arjan van de Ven wrote:
> > > On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> > > > was ufs_fs.h purposefully not exported to userspace or di
On Feb 7 2007 19:06, Christoph Hellwig wrote:
>On Wed, Feb 07, 2007 at 07:03:05PM +0100, Jan Engelhardt wrote:
>
>> With filesystems that can turn on their quota after mount time (about
>> every fs except xfs), I can surely have a ton of files open, and hence,
>> if I understand correctly, have
In my last set of numbers for my buffered-write deadlock fix using 2 copies
per page, I realised there is no real performance hit for !uptodate pages
as opposed to uptodate ones. This is unexpected because the uptodate pages
only require a single copy...
The problem turns out to be operator error.
Add an iterator data structure to operate over an iovec. Add usercopy
operators needed by generic_file_buffered_write, and convert that function
over.
include/linux/fs.h | 32
mm/filemap.c | 132 ++---
mm/filemap.h | 103
Add a new "perform_write" aop, which replaces prepare_write and commit_write
as a single call to copy a given amount of userdata at the given offset. This
is more flexible, because the implementation can determine how to best handle
errors, or multi-page ranges (eg. it may use a gang lookup), and o
Convert ext2 to use ->perform_write. This uses the main loop out of
generic_perform_write, but when encountering a short usercopy, it
zeroes out new uninitialised blocks, and passes in a short-length commit
to __block_commit_write, which does the right thing (in terms of not
setting things uptodate
Nick Piggin <[EMAIL PROTECTED]> writes:
> Convert ext2 to use ->perform_write. This uses the main loop out of
> generic_perform_write, but when encountering a short usercopy, it
> zeroes out new uninitialised blocks, and passes in a short-length commit
> to __block_commit_write, which does the rig
On Wed, Dec 13, 2006 at 10:35:08AM +0900, Horms wrote:
> On Fri, Dec 08, 2006 at 10:32:15AM +1100, Michael Neuling wrote:
> > > >Is there a kexec-tools patch too? How does second kernel know about
> > > >the location of the first kernel's initrd to be reused?
> > > >
> > > >
> > > kexec-tools has
1 - 100 of 329 matches
Mail list logo
