Fix a preemption bug in kprobe_handler(). It has to call preempt_enable()
before returning.
I think this is critical on preemptive kernel.
Signed-off-by: Masami Hiramatsu <[EMAIL PROTECTED]>
---
arch/x86/kernel/kprobes.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Index:
On Tue, Dec 18, 2007 at 04:46:09PM -0500, Chuck Ebbert wrote:
> pnpacpi=off should work.
This does result in the graphics bar being placed at e000,
and does result in a system lockup when X starts. So it appears
as if there's really something there.
r~
--
To unsubscribe from this list:
On Sun, 9 Dec 2007 22:23:42 +0100
Marcin __lusarz <[EMAIL PROTECTED]> wrote:
> usb/storage/initializers.c: fix signedness difference
>
> Signed-off-by: Marcin __lusarz <[EMAIL PROTECTED]>
> ---
> drivers/usb/storage/initializers.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
This fix corrects the problem that early_identify_cpu() sets
cpu_index to '0' (needed when called by setup_arch) after
smp_store_cpu_info() had set it to the correct value.
The error shows up in 'cat /proc/cpuinfo' will all cpus = 0.
Signed-off-by: Mike Travis <[EMAIL PROTECTED]>
---
It appears that this patch is missing from the latest 2.6.24 git
kernel as well as the 2.6.24-rc5-mm1 patch?
> Mike, This issue still seems to be present in linus git tree. Perhaps
> the fix in -mm not pushed to mainline yet.
>
> Can you please raise the flag with Andrew, so that he can push it
Matt Mackall wrote:
Blech. Invoking the random pool machinery at oops time is moderately
safe, but not very shiny. Going through all the sprintf ugliness to
format it to an irrelevant UUID standard is not very shiny either. At
least refactor it so it's not duplicating code.
And I'd much rather
It appears that this patch is missing from the latest 2.6.24 git
kernel as well as the 2.6.24-rc5-mm1 patch?
> Mike, This issue still seems to be present in linus git tree. Perhaps
> the fix in -mm not pushed to mainline yet.
>
> Can you please raise the flag with Andrew, so that he can push it
On Tue, Dec 18, 2007 at 07:50:33PM +0800, Fengguang Wu wrote:
> On Tue, Dec 18, 2007 at 09:19:07AM +0100, Nick Piggin wrote:
> > On Sun, Dec 16, 2007 at 07:59:30PM +0800, Fengguang Wu wrote:
>
> > > + read_lock_irq(>tree_lock);
> > > + page = radix_tree_lookup(>page_tree, offset);
> > > + if
On Tue 18-12-07 14:50:07, Mark Fasheh wrote:
> On Tue, Dec 18, 2007 at 04:25:05PM +0100, Jan Kara wrote:
> > Although we don't allow writes over s_maxbytes, it can happen that a file's
> > size is larger than s_maxbytes. For example we can write the file from
> > a computer with a different
shashi59 wrote:
I am newbie for Linux Kernel.How can I read the memory area like the range
between to .Directly i read that area it shows some error
like this "unable to handle kernel paging request at virtual address
". So,I don't know, how to solve this error .Please
Add debugfs_create_s{8,16,32,64}. For these to work properly, we need to
remove a cast in libfs.
Cc: Johannes Berg <[EMAIL PROTECTED]>
To: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>
---
Greg,
here comes an implementation of
Linus Torvalds wrote:
On Tue, 18 Dec 2007, Richard Henderson wrote:
I've added dmesg, /proc/iomem, and lspci -v output to that bug.
Basically, we have
c000-cfff : free
ddf0-dfef : PCI Bus #04
e000-efff : pnp 00:0b
f000-fedf :
On Tue, 11 Dec 2007 16:38:46 +0100
[EMAIL PROTECTED] wrote:
> [PATCH 01/02]
>
> This patch computes msg_ctlmni to make it scale with system memory.
> msg_ctlmni is now set to make the message queues occupy 1/32 of the available
> memory.
>
> Some cleaning has also been done in the MSGXXX
On Tue, 11 Dec 2007 21:05:10 +0100
Daniel Ritz <[EMAIL PROTECTED]> wrote:
> [PATCH] usbtouchscreen: fix buffer overflow, make more egalax work
>
> fixes a buffer overflow in mutli-packet handling code. the overflow can only
> happen with eGalax devices and is even there very unlikely (only
groups_sort() can be quite long if user loads a large gid table.
This is because GROUP_AT(group_info, some_integer) uses an integer divide.
So having to do XXX thousand divides during one syscall can lead to very high
latencies. (NGROUPS_MAX=65536)
In the past (25 Mar 2006), an analog problem
Sorry, people are telling me that this is line wrapped. Which is strange
because claws-mail doesn't show that, will try to fix and resend anyway.
Sorry again for the noise.
--
Ciao
Stefano
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Linus Torvalds wrote:
On Tue, 18 Dec 2007, Chuck Ebbert wrote:
On 12/18/2007 04:09 PM, Linus Torvalds wrote:
I wonder what the heck is the point of that pnp entry. Just for fun, can
you try to just disable CONFIG_PNP, and see if it all works then?
pnpacpi=off should work.
PnP is also
Harald Dunkel wrote on 16-12-07 23:25:
Hi folks,
Is there a way to replace the system beep by something more
melodic?
I remember some 10 years ago there was a patch for the kernel
to call an external "beep daemon" playing an audio file instead
(no kidding). But it never worked very well.
On Wed, 19 Dec 2007 01:14:33 +0100
Eric Dumazet <[EMAIL PROTECTED]> wrote:
> groups_sort() can be quite long if user loads a large gid table.
>
> This is because GROUP_AT(group_info, some_integer) uses an integer divide.
> So having to do XXX thousand divides during one syscall can lead to very
Karsten Wiese wrote:
Hi,
while playing with jackd on 2.6.24-rcx, I found poll() timing out too early.
That is: earlier than its timeout argument specified.
Setting poll()'s timeout argument to "required timeout" + "1 jiffy in ms"
fixed it. Patch below should fix it too. Correct?
Untested.
On Tuesday 18 December 2007 02:09:15 pm Linus Torvalds wrote:
>
> On Tue, 18 Dec 2007, Richard Henderson wrote:
> >
> > I've added dmesg, /proc/iomem, and lspci -v output to that bug.
> >
> > Basically, we have
> >
> > c000-cfff : free
> > ddf0-dfef : PCI Bus #04
> >
* kinesis <[EMAIL PROTECTED]> wrote:
> my machine is 64bit running SLAMD64 v12 (slackware) Linux excalibur
> 2.6.24-rc4-kinesis-g94545bad #8 SMP Sun Dec 9 10:47:29 PST 2007 x86_64
> x86_64 x86_64 GNU/Linux
>
> Issuing the command hwclock --systohc and sometimes at boot --hctosys
> causes my
Hello!
We are running Debian with 2.6.22-2-686-bigmem on Dell Blade 1955 hardware
and get a Kernel Panic with oom + message that there are no processes
left to kill:
http://home.schottelius.org/~nico/unix/linux/oom_no_killable-2.6.22-1.jpeg
Anyone an idea, what's the cause for that? This error
Add debugfs_create_s{8,16,32,64}. For these to work properly, we need to remove
a cast in libfs.
Cc: Johannes Berg <[EMAIL PROTECTED]>
To: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>
---
Greg,
here comes an implementation of
People with HP Desktops (including me) encounter couple of DMI errors
during boot - dmi_save_oem_strings_devices: out of memory and dmi_string: out of
memory.
On some HP desktops the DMI data include OEM strings (type 11) out of
which only few are meaningful and most other are empty. DMI
Andrew Morton a écrit :
On Wed, 19 Dec 2007 01:14:33 +0100
Eric Dumazet <[EMAIL PROTECTED]> wrote:
groups_sort() can be quite long if user loads a large gid table.
This is because GROUP_AT(group_info, some_integer) uses an integer divide.
So having to do XXX thousand divides during one
On Tue, Dec 18, 2007 at 05:36:42PM +, Christoph Hellwig wrote:
>
> This was broken by my '[XFS] simplify xfs_create/mknod/symlink prototype',
> which assigned the re-shuffled ondisk dev_t back to the rdev variable in
> xfs_vn_mknod. Because of that i_rdev is set to the ondisk dev_t instead
>
Linus Torvalds wrote:
On Mon, 17 Dec 2007, Chuck Ebbert wrote:
Looks like a commit that I can't find in git due to the arch merge
has broken PCI address assignment. This patch by Richard Henderson
against 2.6.23 fixes it for x86_64:
--- linux-2.6.23.x86_64/arch/x86_64/kernel/e820.c
On Tue, Dec 18, 2007 at 05:59:11PM +1100, Lachlan McIlroy wrote:
> Please pull from the for-linus branch:
> git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
Linus, please don't pull this yet. A problem has been found in
the dirent fix, and we've just fixed another mknod related
On Tue, 18 Dec 2007, Erez Zadok wrote:
>
> Just curious, but didn't you (or someone else) mention that they wanted to
> do away with AOP_WRITEPAGE_ACTIVATE entirely? If these patches are for
> 2.6.25, would that be the right time?
That's right, it was me. Not forgotten, but I was anxious to
On Wednesday 19 December 2007 08:15, Rik van Riel wrote:
> I have seen soft cpu lockups in page_referenced_file() due to
> contention on i_mmap_lock() for different pages. Making the
> i_mmap_lock a reader/writer lock should increase parallelism
> in vmscan for file back pages mapped into many
On Tue, 18 Dec 2007, Erez Zadok wrote:
> In message <[EMAIL PROTECTED]>, Hugh Dickins writes:
> > In order to fix unionfs truncation, we need to move the lower notify_change
> > out of the loop in unionfs_setattr. But when I came to do that, I couldn't
> [...]
>
> Hugh, I want to understand how
On Tue, Dec 18, 2007 at 05:36:12PM +0100, Miguel Bot??n wrote:
> config IWL4965_SPECTRUM_MEASUREMENT
> - bool "Enable Spectrum Measurement in iw4965 driver"
> + bool "Enable Spectrum Measurement in iwl4965 driver"
> depends on IWL4965
> ---help---
> This option will
clocksource_watchdog can use a deferrable timer - reduces wakeups from
idle per second.
Signed-off-by: Parag Warudkar <[EMAIL PROTECTED]>
--- linux-2.6/kernel/time/clocksource.c 2007-12-07 10:04:43.0 -0500
+++ linux-2.6-work/kernel/time/clocksource.c2007-12-13 12:49:14.0
On Wednesday 19 December 2007 08:15, Rik van Riel wrote:
> Rework of a patch by Nick Piggin -- part 1 of 2.
>
> This patch:
>
> 1) defines the [CONFIG_]NORECLAIM_MLOCK sub-option and the
>stub version of the mlock/noreclaim APIs when it's
>not configured. Depends on [CONFIG_]NORECLAIM.
>
On 12/18/2007 07:11 PM, Robert Hancock wrote:
>> However, I wonder about that
>>
>> e000-efff : pnp 00:0b
>>
>> thing. I actually suspect that that whole allocation is literally
>> *meant* for that 256MB graphics aperture, but the kernel explicitly
>> avoids it because it's listed in
On Tue, 11 Dec 2007 10:01:20 +0100
Ingo Molnar <[EMAIL PROTECTED]> wrote:
> ok, just to make sure we are all synced up. I made 8 patches related to
> this problem category (and all the trickle effects). 3 are upstream
> already, 5 are pending for v2.6.25. One out of those 5 is an immaterial
>
Nico Schottelius wrote:
Hello!
We are running Debian with 2.6.22-2-686-bigmem on Dell Blade 1955 hardware
and get a Kernel Panic with oom + message that there are no processes
left to kill:
http://home.schottelius.org/~nico/unix/linux/oom_no_killable-2.6.22-1.jpeg
Anyone an idea, what's the
Reduces the number of wakeups from idle per second, makes powertop happy.
Signed-off-by: Parag Warudkar <[EMAIL PROTECTED]>
--- linux-2.6/net/sched/sch_generic.c 2007-12-07 10:04:43.0 -0500
+++ linux-2.6-work/net/sched/sch_generic.c 2007-12-16 17:57:05.0
-0500
@@ -213,7
On Tue, 18 Dec 2007 22:19:22 + (GMT)
Hugh Dickins <[EMAIL PROTECTED]> wrote:
> 1. Why is spin_lock_irqsave rather than spin_lock needed on mz->lru_lock?
> If it is needed, doesn't mem_cgroup_isolate_pages need to use it too?
>
When I wrote a patch to treat lru_lock (it was not per-zone yet.),
dmi_alloc() for CONFIG_X86_64 is defined to allocate from a static array
and it maintains a allocation index which is advanced each time allocation
is attempted - it gets incremented even if an allocation fails thereby
depriving any future request that may be small enough to be satisfied from
Am Mittwoch, 19. Dezember 2007 schrieb Robert Hancock:
>
> That seems fishy. What is your value of HZ and what is the timeout value
> that was passed in the bad case?
HZ set to 250, timeout to 4ms.
Time spent in poll() taken by clock_gettime(CLOCK_MONOTONIC, )
before and after poll()call: i.e
Handle errors in ISOFS correctly.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
fs/isofs/inode.c | 22 +-
1 files changed, 13 insertions(+), 9 deletions(-)
diff --git a/fs/isofs/inode.c b/fs/isofs/inode.c
index a854831..4d76594 100644
--- a/fs/isofs/inode.c
+++
sky2 can use deferrable timer for watchdog - reduces wakeups from idle per
second.
Signed-off-by: Parag Warudkar <[EMAIL PROTECTED]>
--- linux-2.6/drivers/net/sky2.c2007-12-07 10:04:39.0 -0500
+++ linux-2.6-work/drivers/net/sky2.c 2007-12-18 20:07:58.0 -0500
@@
On Tue, Dec 18, 2007 at 08:52:01AM -0600, Chris Friesen wrote:
>
> Looks like that did it. Why does specifying the family make a difference?
Because this is the only parameter that changes kernel behaviour.
Next step is to strace both commands with -s 16384 to see exactly
what the kernel reply
On Tue, Dec 18, 2007 at 07:55:37PM -0500, Chuck Ebbert wrote:
> You can boot with "pci=mmconf" to enable it.
Heh.
PCI: BIOS Bug: MCFG area at e000 is not E820-reserved
PCI: Not using MMCONFIG.
r~
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
In message <[EMAIL PROTECTED]>, Hugh Dickins writes:
> On Tue, 18 Dec 2007, Erez Zadok wrote:
> > In message <[EMAIL PROTECTED]>, Hugh Dickins writes:
> > > In order to fix unionfs truncation, we need to move the lower
> > > notify_change
> > > out of the loop in unionfs_setattr. But when I came
On Wed, 12 Dec 2007 18:00:12 -0800
Geoff Levand <[EMAIL PROTECTED]> wrote:
> > This stray down would cause a permanent sleep which doesn't seem correct.
> > The other uses of this semaphore appear fairly mutex like it's even
> > initialized
> > with init_MUTEX() .. So here a patch for removing
Andrew Morton <[EMAIL PROTECTED]> wrote:
> > - inode = ERR_PTR(ret);
> > + return NULL;
> > } else {
> > unlock_new_inode(inode);
> > }
> >
>
> Yup.
Nope. The correct fix is to make the various callers use
On Wed, 19 Dec 2007, David Chinner wrote:
>
> On Tue, Dec 18, 2007 at 05:59:11PM +1100, Lachlan McIlroy wrote:
> > Please pull from the for-linus branch:
> > git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
>
> Linus, please don't pull this yet. A problem has been found in
> the
On Tue, 18 Dec 2007, Linus Torvalds wrote:
>
> That question also brings up another issue: how come did we actually
> choose address 0xc000 with the original patch you sent in? If we can't
> find it in the parent resources, we shouldn't have accepted it even if it
> had room for it!
Use deferrable timer for watchdog. Reduces wakeups from idle per second.
Signed-off-by: Parag Warudkar <[EMAIL PROTECTED]>
--- linux-2.6/drivers/net/e1000/e1000_main.c2007-12-07 10:04:39.0
-0500
+++ linux-2.6-work/drivers/net/e1000/e1000_main.c 2007-12-18
20:38:38.0
On Tue, Dec 18, 2007 at 09:59:22PM +, Hugh Dickins wrote:
> add_to_swap_cache doesn't amount to much: merge it into its sole caller
> read_swap_cache_async. But we'll be needing to call __add_to_swap_cache
> from shmem.c, so promote it to the new add_to_swap_cache. Both were
> static, so
On Tue, 2007-12-18 at 17:10 -0800, Andrew Morton wrote:
> is correct. Although not exactly a thing of beauty.
This isn't the worst I've seen ;( .. Do you think the ending should fall
through instead of having two returns?
Daniel
--
To unsubscribe from this list: send the line "unsubscribe
Reduce wakeups from idle per second.
Signed-off-by: Parag Warudkar <[EMAIL PROTECTED]>
--- linux-2.6/drivers/net/e1000e/netdev.c 2007-12-07 10:04:39.0
-0500
+++ linux-2.6-work/drivers/net/e1000e/netdev.c 2007-12-18 20:45:59.0
-0500
@@ -3899,7 +3899,7 @@
On Dec 19, 2007 9:22 AM, David Howells <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > > - inode = ERR_PTR(ret);
> > > + return NULL;
> > > } else {
> > > unlock_new_inode(inode);
> > > }
>
On Wed, 19 Dec 2007 01:22:21 + David Howells <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > > - inode = ERR_PTR(ret);
> > > + return NULL;
> > > } else {
> > > unlock_new_inode(inode);
> > > }
On Tue, 2007-12-18 at 16:06 -0800, Andrew Morton wrote:
> On Tue, 11 Dec 2007 16:38:46 +0100
> [EMAIL PROTECTED] wrote:
>
> > [PATCH 01/02]
> >
> > This patch computes msg_ctlmni to make it scale with system memory.
> > msg_ctlmni is now set to make the message queues occupy 1/32 of the
> >
On Tue, 2007-12-18 at 08:50 -0500, Masami Hiramatsu wrote:
> Hi Harvey,
>
> Thank you for cleaning this up.
>
> Harvey Harrison wrote:
> > Subject: [PATCH] x86: kprobes leftover cleanups
> >
> > Eliminate __always_inline, all of these static functions are
> > only called once. Minor whitespace
Larry, thanks for being so patient so far. Tomorrow I plan to take my
laptop to somewhere with coffee and a wireless network. For now
though, can you tell me if these messages could be related:
PCI: Cannot allocate resource region 7 of bridge :00:05.0
PCI: Cannot allocate resource region 8 of
Karsten Wiese wrote:
Am Mittwoch, 19. Dezember 2007 schrieb Robert Hancock:
That seems fishy. What is your value of HZ and what is the timeout value
that was passed in the bad case?
HZ set to 250, timeout to 4ms.
Time spent in poll() taken by clock_gettime(CLOCK_MONOTONIC, )
before and after
Load each file decryption key only once
Signed-off-by: Trevor Highland <[EMAIL PROTECTED]>
---
fs/ecryptfs/crypto.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
index 70f7aab..949fe44 100644
---
On Dec 18, 2007 9:36 AM, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> This was broken by my '[XFS] simplify xfs_create/mknod/symlink prototype',
> which assigned the re-shuffled ondisk dev_t back to the rdev variable in
> xfs_vn_mknod. Because of that i_rdev is set to the ondisk dev_t instead
On Tue, 2007-12-18 at 13:09 -0800, Linus Torvalds wrote:
> It's not like 256MB is even as large as they come, half-gig graphics cards
> are getting to be fairly common at the high end, and X absolutely _has_ to
> be able to handle a 64-bit address for those.
We're now using a
On Dec 18, 2007 7:32 PM, Frans Pop <[EMAIL PROTECTED]> wrote:
> On Tuesday 18 December 2007, Glauber de Oliveira Costa wrote:
> > On Dec 18, 2007 6:54 PM, Frans Pop <[EMAIL PROTECTED]> wrote:
> > > Glauber de Oliveira Costa wrote:
> > > > What's left in processor_32.h and processor_64.h cannot be
On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote:
> Thanks. This is a bug in iwlwifi.
>
> The problem is actually another case where my workqueue debugging with
> lockdep is triggering a warning :))
>
> Here's the thing:
>
> iwl3945_cancel_deferred_work does
>
>
Change the type of cipher_code from u16 to u8.
Signed-off-by: Trevor Highland <[EMAIL PROTECTED]>
---
fs/ecryptfs/crypto.c |8
fs/ecryptfs/ecryptfs_kernel.h |4 ++--
fs/ecryptfs/keystore.c|8
3 files changed, 10 insertions(+), 10 deletions(-)
diff
On Wed, 05 Dec 2007 13:39:04 MST, Bjorn Helgaas said:
> > -#define PNP_MAX_PORT 24
> > +#define PNP_MAX_PORT 128
> > #define PNP_MAX_MEM12
> > #define PNP_MAX_IRQ2
> > #define PNP_MAX_DMA2
>
> I don't think we can
On Tue, Dec 18, 2007 at 05:19:04PM -0800, Linus Torvalds wrote:
>
>
> On Wed, 19 Dec 2007, David Chinner wrote:
> >
> > On Tue, Dec 18, 2007 at 05:59:11PM +1100, Lachlan McIlroy wrote:
> > > Please pull from the for-linus branch:
> > > git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git
On Tue, 18 Dec 2007, Richard Henderson wrote:
>
> Heh.
>
> PCI: BIOS Bug: MCFG area at e000 is not E820-reserved
> PCI: Not using MMCONFIG.
Well, that at least confirms that e000 is indeed the mmconfig area.
One of these days we'll trust the ACPI resource data enough that we can
use
David Howells wrote:
> Stephen Smalley <[EMAIL PROTECTED]> wrote:
>>> That sounds too SELinux specific. How do I do it so that it works for any
>>> LSM?
>>>
>> You can't. There is no LSM for userspace; LSM specifically disavowed
>> any common userspace API, and that was one of our
Stephen Smalley wrote:
>> It is if I have to maintain a special pieces of code for each possible LSM.
>> One piece for SELinux, one piece for AppArmour, one piece for Smack, one
>> piece
>> for Casey's security system. That sounds like a pain.
>>
> All your code has to do is invoke a
On 12/18/2007 05:10 PM, Andrew Morton wrote:
> On Wed, 12 Dec 2007 18:00:12 -0800
> Geoff Levand <[EMAIL PROTECTED]> wrote:
>
>> > This stray down would cause a permanent sleep which doesn't seem correct.
>> > The other uses of this semaphore appear fairly mutex like it's even
>> > initialized
On Tue, Dec 18, 2007 at 06:04:58PM -0800, Andrew Morton wrote:
> Nobody seems to look after hppfs. I'll resend the fat and hostfs patches to
> maintainers for a review, please.
It's mine - I'll take a look at it.
Jeff
--
Work email - jdike at linux dot intel
Hi
Masami Hiramatsu wrote:
> Fix a preemption bug in kprobe_handler(). It has to call preempt_enable()
> before returning.
> I think this is critical on preemptive kernel.
Sorry, this patch has a mistake.
>
> Signed-off-by: Masami Hiramatsu <[EMAIL PROTECTED]>
> ---
> arch/x86/kernel/kprobes.c
This driver reports voltage, temperature and fan sensor readings
on an ADT7473 chip. The ADT7467 chip seems to share some registers
with this one, so it may be possible to add support for it, though
the therm_adt746x driver seems to cover it ok on a PPC Mac.
Signed-off-by: Darrick J. Wong
L: entries should be email addresses
Change L:http entries to W:http
Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
---
diff --git a/MAINTAINERS b/MAINTAINERS
index 3c7db62..907094f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2025,26 +2025,26 @@ S: Supported
INTEL PRO/WIRELESS 2100
Al Viro wrote:
On Tue, Dec 18, 2007 at 11:00:16PM +, Al Viro wrote:
On Tue, Dec 18, 2007 at 05:46:21PM -0500, Mark Lord wrote:
Why does link(2) not support hard-linking across bind mount points
of the same underlying filesystem ?
Because it gives you a security boundary around a subtree.
Mark Lord wrote:
But.. pity there's no mount flag override for smaller systems,
where bind mounts might be more useful with link(2) actually working.
I don't see it. You always can make hard link on the underlying
filesystem. If you need to make it on the bound mount, that is, if you
can't
Hi Ingo:
I noticed that local_bh_disable is now always out-of-line. The
change was made when TRACE_IRQFLAGS was added. However, with
TRACE_IRQFLAGS off, local_bh_disable does exactly the same work
as before. In particular, it does pretty much the same as what
preempt_disable does and the
Remove the old alarms sysfs hack and replace it with per-sensor alarm files.
Also don't read the second alarm register if it's not needed.
Signed-off-by: Darrick J. Wong <[EMAIL PROTECTED]>
---
drivers/hwmon/adt7470.c | 97 ++-
1 files changed, 86
I did some testing on special-file copyup in unionfs, whereby unionfs calls
vfs_mknod on a lower f/s to create (copyup) a device. The copyup
functionality worked fine when unionfs was stacked on top of all file
systems other than xfs. I found out that when I create a device with
on xfs, then I
Hi
> > rmap: try_to_unmap_file() required new cond_resched_rwlock().
> > To reduce code duplication, I recast cond_resched_lock() as a
> > [static inline] wrapper around reworked cond_sched_lock() =>
> > __cond_resched_lock(void *lock, int type).
> > New cond_resched_rwlock() implemented as
Harvey Harrison wrote:
> On Tue, 2007-12-18 at 08:50 -0500, Masami Hiramatsu wrote:
>> Hi Harvey,
>>
>> Thank you for cleaning this up.
>>
>> Harvey Harrison wrote:
>>> Subject: [PATCH] x86: kprobes leftover cleanups
>>>
>>> Eliminate __always_inline, all of these static functions are
>>> only
We are pleased to announce the 2.6.23.11-rt14 tree, which can be
downloaded from the location:
http://www.kernel.org/pub/linux/kernel/projects/rt/
Changes since 2.6.23.9-rt13
- ported to 2.6.23.11
- Add ifdef CONFIG_SMP around variable in sched_rt.c (Remy Bohmer)
- Removed extra
Hi Rik-san,
> To keep the maximum amount of necessary work reasonable, we scale the
> active to inactive ratio with the size of memory, using the formula
> active:inactive ratio = sqrt(memory in GB * 10).
Great.
why do you think best formula is sqrt(GB*10)?
please tell me if you don't mind.
On Tue, 2007-12-18 at 23:43 -0500, Masami Hiramatsu wrote:
> Harvey Harrison wrote:
> > On Tue, 2007-12-18 at 08:50 -0500, Masami Hiramatsu wrote:
> >> Hi Harvey,
> >>
> >> Thank you for cleaning this up.
> >>
> >> Harvey Harrison wrote:
> >>> Subject: [PATCH] x86: kprobes leftover cleanups
> >>>
__always_inline on some static functions was to ensure they ended
up in the .kprobes.text section. Mark this explicitly.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/x86/kernel/kprobes.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On 2007.12.18 13:08:09 +, Zhenyu Wang wrote:
>
> Here're three patches below:
>
> - intel_iommu-explicit-export-current-graphics-dmar-status.patch
>
> This exports current status of graphics dma remap engine, which
> depends on current platform iommu support, kernel config or runtime
This patch changes the x86 PCI code to disable IO and/or Memory
decoding on a PCI device when a resource of that type failed to
be allocated.
This is done to avoid having unallocated dangling BARs enabled
that might try to decode on top of other devices.
If a proper resource is assigned later
On Tuesday 18 December 2007 18:23:53 Rusty Russell wrote:
> On Tuesday 18 December 2007 17:46:15 Srinivasa Ds wrote:
> > Rusty Russell wrote:
> > > The downside is that this might make backtraces through (discarded)
> > > init functions harder to read on some archs.
> >
> > I think it is better to
[agp-mm] [intel_iommu] explicit export current graphics dmar status
To make it possbile to tell other modules about curent
graphics dmar engine status, that could decide if graphics
driver should remap physical address to dma address.
Also this one trys to make dmar_disabled really present
[agp-mm] [AGP] Add generic support for graphics dma remapping
New driver hooks for support graphics memory dma remapping
are introduced in this patch. It makes generic code can
tell if current device needs dma remapping, then call driver
provided interfaces for mapping and unmapping. Change has
--- Crispin Cowan <[EMAIL PROTECTED]> wrote:
> Stephen Smalley wrote:
> >> It is if I have to maintain a special pieces of code for each possible
> LSM.
> >> One piece for SELinux, one piece for AppArmour, one piece for Smack, one
> piece
> >> for Casey's security system. That sounds like a
[agp-mm] [AGP] intel_agp: add support for graphics dma remapping on G33
When graphics dma remapping engine is active, we must fill
gart table with dma address from dmar engine, as now graphics
device access to graphics memory must go through dma remapping
table to get real physical address.
Add
Harvey Harrison wrote:
> __always_inline on some static functions was to ensure they ended
> up in the .kprobes.text section. Mark this explicitly.
It is good to me.
Thanks!
>
> Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
Acked-by: Masami Hiramatsu <[EMAIL PROTECTED]>
> ---
>
Just saw this again:
[ 5667.086055] BUG: sleeping function called from invalid context at
kernel/fork.c:401
[ 5667.087314] in_atomic():1, irqs_disabled():0
[ 5667.088210]
[ 5667.088212] Call Trace:
[ 5667.089104] [] show_stack+0x80/0xa0
[ 5667.089106]
Hello Robert,
Robert Hancock [Tue, Dec 18, 2007 at 06:43:22PM -0600]:
> How much RAM is in these machines?
8 GiB
> If you're running tons of memory, it
> really is better to run a 64-bit kernel if possible.
Sure? Afaik that results in a bit slower access to memory and appart
from being able
Hugh Dickins wrote:
> Here's a couple of patches to get memcgroups working better with tmpfs
> and shmem, in conjunction with the tmpfs patches I just posted. There
> will be another to come later on, but I shouldn't wait any longer to get
> these out to you.
>
Hi, Hugh,
Thank you so much for
Based on the recommendation and observations of Hugh Dickins,
page_cgroup_assign_cgroup() is not required. This patch replaces it with
a VM_BUG_ON, so that we can catch them in free_hot_cold_page()
Signed-off-by: Balbir Singh <[EMAIL PROTECTED]>
---
mm/page_alloc.c |2 +-
1 file changed,
701 - 800 of 816 matches
Mail list logo
