On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
[...]
> > /*
> > * Do not allocate memory (or fail in any way) in machine_kexec().
> > * We are past the point of no return, committed to rebooting now.
> > */
> > -NORET_TYPE void machine
Hi,
On Tue, 11 Dec 2007 12:12:59 +1030
David Newall <[EMAIL PROTECTED]> wrote:
> H. Peter Anvin wrote:
> > David Newall wrote:
> >
> > I think a single ISA bus transaction is 1 µs, so two of them back to
> > back should be 2 µs, not 8 µs...
>
> Exactly. You think it's 2us, but the documentatio
On 11-12-07 02:25, H. Peter Anvin wrote:
David Newall wrote:
Where did the 8us delay come from? The documentation and source is
careful not to say how long the delay is. Would changing it to, say
1us, be technically wrong? Is code that requires 8us correct?
I think a single ISA bus transa
Hi, linus
kernel.org web download is not available yet, isn't it?
Regards
dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http:/
On Dec 10, 2007 8:48 PM, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> Neil Horman <[EMAIL PROTECTED]> writes:
>
> Almost there.
>
>
>
> > On Mon, Dec 10, 2007 at 06:08:03PM -0700, Eric W. Biederman wrote:
> >> Neil Horman <[EMAIL PROTECTED]> writes:
> >>
> >
> >>
> >> Ok. This test is broken.
On Sat, Dec 08, 2007 at 08:52:11PM +0100, Ingo Molnar wrote:
> so even today's upstream kernel, which has 'ancient' SLUB code, SLAB and
> SLUB have essentially the same linecount:
>
> $ wc -l mm/slab.c mm/slub.c
> 4478 mm/slab.c
> 4125 mm/slub.c
>
> (and while linecount != complex
From: Ananth N Mavinakayanahalli <[EMAIL PROTECTED]>
This patch builds samples/kprobes/kretprobe_example.c only on archs that
support kretprobes. Thanks to Sam Ravnborg for Kconfig suggestions.
V2: Updated dependency on CONFIG_KRETPROBES
Signed-off-by: Ananth N Mavinakayanahalli <[EMAIL PROTECTE
The patch 04fbfdc14e5f48463820d6b9807daa5e9c92c51f implemented bdi per
device dirty threshold. It works well.
However, the period for proportion calculation may be too large.
For 8G memory, the calc_period_shift() will return 19 as the shift.
When we switch writing operation between different disk
From: Ananth N Mavinakayanahalli <[EMAIL PROTECTED]>
This patch adds CONFIG_HAVE_KRETPROBES to the arch//Kconfig file
for relevant architectures with kprobes support. This facilitates easy
handling of in-kernel modules (like samples/kprobes/kretprobe_example.c)
that depend on kretprobes being pres
On Mon, Dec 10, 2007 at 10:10:01AM -0500, Mathieu Desnoyers wrote:
> * Ananth N Mavinakayanahalli ([EMAIL PROTECTED]) wrote:
> > On Mon, Dec 10, 2007 at 11:13:07AM +0100, Sam Ravnborg wrote:
> > > On Mon, Dec 10, 2007 at 03:22:22PM +0530, Ananth N Mavinakayanahalli
> > > wrote:
> > > > From: Anant
Alan Cox wrote:
In any case, my machine does not have an ISA bus. Why should it? It's
a laptop!
Yes it does. The branding spec said "No ISA bus" so it was renamed "LPC"
and hidden internally, but its alive and well.
Well that, plus it was serialized and uses PCI electricals and timing,
he
Andi Kleen wrote:
My machine in question, for example, needs no waiting within CMOS_READs
at all. And I doubt any other chip/device needs waiting that isn't
I don't know about CMOS, but there were definitely some not too ancient
systems (let's say not more than 10 years) who required IO dela
It's been a week, and I promised to be a good boy and try to follow my
release rules, so here is the next -rc.
Things _have_ slowed down, although I'd obviously be lying if I said we've
got all the regressions handled and under control. They are being worked
on, and the list is shrinking, but
KAMEZAWA Hiroyuki wrote:
> On Tue, 11 Dec 2007 10:44:36 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
>
>> Looks good to me.
>>
>> Acked-by: Balbir Singh <[EMAIL PROTECTED]>
>>
>> TODO:
>>
>> 1. Should we have vm_events for the memory controller as well?
>>May be in the longer term
>>
>
> A
On Tue, 11 Dec 2007 10:44:36 +0530
Balbir Singh <[EMAIL PROTECTED]> wrote:
> Looks good to me.
>
> Acked-by: Balbir Singh <[EMAIL PROTECTED]>
>
> TODO:
>
> 1. Should we have vm_events for the memory controller as well?
>May be in the longer term
>
ALLOC_STALL is recoreded as failcnt, I th
KAMEZAWA Hiroyuki wrote:
> Without this, ALLOCSTALL and PGSCAN_DIRECT increases too much unless
> there is no memory shortage.
>
> against 2.6.24-rc4-mm1.
>
> -Kame
>
> ==
> Some amount of accounting is done while page reclaiming.
>
> Now, there are 2 types of page reclaim (if memory controller
KAMEZAWA Hiroyuki wrote:
> Balbir-san, could you review this update ?
>
> --
> Documentation updates for memory controller.
>
> Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
>
> Index: linux-2.6.24-rc4-mm1/Documentation/controllers/memory.txt
>
I noticed this vmlinux layout on i686 (where CONFIG_X86_L1_CACHE_SHIFT = 7) :
c06cdab4 d pid_caches_lh
c06cdb00 d qlowmark
c06cdb04 d qhimark
c06cdb08 d blimit
c06cdb80 d rcu_ctrlblk
c06cdc80 d rcu_bh_ctrlblk
This means that qlowmark, qhimark and blimit use a whole 128 bytes cache line.
Linker
Neil Horman <[EMAIL PROTECTED]> writes:
Almost there.
> On Mon, Dec 10, 2007 at 06:08:03PM -0700, Eric W. Biederman wrote:
>> Neil Horman <[EMAIL PROTECTED]> writes:
>>
>
>>
>> Ok. This test is broken. Please remove the == 1. You are looking
>> for == (1 << 18). So just saying: "if (htcfg
Fixing:
CHECK drivers/net/pcmcia/pcnet_cs.c
drivers/net/pcmcia/pcnet_cs.c:523:15: warning: symbol 'hw_info' shadows an
earlier one
drivers/net/pcmcia/pcnet_cs.c:148:18: originally declared here
Signed-off-by: Richard Knutsson <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/pcmcia/pcnet_cs.
Use 'max(x,y)' instead of 'x < y ? y : x'.
Signed-off-by: Richard Knutsson <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/pcmcia/axnet_cs.c b/drivers/net/pcmcia/axnet_cs.c
index 8d910a3..96931cc 100644
--- a/drivers/net/pcmcia/axnet_cs.c
+++ b/drivers/net/pcmcia/axnet_cs.c
@@ -1091,8 +1091,8 @
Fixing:
CHECK drivers/net/pcmcia/fmvj18x_cs.c
drivers/net/pcmcia/fmvj18x_cs.c:1205:6: warning: symbol 'i' shadows an earlier
one
drivers/net/pcmcia/fmvj18x_cs.c:1179:9: originally declared here
Signed-off-by: Richard Knutsson <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/pcmcia/fmvj18x_c
Fixing:
CHECK drivers/net/pcmcia/3c574_cs.c
drivers/net/pcmcia/3c574_cs.c:695:7: warning: symbol 'i' shadows an earlier one
drivers/net/pcmcia/3c574_cs.c:636:6: originally declared here
Signed-off-by: Richard Knutson <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/pcmcia/3c574_cs.c b/driver
Fixing:
CHECK drivers/net/pcmcia/3c574_cs.c
drivers/net/pcmcia/3c574_cs.c:194:13: warning: dubious bitfield without
explicit `signed' or `unsigned'
drivers/net/pcmcia/3c574_cs.c:196:14: warning: dubious bitfield without
explicit `signed' or `unsigned'
Signed-off-by: Richard Knutsson <[EMAIL
Fixing:
CHECK drivers/net/pcmcia/axnet_cs.c
drivers/net/pcmcia/axnet_cs.c:994:5: warning: symbol 'ax_close' was not
declared. Should it be static?
drivers/net/pcmcia/axnet_cs.c:1017:6: warning: symbol 'ei_tx_timeout' was not
declared. Should it be static?
Signed-off-by: Richard Knutsson <[EM
On Monday 10 December 2007 13:31, Jonathan Corbet wrote:
> Hey, Daniel,
>
> I'm just getting around to looking at this. One thing jumped out at me:
> > + if (bio->bi_throttle) {
> > + struct request_queue *q = bio->bi_queue;
> > + bio->bi_throttle = 0; /* or detect multiple e
On Mon, Dec 10, 2007 at 06:08:03PM -0700, Eric W. Biederman wrote:
> Neil Horman <[EMAIL PROTECTED]> writes:
>
>
> Ok. This test is broken. Please remove the == 1. You are looking
> for == (1 << 18). So just saying: "if (htcfg & (1 << 18))" should be clearer.
>
Fixed. Thanks!
> > + printk
Dmitry Adamushko found that the current implementation of the RT
balancing code left out changes to the sched_setscheduler and rt_mutex_setprio.
This patch addresses this issue by adding methods to the schedule classes to
handle being switched out of (switched_from) and being switched into
(switch
To make the main sched.c code more agnostic to the schedule classes.
Instead of having specific hooks in the schedule code for the RT class
balancing. They are replaced with a pre_schedule, post_schedule
and task_wake_up methods. These methods may be used by any of the classes
but currently, only t
From: Gregory Haskins <[EMAIL PROTECTED]>
We had support for overlapping cpuset based rto logic in early prototypes that
is no longer used, so clean it up.
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
kernel/sched_rt.c | 33 -
[Sorry if this is a repost, but I had a problem with quilt mail, and
I don't know if my original post made it out. Unfortunately, I didn't
save the original "prolog" file, and so this has to be rewritten
from scratch, and I don't even remember the original subject :-/ ]
This patch series goe
From: Gregory Haskins <[EMAIL PROTECTED]>
The overload set/clears were originally idempotent when this logic was first
implemented. But that is no longer true due to the addition of the atomic
counter and this logic was never updated to work properly with that change.
So only adjust the overload
Matthew Wilcox wrote:
>> - add more PCI device IDs
>> - support for adapters based on Marvell IOP
>
> Are you sure it's a good idea to do this? This patch is 1200 lines long
> ... the same size as the existing driver:
>
> $ wc drivers/scsi/hptiop.*
> 947 2273 24531 drivers/scsi/hptiop.c
> 25
Balbir-san, could you review this update ?
--
Documentation updates for memory controller.
Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
Index: linux-2.6.24-rc4-mm1/Documentation/controllers/memory.txt
===
--- linux-2.6.24-rc
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
> To support jumping between two kernels, before jumping to (executing)
> the new kernel and jumping back to the original kernel, the devices
> are
On Dec 10, 2007 6:14 PM, David Brownell <[EMAIL PROTECTED]> wrote:
> On Monday 10 December 2007, eric miao wrote:
> > +config GPIO_PCA9539_GENERIC_IRQ
> > +bool " Generic IRQ support for PCA9539"
> > +depends on GPIO_PCA9539=y
>
> Also depends on GENERIC_HARDIRQS, right? (You should let
> the Kcon
Without this, ALLOCSTALL and PGSCAN_DIRECT increases too much unless
there is no memory shortage.
against 2.6.24-rc4-mm1.
-Kame
==
Some amount of accounting is done while page reclaiming.
Now, there are 2 types of page reclaim (if memory controller is used)
- global: shortage of (global) page
From: Michael Rubin <[EMAIL PROTECTED]>
Fixing a bug where writing to large files while concurrently writing to
smaller ones creates a situation where writeback cannot keep up with the
traffic and memory baloons until the we hit the threshold watermark. This
can result in surprising latency spikes
David Newall wrote:
Exactly. You think it's 2us, but the documentation doesn't say. The _p
functions are generic inasmuch as they provide an unspecified delay.
Drivers which work across platforms, and which use _p, therefore have
different delays on different platforms. Should the length
David Newall wrote:
H. Peter Anvin wrote:
David Newall wrote:
Where did the 8us delay come from? The documentation and source is
careful not to say how long the delay is. Would changing it to, say
1us, be technically wrong? Is code that requires 8us correct?
I think a single ISA bus trans
Your change looks correct to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
H. Peter Anvin wrote:
David Newall wrote:
Where did the 8us delay come from? The documentation and source is
careful not to say how long the delay is. Would changing it to, say
1us, be technically wrong? Is code that requires 8us correct?
I think a single ISA bus transaction is 1 µs, so tw
Your change looks correct to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Your change looks correct to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> On 12/09, Eric W. Biederman wrote:
>>
>> Oleg below is my proof of concept patch, which really needs to be
>> broken up into a whole patch series, so the changes are small
>> enough we can do a thorough audit on them. Anyway take a look
>> and see what
On Mon, Dec 10, 2007 at 05:35:25PM -0600, Matt Mackall wrote:
> > I must have missed this. Can you please explain again? For a layman it
> > looks like a paranoid application cannot read 500 Bytes from
> > /dev/random without blocking if some other application has previously
> > read 10 Kilobytes f
This looks fine to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
David Newall wrote:
Where did the 8us delay come from? The documentation and source is
careful not to say how long the delay is. Would changing it to, say
1us, be technically wrong? Is code that requires 8us correct?
I think a single ISA bus transaction is 1 µs, so two of them back to
back
The difference between ip=off and ip=::off has been a cause of much
confusion. Document how each behaves, and do not contradict ourselves
by saying that "off" is the default when in fact "any" is the default
and is descibed as being so lower in the file.
Signed-off-by: Amos Waterland <[EMAIL
This looks fine to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> Sorry to reply to myself, but do we have consensus on this patch? I'd like to
> figure out its disposition if possible.
What the patch tries to do looks like the right thing. So if we can get
a version that is clean and actually works we should merge it.
Eric
--
To unsubscribe from this lis
This looks fine to me.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Starting to catch up on some old patch review today. This one has my ACK.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
From: Julia Lawall <[EMAIL PROTECTED]>
Date: Sun, 9 Dec 2007 21:03:55 +0100 (CET)
> From: Julia Lawall <[EMAIL PROTECTED]>
>
> Recently, Wang Chen submitted a patch
> (d30f53aeb31d453a5230f526bea592af07944564) to move a call to netif_rx(skb)
> after a subsequent reference to skb, because netif_rx
From: Julia Lawall <[EMAIL PROTECTED]>
Date: Sun, 9 Dec 2007 21:05:30 +0100 (CET)
> From: Julia Lawall <[EMAIL PROTECTED]>
>
> Recently, Wang Chen submitted a patch
> (d30f53aeb31d453a5230f526bea592af07944564) to move a call to netif_rx(skb)
> after a subsequent reference to skb, because netif_rx
From: Julia Lawall <[EMAIL PROTECTED]>
Date: Sun, 9 Dec 2007 21:02:31 +0100 (CET)
> From: Julia Lawall <[EMAIL PROTECTED]>
>
> Recently, Wang Chen submitted a patch
> (d30f53aeb31d453a5230f526bea592af07944564) to move a call to netif_rx(skb)
> after a subsequent reference to skb, because netif_rx
Neil Horman <[EMAIL PROTECTED]> writes:
> On Fri, Dec 07, 2007 at 09:21:44AM -0500, Neil Horman wrote:
>> On Fri, Dec 07, 2007 at 01:22:04AM -0800, Yinghai Lu wrote:
>> > On Dec 7, 2007 12:50 AM, Yinghai Lu <[EMAIL PROTECTED]> wrote:
>> > >
>> > > On Dec 6, 2007 4:33 PM, Eric W. Biederman <[EMAIL
Where did the 8us delay come from? The documentation and source is
careful not to say how long the delay is. Would changing it to, say
1us, be technically wrong? Is code that requires 8us correct?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
On Tue, 11 Dec 2007 01:01:25 +0100
Guillaume Chazarain <[EMAIL PROTECTED]> wrote:
> Arjan van de Ven <[EMAIL PROTECTED]> wrote:
>
> > the frequency of both cores is the maximum of what linux sets each
> > core to;
>
> Do you mean that the cpufreq code can be confused about the actual
> frequency
Thanos Chatziathanassiou wrote:
help
I KNOW OF PLACES, ACTIONS, AND THINGS. MOST OF MY VOCABULARY
DESCRIBES PLACES AND IS USED TO MOVE YOU THERE. TO MOVE TRY
WORDS LIKE FOREST, BUILDING, DOWNSTREAM, ENTER, EAST, WEST
NORTH, SOUTH, UP, OR DOWN. I KNOW ABOUT A FEW SPECIAL OBJECTS,
LIKE A BLACK R
On Mon, 2007-12-10 at 17:31 -0500, Vivek Goyal wrote:
> [..]
> >
> > -#define KEXEC_ON_CRASH 0x0001
> > -#define KEXEC_ARCH_MASK 0x
> > +#define KEXEC_ON_CRASH 0x0001
> > +#define KEXEC_PRESERVE_CPU 0x0002
> > +#define KEXEC_PRESERVE_CPU_EXT 0x0004
> > +#d
On Mon, 2007-12-10 at 14:55 -0500, Vivek Goyal wrote:
> On Fri, Dec 07, 2007 at 03:53:30PM +, Huang, Ying wrote:
> > This patch implements the functionality of jumping between the kexeced
> > kernel and the original kernel.
> >
>
> Hi,
>
> I am just going through your patches and trying to u
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> do_wait(WSTOPPED) assumes that p->state must be == TASK_STOPPED, this is not
> true if the leader is already dead. Check SIGNAL_STOP_STOPPED instead and use
> ->signal->group_exit_code.
>
> This patch is not complete if not buggy. At the very minimum it
Jan Beulich wrote:
> Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
>
Acked-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> arch/x86/kernel/head_32.S |2 +-
> arch/x86/xen/setup.c |2 +-
> arch/x86/xen/xen-head.S |2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> --
Rene Herman wrote:
By the way, David, it would be interesting if you could test 0xed. If
your problem is some piece of hardware getting upset at LPC bus aborts
it's not going to matter and we'd know an outb delay is just not an
option on your system at least. You said you could quickly reprod
> The GT-64111 system controller doesn't provide any kind of mapping
> functionality that would help here. So legacy port addressing can only
> work by exploiting aliases due to incomplete decoding of legacy ioport
> addreses by the VT82C586 - but direct addressing is impossible.
Ok, that explai
(linux-ide cc'ed)
trash can wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have tolerated this problem for a year and do not post to this list in
haste. I have posted on forums and searched the community over the past
year. I have looked at the list archive on gossamer-threads.com for
s
On Mon, 10 Dec 2007 17:39:22 +0530 (IST) Poonam_Aggrwal-b10812 <[EMAIL
PROTECTED]> wrote:
>
> +++ b/arch/powerpc/sysdev/qe_lib/qe.c
> @@ -149,22 +149,116 @@ EXPORT_SYMBOL(qe_issue_cmd);
> */
> static unsigned int brg_clk = 0;
>
> -unsigned int get_brg_clk(void)
> +u32 get_brg_clk(enum qe_cloc
On Mon, 2007-12-10 at 23:07 +, Alan Cox wrote:
> > Forcing controllers into native mode tends to be something that really
> > only works on -some- controllers. I'm happy to have a hack to try to do
> > that on all of them on powermacs, because the range of controllers that
> > might not be in
Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> the frequency of both cores is the maximum of what linux sets each core to;
Do you mean that the cpufreq code can be confused about the actual
frequency of the cores? That sounds like a big problem.
Thanks for any insight.
--
Guillaume
--
To unsubs
On Tue, Dec 11, 2007 at 07:43:03AM +1100, Benjamin Herrenschmidt wrote:
> > > :00:09.1 IDE interface: VIA Technologies, Inc.
> > > VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> > > (prog-if 8a [Master SecP PriP])
> > > Flags: bus master, fast Back2Back, medium devs
Stefano Brivio <[EMAIL PROTECTED]> wrote:
> Sorry for disappearing. Anyway, yes, those patches fixed it. Precision in
> delays isn't that good when using my crappy unstable TSC (mdelay(2000)
> causes delays between 2 and 2.9 seconds) but it's not depending on frequency
> changes anymore. So I'd sa
On Tue, 11 Dec 2007 00:34:33 +0100
Stefano Brivio <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Dec 2007 00:04:25 +0100
> Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >
> > * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >
> > > * Andrew Morton <[EMAIL PROTECTED]> wrote:
> > >
> > > > > what do you think? Rig
--- David Howells <[EMAIL PROTECTED]> wrote:
> Casey Schaufler <[EMAIL PROTECTED]> wrote:
>
> > That happens to me when interfaces are described in SELinux terms. I
> > still don't care much for multiple contexts, and I don't have a good
> > grasp of how you'll deal with Smack, or any LSM other
--- David Howells <[EMAIL PROTECTED]> wrote:
> Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > From a config file whose pathname would be provided by libselinux (ala
> > the way in which dbusd imports contexts), or directly as a context
> > returned by a libselinux function.
>
> That sounds to
Casey Schaufler <[EMAIL PROTECTED]> wrote:
> That happens to me when interfaces are described in SELinux terms. I
> still don't care much for multiple contexts, and I don't have a good
> grasp of how you'll deal with Smack, or any LSM other than SELinux.
Me neither. I understand SELinux somewhat
On Tue, 11 Dec 2007 00:04:25 +0100
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> > * Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > > what do you think? Right now i've got them queued up for 2.6.25 in
> > > > both the scheduler-devel and the x86-dev
On Tue, Dec 11, 2007 at 12:06:43AM +0100, Marc Haber wrote:
> On Sun, Dec 09, 2007 at 10:16:05AM -0600, Matt Mackall wrote:
> > On Sun, Dec 09, 2007 at 01:42:00PM +0100, Marc Haber wrote:
> > > On Wed, Dec 05, 2007 at 03:26:47PM -0600, Matt Mackall wrote:
> > > > The distinction between /dev/random
Stephen Smalley <[EMAIL PROTECTED]> wrote:
> From a config file whose pathname would be provided by libselinux (ala
> the way in which dbusd imports contexts), or directly as a context
> returned by a libselinux function.
That sounds too SELinux specific. How do I do it so that it works for any
On Friday 07 December 2007 12:13:35 am Shaohua Li wrote:
> On Thu, 2007-12-06 at 02:24 +0800, Bjorn Helgaas wrote:
> > Index: linux-mm/drivers/pnp/driver.c
> > ===
> > --- linux-mm.orig/drivers/pnp/driver.c 2007-11-30 13:58:25.000
> Forcing controllers into native mode tends to be something that really
> only works on -some- controllers. I'm happy to have a hack to try to do
> that on all of them on powermacs, because the range of controllers that
> might not be in native mode in the first place there is pretty small,
> and
On Mon, Dec 10, 2007 at 09:08:53AM -0600, Bob Tracy wrote:
> Ivan Kokshaysky wrote:
> > For now I have reassigned the bug #9457 to myself and will gradually hack
> > into udev...
>
> Thanks... Let me know if there's anything useful I can do to help.
It turns out to be yet another strncpy() bug t
On Sun, Dec 09, 2007 at 10:16:05AM -0600, Matt Mackall wrote:
> On Sun, Dec 09, 2007 at 01:42:00PM +0100, Marc Haber wrote:
> > On Wed, Dec 05, 2007 at 03:26:47PM -0600, Matt Mackall wrote:
> > > The distinction between /dev/random and /dev/urandom boils down to one
> > > word: paranoia. If you are
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > > what do you think? Right now i've got them queued up for 2.6.25 in
> > > both the scheduler-devel and the x86-devel git trees - but can
> > > submit them for 2.6.24 if it's better if we did them there
Hi Kenji-san,
I have been thinking about this problem for quite a bit, and
think that there are no good solutions...
* Kenji Kaneshige <[EMAIL PROTECTED]>:
> On my system, hotplug slots themselves can be added, removed
> and replaced with the ohter type of I/O box.
>> Are you talking abo
On Sat, Dec 08, 2007 at 04:07:14AM +0530, Balbir Singh wrote:
> Signed-off-by: Balbir Singh <[EMAIL PROTECTED]>
Looks good to me. Sure, it could be fleshed out to something more
generic and in common code, but this is small and simple and doesn't
bloat the kernel much as it stands, and it has val
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> > what do you think? Right now i've got them queued up for 2.6.25 in
> > both the scheduler-devel and the x86-devel git trees - but can
> > submit them for 2.6.24 if it's better if we did them there. I've got
> > no strong opinion either way.
>
> p
On Fri, Dec 07, 2007 at 03:53:30PM +, Huang, Ying wrote:
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
> To support jumping between two kernels, before jumping to (executing)
> the new kernel and jumping back to the original kernel
--- Stephen Smalley <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-12-10 at 21:08 +, David Howells wrote:
> > Stephen Smalley <[EMAIL PROTECTED]> wrote:
> >
> > > Otherwise, only other issue I have with this interface is it won't
> > > generalize to dealing with nfsd, where we want to set the act
Quoting Andrew Morton <[EMAIL PROTECTED]>:
> On Mon, 10 Dec 2007 16:32:18 +0300 "Denis V. Lunev" <[EMAIL PROTECTED]> wrote:
> >
>
> Plese don't top-post. It makes replying to you rather awkward.
>
> > could you, plz, check patch sent by Eric above in this thread.
> >
> > I have tried it on my
> I pulled from your tree to look over the patches, and noticed that it
> looks like several commits were merged improperly. It looks like they
> were auto merged or something from an email, and the commit message
> contains the email headers, rather than just the commit message in the
> body. T
Hi,
On Dec 10, 2007 11:31 PM, Jonathan Corbet <[EMAIL PROTECTED]> wrote:
> I'm just getting around to looking at this. One thing jumped out at me:
>
> > + if (bio->bi_throttle) {
> > + struct request_queue *q = bio->bi_queue;
> > + bio->bi_throttle = 0; /* or detect mu
On Mon, 10 Dec 2007 10:59:20 -0800
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> >
> > My ia64 allmodconfig build has taken
> >
> > akpm 15700 89.6 0.0 8256 700 pts/4RN+ 03:09 10:41 bc -q
> > kernel/timeconst.bc
> >
> > 11 minutes so far. fc6/x86_64.
> >
Hello,
I think, I'm experiencing the same problem:
09:16:34 : NETDEV WATCHDOG: eth0: transmit timed out
09:16:34 : eth0: Got tx_timeout. irq:
09:16:34 : eth0: Ring at 37e5
09:16:34 : eth0: Dumping tx registers
09:16:34 : 0: 00ff 0003 025003ca
> > map_phys_fmr
>
> In fact, we do use hCalls there. Our hardware doesn't actually support FMRs,
> so we translate a "map FMR" into a "reallocate PMR", which doesn't work
> without hCalls. What's more, the hCalls involved (e.g. H_FREE_RESOURCE)
> might well return H_LONG_BUSY, so the wh
On Mon, 2007-10-15 at 22:25 +1000, Nick Piggin wrote:
> On Monday 15 October 2007 04:19, Siddha, Suresh B wrote:
> > On Sun, Oct 14, 2007 at 11:01:02AM +1000, Nick Piggin wrote:
> > > This is just a really quick hack, untested ATM, but one that
> > > has at least a chance of working (on x86).
> >
Hey, Daniel,
I'm just getting around to looking at this. One thing jumped out at me:
> + if (bio->bi_throttle) {
> + struct request_queue *q = bio->bi_queue;
> + bio->bi_throttle = 0; /* or detect multiple endio and err? */
> + atomic_add(bio->bi_throttle,
Zach Brown wrote:
The following patches are a substantial refactoring of the syslet code. I'm
branding them as the v7 release of the syslet infrastructure, though they
represent a signifiant change in focus.
My current focus is to see the most fundamental functionality brought to
maturity. To
On Mon, 2007-12-10 at 21:08 +, David Howells wrote:
> Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > Otherwise, only other issue I have with this interface is it won't
> > generalize to dealing with nfsd, where we want to set the acting context
> > to a context we obtain from or determine ba
Linus, please pull from the for-linus branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
for-linus
to receive the following FireWire subsystem update.
This considerably enhances compatibility of the new firewire-ohci driver
with a number of controllers. It s
1 - 100 of 315 matches
Mail list logo
