On Thursday 19 July 2007 21:56, Ingo Molnar wrote:
> nope - with this patch applied the box still has no network, symptoms
> are similar. (should i apply the WARN_ON() patch too?)
Yes, that would be nice. If that doesn't help, you can also throw in
the one below.
Olaf
--
Olaf Kirch | --- o
DRM
Subject : wine locks up system
References : http://lkml.org/lkml/2007/7/17/128
Last known good : ?
Submitter : Charles Gagalac <[EMAIL PROTECTED]>
Caused-By : commit d4e2cbe9cb9219fc924191a6baa2369140cb5ea8
Dave Airlie <[EMAIL PROTECTED]>
On Thu, 19 Jul 2007, Denis Vlasenko wrote:
> On Tuesday 17 July 2007 00:42, Bodo Eggert wrote:
> > > b) make 4K stacks the default option in vanilla kernel.org kernels as
> > > a gentle nudge towards getting people to start fixing the code paths
> > > that are not 4K stack safe.
> >
> > That's
On Jul 19 2007 21:28, Hans-Jürgen Koch wrote:
>Am Donnerstag 19 Juli 2007 18:33 schrieb Jan Engelhardt:
>> On Jul 18 2007 16:26, Greg Kroah-Hartman wrote:
>> >
>> >http://www.tglx.de/private/hjk/cif-orig-2.6.tar.bz2
>> >
>> >WARNING: Don't look at the code for too long, you might become sick :-)
> "
> * For initialized data:
> * You should insert __initdata between the variable name and equal
> * sign followed by value, e.g.:
> *
> * static int init_variable __initdata = 0;
> * static char linux_logo[] __initdata = { 0x32, 0x36, ... };
> "
>
> or we need to update these lines?
On Jul 19 2007 12:18, Greg KH wrote:
>On Thu, Jul 19, 2007 at 08:03:06PM +0200, Jan Engelhardt wrote:
>>
>> top is 275afcac9953ece0828972edeab9684cfe1a5ef3, error is:
>> LD .tmp_vmlinux1
>> drivers/built-in.o: In function `store_uevent':
>> core.c:(.text+0x20ebb): undefined reference to
Temporarily allocated struct mlx4_qp_context *context is leaked by
several error paths. The patch takes advantage of the return value 'err'
being preinitialized to -EINVAL.
Spotted by Coverity (1768).
Signed-off-by: Florin Malita <[EMAIL PROTECTED]>
---
drivers/infiniband/hw/mlx4/qp.c | 12
* Olaf Kirch <[EMAIL PROTECTED]> wrote:
> Does the following help?
> --- build-2.6.orig/drivers/net/netconsole.c
> +++ build-2.6/drivers/net/netconsole.c
> @@ -70,7 +70,7 @@ static void write_msg(struct console *co
> int frag, left;
> unsigned long flags;
>
> - if (!np.dev)
>
On Jul 19, 2007, at 12:30 AM, Andrew Morton wrote:
On Fri, 13 Jul 2007 21:20:33 -0400 Mathieu Desnoyers
<[EMAIL PROTECTED]> wrote:
Powerpc - Include pagemap.h in asm/powerpc/tlb.h
Fixes this powerpc build error in 2.6.22-rc6-mm1 for powerpc 64 :
In file included from
>
> I was not talking about sysdevs. I was talking about platform devices
> that are already being created for pcspkr by arch code. Now I want
> arch code to provide a spinlock for pcspkr driver to use when
> accessing PIT. What it does it allows to remove arch specific
> knowledge (i.e. #ifdef
On Thu, Jul 19, 2007 at 01:09:10PM -0600, Matthew Wilcox wrote:
> With the new setup code, we generate a couple more files
> --- a/arch/i386/boot/.gitignore
> +++ b/arch/i386/boot/.gitignore
> @@ -1,3 +1,5 @@
> bootsect
> bzImage
> setup
> +setup.bin
> +setup.elf
ACK
same chunk against
Linus, Christoph,
recent slub commits in -git cause this bootup crash:
Freeing unused kernel memory: 324k freed
Write protecting the kernel read-only data: 1294k
[ cut here ]
kernel BUG at mm/slub.c:2401!
invalid opcode: [#1]
PREEMPT SMP
Modules linked in:
* Jan Glauber <[EMAIL PROTECTED]> wrote:
> > still, CFS needs time measurement across idle periods as well, for
> > another purpose: to be able to do precise task statistics for /proc.
> > (for top, ps, etc.) So it's still true that sched_clock() should
> > include idle periods too.
>
> I'm
* Jesper Juhl ([EMAIL PROTECTED]) wrote:
> Hi,
>
> Coverity spotted what looks like a real possible case of using a
> variable after it has been freed.
> The problem is in kernel/relay.c::relay_open_buf()
>
> If the code hits "goto free_buf;" it ends up in this code :
>
> free_buf:
>
Does the following help?
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
[EMAIL PROTECTED] |/ | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
Test patch
---
Index: build-2.6/drivers/net/netconsole.c
On Tuesday 17 July 2007 00:42, Bodo Eggert wrote:
> > Please note that I was not trying to remove the 8K stack option right
> > now - heck, I didn't even add anything to feature-removal-schedule.txt
> > - all I wanted to accomplish with the patch that started this threas
> > was; a) indicate that
On Thu, Jul 19, 2007 at 08:03:06PM +0200, Jan Engelhardt wrote:
> Hi,
>
>
> top is 275afcac9953ece0828972edeab9684cfe1a5ef3, error is:
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `store_uevent':
> core.c:(.text+0x20ebb): undefined reference to `kobject_actions'
>
On Thu, Jul 19, 2007 at 08:11:26PM +0200, Gabriel C wrote:
> Jan Engelhardt wrote:
> > Hi,
> >
> >
> > top is 275afcac9953ece0828972edeab9684cfe1a5ef3, error is:
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `store_uevent':
> > core.c:(.text+0x20ebb): undefined reference to
I think my first attempt to post this may have got lost in space somewhere.
Signed-off by: Adrian McMenamin <[EMAIL PROTECTED]>
diff --git a/arch/sh/drivers/dma/dma-api.c b/arch/sh/drivers/dma/dma-api.c
index cf8e119..0c9b3bc 100644
--- a/arch/sh/drivers/dma/dma-api.c
+++
On Thu, 19 Jul 2007 11:20:43 -0700 (PDT)
andrei radulescu-banu <[EMAIL PROTECTED]> wrote:
> > [Ben] If tcpdump and/or bridging needs to disable the hw-accel, then it can
> explicitly do so by some API. That is better than overloading
> the promisc flag in my opinion.
>
> I guess I could be
Am Donnerstag 19 Juli 2007 18:33 schrieb Jan Engelhardt:
>
> On Jul 18 2007 16:26, Greg Kroah-Hartman wrote:
> >
> >http://www.tglx.de/private/hjk/cif-orig-2.6.tar.bz2
> >
> >WARNING: Don't look at the code for too long, you might become sick :-)
>
> Taking precautions for people? I get a 404...
On Thu, 19 Jul 2007, Thomas Gleixner wrote:
On Wed, 2007-07-18 at 16:43 -0700, Jeremy Katz wrote:
On Wed, 18 Jul 2007, Jeremy Katz wrote:
On Wed, 18 Jul 2007, Thomas Gleixner wrote:
Also can you please enable CONFIG_PROVE_LOCKING, which might catch any
locking problem, which might be
On 7/19/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
On Thursday 19 July 2007 17:22:38 Dmitry Torokhov wrote:
> Hi Andi,
>
> On 7/19/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> >
> > From: Thomas Gleixner <[EMAIL PROTECTED]>
> >
> > Replace the pcspkr private PIT lock by the global PIT lock to
* Olaf Kirch <[EMAIL PROTECTED]> wrote:
> Here's a somewhat drastic modification that should not change any
> timing, but just verifies whether my patch is to blame at all. Can you
> give it a try?
> @@ -1027,7 +1027,7 @@ static inline void netif_rx_complete(str
>* But at least it
ACK
Thanks for catching this. Your patch looks fine. I tested for
regression, no problems. I also tested the error path and had the
expected results.
Thanks
Dave
Jesper Juhl wrote:
Hi,
Coverity spotted what looks like a real possible case of using a
variable after it has been freed.
The
Coverity (1769) found the following problem: if the erase counter
overflow check triggers, ec_hdr is leaked.
Moving the allocation after the overflow check should take care of it.
Signed-off-by: Florin Malita <[EMAIL PROTECTED]>
---
drivers/mtd/ubi/scan.c |8
1 file changed, 4
On Thu, 19 Jul 2007, Linus Torvalds wrote:
>
> Does something like this fix it?
>
> Christoph, please go over this and see if there are other cases like that.
Actually, here's a better version, I think.
Andi, does this patch fix your problem?
Linus
---
mm/slab.c |4 ++--
On Thu, 2007-07-19 at 18:00 +0200, Ingo Molnar wrote:
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> > > /*
> > > - * Monotonic_clock - returns # of nanoseconds passed since time_init()
> > > + * Scheduler clock - returns current time in nanosec units.
> > > + * Now based on virtual cpu
On 19/07/07, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
On Thursday 19 July 2007, Michal Piotrowski wrote:
> IDE
>
> Subject : compile error if CONFIG_BLOCK not enabled related to
linux/ide.h include
> References : http://lkml.org/lkml/2007/7/18/11
> Last known good : ?
Hey-
Patch to update do_coredump such that it ignores RLIMIT_CORE in the
event that core_pattern is a pipe. RLIMIT_CORE is meant to prevent dumping
cores that are to large for the filesystem they are being written to for a given
user id. If the core_pattern points to a pipe, the core
On Thursday 19 July 2007 18:07, Ingo Molnar wrote:
> because i dont seem to be able to trigger Olaf's WARN_ON(), can you see
> anything in the ethtool output that i sent in the previous mail(s)?
If the WARN_ON doesn't trigger, I cannot see how my patch would affect
your system.
- IF we
I'm getting this with current GIT kernels when I plug an SD card into
the side of my machine. It appears to see the filesystem OK anyway, but
for some reason all the hal/gnome desktop stuff isn't seeing it. Was
working last week.
The message is:
mmc0: Unexpected interrupt 0x8000.
sdhci:
On Thursday 19 July 2007, Michal Piotrowski wrote:
> IDE
>
> Subject : compile error if CONFIG_BLOCK not enabled related to
> linux/ide.h include
> References : http://lkml.org/lkml/2007/7/18/11
> Last known good : ?
> Submitter : Kumar Gala <[EMAIL PROTECTED]>
> Caused-By
Hi,
On Thursday 19 July 2007, Michal Piotrowski wrote:
> Unclassified
>
> Subject : disk error loop (panic?) ide_do_rw_disk-bad
> References : http://lkml.org/lkml/2007/7/17/467
> Last known good : ?
> Submitter : Giacomo Catenazzi <[EMAIL PROTECTED]>
> Caused-By : ?
>
With the new setup code, we generate a couple more files
Signed-off-by: Matthew Wilcox <[EMAIL PROTECTED]>
diff --git a/arch/i386/boot/.gitignore b/arch/i386/boot/.gitignore
index 495f20c..1846514 100644
--- a/arch/i386/boot/.gitignore
+++ b/arch/i386/boot/.gitignore
@@ -1,3 +1,5 @@
bootsect
Linus Torvalds wrote:
Ok, I think I see it: I think the mm/slab.c conversion of kmalloc(0) is
totally broken.
The problem? It returns ZERO_SIZE_PTR from __find_general_cachep(), not
from __kmalloc(). So anythign that uses __find_general_cachep() will get
an invalid cachep pointer, which was
On 7/20/07, Gabriel C <[EMAIL PROTECTED]> wrote:
Gabriel C wrote:
>>
>>
>>> Subject : Oops while modprobing phy fixed module
>>> References : http://lkml.org/lkml/2007/7/14/63
>>> Last known good : ?
>>> Submitter : Gabriel C <[EMAIL PROTECTED]>
>>> Caused-By : Tejun Heo
Ingo Molnar wrote:
> just in case someone sees false positives and wants to turn it off.
Why not make 0=off?
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[PATCH] fix modpost warnings for xtensa
The Xtensa architecture places literal pools in sections separate
from the instructions. The corresponsing text sections, therefore,
reference the .literal section, and we have to suppress those
warnings. The naming
Hi Linus:
Updates to the hwmon subsystem are ready...
Please pull from:
git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git release
You'll get several new drivers, conversion of several existing drivers to
use the platform device model, and various bugfixes and enhancements.
The last
* Ravikiran G Thirumalai <[EMAIL PROTECTED]> wrote:
> > also, i think the valid threshold should be between 1 and 60 seconds
> > i think.
>
> 60 seconds! Is that not a pretty high threshold? The reason for
> lowering the tolerance threshold from 10s is to catch bugs early in
> lab
Gabriel C wrote:
>>
>>
>>> Subject : Oops while modprobing phy fixed module
>>> References : http://lkml.org/lkml/2007/7/14/63
>>> Last known good : ?
>>> Submitter : Gabriel C <[EMAIL PROTECTED]>
>>> Caused-By : Tejun Heo <[EMAIL PROTECTED]>
>>>
On 19/07/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
> Subject : ext4 build warnings
> References : http://lkml.org/lkml/2007/7/18/420
> Last known good : ?
> Submitter : Jeff Garzik <[EMAIL PROTECTED]>
> Caused-By : ?
> Handled-By : Mingming Cao <[EMAIL
On Thu, Jul 19, 2007 at 11:11:42AM +0200, Ingo Molnar wrote:
>
>* Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>> > +softlockup_thresh:
>> > +
>> > +This value can be used to lower the softlockup tolerance
>> > +threshold. The default threshold is 10s. If a cpu is locked up
>> > +for 10s, the
> [Ben] If tcpdump and/or bridging needs to disable the hw-accel, then it can
explicitly do so by some API. That is better than overloading
the promisc flag in my opinion.
I guess I could be persuaded in the end. But let me still play devil advocate.
The semantics of 'promiscuous', in my
On Thu, Jul 19 2007, Jeremy Fitzhardinge wrote:
> Jens Axboe wrote:
> > On Thu, Jul 19 2007, Jeremy Fitzhardinge wrote:
> >
> >>> Index: linux/block/blktrace.c
> >>> ===
> >>> --- linux.orig/block/blktrace.c
> >>> +++
On Wed, 18 Jul 2007 00:24:07 +0800, leo wrote:
(snip)
> Here is the helper process I propose to help more people to participate.
> Suggestions and comments are welcomed.
I think this seems mostly good. I will try to comment a bit.
> 1) Developer who can't speak English or has a problem going
Jan Engelhardt wrote:
> Hi,
>
>
> top is 275afcac9953ece0828972edeab9684cfe1a5ef3, error is:
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `store_uevent':
> core.c:(.text+0x20ebb): undefined reference to `kobject_actions'
> core.c:(.text+0x20edd): undefined reference to
On Thu, 19 Jul 2007, Roland Dreier wrote:
>
> I think the oops below is related -- Michael reports that avoiding
> kmalloc(0) in the mlx4_ib driver makes it go away.
Ok, I think I see it: I think the mm/slab.c conversion of kmalloc(0) is
totally broken.
The problem? It returns ZERO_SIZE_PTR
Jens Axboe wrote:
> On Thu, Jul 19 2007, Jeremy Fitzhardinge wrote:
>
>>> Index: linux/block/blktrace.c
>>> ===
>>> --- linux.orig/block/blktrace.c
>>> +++ linux/block/blktrace.c
>>> @@ -41,7 +41,7 @@ static void trace_note(struct
Quoting Arjan van de Ven ([EMAIL PROTECTED]):
>
> >
> > :)
> >
> > Actually, given that when lsm was being introduced, lsm seemed to
> > improve performance overall, have you taken any measurements to show
> > that this is actually the case? Of course it makes sense that it would,
> > but
On Thu, 2007-07-19 at 20:00 +0200, Andi Kleen wrote:
> On Thursday 19 July 2007 19:43:49 Daniel Walker wrote:
> > On Thu, 2007-07-19 at 19:38 +0200, Andi Kleen wrote:
> > > On Thursday 19 July 2007 19:31:56 Daniel Walker wrote:
> > >
> > > > >From my perspective a downside to sched_clock is that
On Thu, 19 Jul 2007, Krzysztof Halasa wrote:
>
> Jeff Garzik <[EMAIL PROTECTED]> writes:
>
> > My overall goal is killing useless warnings
> > that continually obscure real ones.
>
> Precisely, the goal should be to make must_check (and similar things)
> warn only in real cases.
.. the
Fix afs_send_simple_reply() to accept a greater-than-zero return value from
rxrpc_kernel_send_data() as being a successful return rather than thinking it
an error and aborting the call.
rxrpc_kernel_send_data() previously returned zero incorrectly when it worked
successfully, but has been patched
Hi,
top is 275afcac9953ece0828972edeab9684cfe1a5ef3, error is:
LD .tmp_vmlinux1
drivers/built-in.o: In function `store_uevent':
core.c:(.text+0x20ebb): undefined reference to `kobject_actions'
core.c:(.text+0x20edd): undefined reference to `kobject_actions'
make[1]: *** [.tmp_vmlinux1]
Now that arch/powerpc/platforms/cell/spufs/fault.c is always built in
the kernel there is no need to export handle_mm_fault anymore.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Index: linux-2.6/mm/memory.c
===
---
On Thu, 19 Jul 2007, Krzysztof Halasa wrote:
> >
> > We absolutely NEVER add things like "must_check" unless not checking
> > causes a real and obvious SECURITY ISSUE.
>
> Oh, come on, almost every kernel bug is a potential security issue.
Sure. And adding unnecessary checking that
>
> :)
>
> Actually, given that when lsm was being introduced, lsm seemed to
> improve performance overall, have you taken any measurements to show
> that this is actually the case? Of course it makes sense that it would,
> but witjout measurements we do not know.
SuSE did a bunch of
On Thursday 19 July 2007 19:43:49 Daniel Walker wrote:
> On Thu, 2007-07-19 at 19:38 +0200, Andi Kleen wrote:
> > On Thursday 19 July 2007 19:31:56 Daniel Walker wrote:
> >
> > > >From my perspective a downside to sched_clock is that the math is
> > > duplicated per architecture .. I think it
On 07/19/2007 11:47 AM, Andrew Morton wrote:
On Thu, 19 Jul 2007 11:39:32 +0200 (CEST) Geert Uytterhoeven <[EMAIL
PROTECTED]> wrote:
Oh dear.
ps3rom_priv(dev) = host;
that's 'orrid. We have an identifier pretending to be a function, only we
go and treat it as an lvalue.
I mean, C
On Thu, 2007-07-19 at 13:44 -0400, James Smart wrote:
> Florin,
>
> Thanks for the effort to create this patch. Turns out we have already
> fixed this, and have it included in our 8.2.2 patch set, which we will be
> posting within the next week.
The 2.6.23 merge window is estimated to close on
On Thursday 19 July 2007 19:36, Olaf Kirch wrote:
> Can you confirm this by spraying the laptop with arp packets
> or broadcast pings while it's booting?
Sorry for the noise - didn't see your other message where you
described just that.
This sounds more like a hardware issue - Rx interrupt seems
Daniël Mantione <[EMAIL PROTECTED]> wrote:
> Op Thu, 19 Jul 2007, schreef Dmitry Torokhov:
>> On 7/14/07, Daniel Mantione <[EMAIL PROTECTED]> wrote:
> To make this discussion productive, I want to work towards a solution. I
> don't mind how I can make the keyboard work as it should, I just want
Florin,
Thanks for the effort to create this patch. Turns out we have already
fixed this, and have it included in our 8.2.2 patch set, which we will be
posting within the next week.
So James, don't pick this patch up, take the larger patch set instead.
Thanks.
-- james s
Florin Malita
On Thu, Jul 19, 2007 at 10:07:59AM -0700, Nishanth Aravamudan wrote:
> But I do think a second reason to do this is to make hugetlbfs behave
> like a normal fs -- that is read(), write(), etc. work on files in the
> mountpoint. But that is simply my opinion.
Mine as well.
-- wli
-
To
On Thu, 2007-07-19 at 19:38 +0200, Andi Kleen wrote:
> On Thursday 19 July 2007 19:31:56 Daniel Walker wrote:
>
> > >From my perspective a downside to sched_clock is that the math is
> > duplicated per architecture .. I think it would be a win to use the
> > generic functions if it's possible..
>
On Thu, 19 Jul 2007 01:43:14 +0200, jesper.juhl wrote:
> On 19/07/07, Greg Kroah-Hartman <[EMAIL PROTECTED]> wrote:
> > From: Tsugikazu Shibata <[EMAIL PROTECTED]>
> >
> > Add the japanese translation of the Documentation/HOWTO file.
> >
>
> A few comments below.
Jesper, Thank you very much for
>> [Andrei] VLAN_TX_SKB_CB() is perfect for that.
> [Patrick, Stephen] No its not. Its only legal to use while something has
> ownership
of the skb. Between VLAN devices and real devices qdiscs are
free to use it.
All right, using VLAN_TX_SKB_CB() is a bad idea. In that case, we need to amend
* Andi Kleen ([EMAIL PROTECTED]) wrote:
>
> > Ewww you plan to run this in SMP ? So you actually go byte
> > by byte changing pieces of instructions non atomically and doing
> > non-Intel's errata friendly XMC. You are really looking for trouble
> > there :) Two distinct errors can
* Olaf Kirch <[EMAIL PROTECTED]> wrote:
> On Thursday 19 July 2007 18:05, Ingo Molnar wrote:
> > that network-intense test also produced periodic broadcast packets that
> > got the e1000 out of its weird state before the tx timeout could hit.
> > Now that i've stopped the test, the network is
* Bill Davidsen <[EMAIL PROTECTED]> wrote:
> Bill Davidsen wrote:
> >Ingo Molnar wrote:
> >>* Bill Davidsen <[EMAIL PROTECTED]> wrote:
> >>
> Does the patch below help?
> >
> >Doesn't seem to apply against 2.6.22.1, I'm trying 2.6.22.6 as soon as
> >I recreate it.
>
> Applied to
On Thu, 19 Jul 2007, Milton Miller wrote:
(2) Upon start-up (by which I mean what happens after the user has pressed
the power button or something like that):
* check if the image is present (and valid) _without_ enabling ACPI (we
don't
do that now, but I see no reason for not
On 7/19/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> do we need to put __initdata just before =?
AFAIK gcc __attribute__ syntax allows both. It certainly seems to compile.
in include/linux/init.h
it said
"
* For initialized data:
* You should insert __initdata between the variable name and
On Thursday 19 July 2007 19:31:56 Daniel Walker wrote:
> >From my perspective a downside to sched_clock is that the math is
> duplicated per architecture .. I think it would be a win to use the
> generic functions if it's possible..
They can't be used because they're not cpu local. The whole
On Thu, 19 Jul 2007, Jens Axboe wrote:
> On Wed, Jul 18 2007, Hugh Dickins wrote:
> > On Wed, 18 Jul 2007, Jens Axboe wrote:
> > >
> > > Since I had my hands dirty already...
> >
> > Great, thanks. (There's also such a test in fs/nfs/direct.c,
> > but let's not trouble Trond until we've settled
On Thursday 19 July 2007 18:05, Ingo Molnar wrote:
> that network-intense test also produced periodic broadcast packets that
> got the e1000 out of its weird state before the tx timeout could hit.
> Now that i've stopped the test, the network is quiescent again and the
> e1000 hangs.
Can you
Denis Cheng wrote:
this memcpy looks so strange, in fact it's merely a pointer dereference,
so I change the parameter's type to refer it more directly,
this could make the memcpy not needed anymore.
in the function nbd_read_stat where nbd_find_request is only once called,
the parameter served
On Thu, 2007-07-19 at 19:22 +0200, Andi Kleen wrote:
> On Thursday 19 July 2007 19:15:38 Daniel Walker wrote:
> > On Thu, 2007-07-19 at 19:13 +0200, Andi Kleen wrote:
> > > > What about using the cycles2ns() clocksource helpers, it would eliminate
> > > > the duplication of the shift/multiply math
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
> Actually, given that when lsm was being introduced, lsm seemed to
> improve performance overall, have you taken any measurements to show
> that this is actually the case? Of course it makes sense that it would,
> but witjout measurements we do not
On Thursday 19 July 2007 17:22:38 Dmitry Torokhov wrote:
> Hi Andi,
>
> On 7/19/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> >
> > From: Thomas Gleixner <[EMAIL PROTECTED]>
> >
> > Replace the pcspkr private PIT lock by the global PIT lock to serialize the
> > PIT access all over the place.
> >
>
On Thu, Jul 19 2007, Pavel Emelyanov wrote:
> The elevator_ops's member "trim" is declared and called not like
> all the other ones. Was this deliberate?
It's not a elevator action like the others, it's not called during
request handling, only for shutdown. So the different naming is actually
ok,
On Thu, Jul 12, 2007 at 02:52:23PM +1000, Rusty Russell wrote:
> This is solely for the wakeup: you don't wake an mm 8)
>
> The mm reference is held as well under the big lguest_mutex (mm gets
> destroyed before files get closed, so we definitely do need to hold a
> reference).
>
> I just
Fix up mpsc.c to be aligned with Documentation/CodingStyle.
Also fix up some whitespace issues.
Signed-off-by: Mark A. Greer <[EMAIL PROTECTED]>
---
drivers/serial/mpsc.c | 684
1 file changed, 283 insertions(+), 401 deletions(-)
diff --git
Remove the duplicate definition of SUPPORT_SYSRQ in mpsc driver.
Signed-off-by: Mark A. Greer <[EMAIL PROTECTED]>
---
drivers/serial/mpsc.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/serial/mpsc.c b/drivers/serial/mpsc.c
index 0d75505..1311433 100644
---
On Thu, Jul 19, 2007 at 09:54:30AM -0700, Arjan van de Ven wrote:
> the next step after this patch is to have an option to get rid of all
> the function pointer chasing (which is expensive) for the case where you
> know you only want one security module (which you then can turn on or
> off)...
From: Stephane Chazelas <[EMAIL PROTECTED]>
Currently, the MPSC driver doesn't stop recieving characters when the
CREAD flag in termios->c_cflag is cleared. It should. Also, only start
receiving if its not already started.
Signed-off-by: Stephane Chazelas <[EMAIL PROTECTED]>
Signed-off-by:
Bill Davidsen wrote:
Ingo Molnar wrote:
* Bill Davidsen <[EMAIL PROTECTED]> wrote:
Does the patch below help?
Doesn't seem to apply against 2.6.22.1, I'm trying 2.6.22.6 as soon as
I recreate it.
Applied to 2.6.22-git9, building now.
-
To unsubscribe from this list: send the line
From: Carlos Sanchez <[EMAIL PROTECTED]>
The patch in commit ID f7232056bff5fe2d3bfeab35252a66ebaeb5bbde
stops (aborts) the MPSC's receive engine just before restarting it.
Unfortunately, it doesn't wait for the abort to complete before
restarting it which creates a race between the abort and the
On Thu, 19 Jul 2007, Stephen Smalley wrote:
> Not wanting to get into any flamewars here about selinux, but just FYI:
> security_sb_post_mountroot is obsolete and can be removed without harm
> to selinux; it is a leftover of selinux before we moved the initial
> policy load to userspace. These
On Thu, Jul 19 2007, Jeremy Fitzhardinge wrote:
> > Index: linux/block/blktrace.c
> > ===
> > --- linux.orig/block/blktrace.c
> > +++ linux/block/blktrace.c
> > @@ -41,7 +41,7 @@ static void trace_note(struct blk_trace
> >
> do we need to put __initdata just before =?
AFAIK gcc __attribute__ syntax allows both. It certainly seems to compile.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Satyam Sharma wrote:
Subject : ext4 build warnings
References : http://lkml.org/lkml/2007/7/18/420
Last known good : ?
Submitter : Jeff Garzik <[EMAIL PROTECTED]>
Caused-By : ?
Handled-By : Mingming Cao <[EMAIL PROTECTED]>
Status : unknown
Mingming Cao
On Thursday 19 July 2007 19:15:38 Daniel Walker wrote:
> On Thu, 2007-07-19 at 19:13 +0200, Andi Kleen wrote:
> > > What about using the cycles2ns() clocksource helpers, it would eliminate
> > > the duplication of the shift/multiply math .
> >
> > They are completely different from what
On Tue, 17 Jul 2007, Arjan van de Ven wrote:
> > 1) It all can be reduced to 4K + 4K by asuming all IRQ happen on one CPU.
>
> no it's separate stacks for soft and hard irqs, so it's really 4+4+4
Thanks, I missed that information. Unfortunately this change still does
not help if one of these
On Thu, 2007-07-19 at 19:13 +0200, Andi Kleen wrote:
> > What about using the cycles2ns() clocksource helpers, it would eliminate
> > the duplication of the shift/multiply math .
>
> They are completely different from what clocksource provides.
How so?
Daniel
-
To unsubscribe from this list:
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix docbook warnings:
Warning(linux-2.6.22-git12//drivers/base/power/main.c): no structured comments
found
Warning(linux-2.6.22-git12//include/linux/splice.h): no structured comments
found
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Quoting Arjan van de Ven ([EMAIL PROTECTED]):
>
> > Right, the ability to boot with security.capability=disabpled (or
> > whatever) and then load a custom module without having to use a whole
> > new kernel is something I'm sure end-users want.
> >
> > Especially since compiling a kernel which
From: Randy Dunlap <[EMAIL PROTECTED]>
Add kernel-doc entry in for:
Warning(linux-2.6.22-git12//include/linux/irq.h:177): No description found for
parameter 'last_unhandled'
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
include/linux/irq.h |1 +
1 file changed, 1 insertion(+)
---
* Bill Davidsen <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> >* Bill Davidsen <[EMAIL PROTECTED]> wrote:
> >
> >>>Does the patch below help?
>
> Doesn't seem to apply against 2.6.22.1, I'm trying 2.6.22.6 as soon as
> I recreate it.
the patch below is merged against 2.6.22.1-cfs-v19 -
Satyam Sharma wrote:
> On 7/19/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
>
>> Subject : Section mismatch: reference to .init.data:cpu_llc_id
>> (between 'set_cpu_sibling_map' and 'initialize_secondary')
>> References : http://lkml.org/lkml/2007/7/19/202
>> Last known good
201 - 300 of 1493 matches
Mail list logo
