The following change was checked into 'warnings' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
commit b1c9131343597967d8fcc042f59e4ed36ea2855f
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed Jul 18 01:47:39 2007 -0400
[X86-64] make flush_tlb_kernel_range()
The following change was checked into 'warnings' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
commit 61470a24062de01853fb922ec4a81dcd1c0ba1d0
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed Jul 18 01:43:05 2007 -0400
drivers/video/aty/radeon_base: fix
The following change was checked into 'warnings' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
commit 5330916f5a11d8b7def46a6b3e14a831684032f5
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed Jul 18 01:41:29 2007 -0400
drivers/base/core: improve
John Stoffel napsal(a):
> Zdenek> I get kernel oopses when I run powertop on my old BP6 SMP dual
> Zdenek> Celeron board.
>
> Zdenek> In case more details are needed - send me a replay.
>
> Since it's tainted with a proprietary module, we can't do anything
> here. Please re-create the oops
Okay, successfully reproduced here. Will hunt down.
--
tejun
-
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
On Wed, 18 Jul 2007 05:49:50 +0100 (BST) Hugh Dickins <[EMAIL PROTECTED]> wrote:
> > With your patch, I have reproduced the panic:
>
> That is... surprising to me.
To me also. I'd like to double-check the code which Joe actually
tested, please - have a sneaking suspicion that the 2.6.22
On Wed, Jul 18, 2007 at 11:00:39AM +0530, Balbir Singh wrote:
> Thinking out loud again, can we add can_destory() callbacks?
I remember suggesting such a callback long before :
http://marc.info/?l=linux-kernel=117576241131788=2
--
Regards,
vatsa
-
To unsubscribe from this list: send
Balbir Singh wrote:
> Paul (??) Menage wrote:
>> On 7/17/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>>> without too much knowledge of each other. BTW, what are the semantics
>>> of css_put() is it expected to free the container/run the release agent
>>> when the reference count of the
On Tue, 2007-07-17 at 21:48 -0400, Dmitry Torokhov wrote:
> On Tuesday 17 July 2007 14:16, Soeren Sonnenburg wrote:
> > On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
> [...]
> > > How many boxes did you try this patch on?
> >
> > Mine plus 1 other. However please note that Matthews
With sysfs_fill_super() converted to use sysfs_get_inode(), there is
no user of sysfs_init_inode() outside of fs/sysfs/inode.c. Make it
static.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/inode.c |2 +-
fs/sysfs/sysfs.h |1 -
2 files changed, 1 insertion(+), 2 deletions(-)
While making sysfs indoes hashed, sysfs root inode was left out. Now
that nlink accounting depends on the inode being on the hash, sysfs
root inode nlink isn't adjusted properly.
Put sysfs root inode on the inode hash by allocating it using
sysfs_get_inode() like other sysfs inodes. While at
Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for input subsystem.
Changelog:
-
Dmitry Torokhov (3):
Input: add driver
>I think this is an important question. If we merge the local SA
>stuff, then are we creating a problem for dealing with QoS?
Yes - I do believe that merging PR caching and QoS together will be difficult.
I don't think the problems are insurmountable, but I can't say that I have a
definite
Brandon Philips wrote:
> Signed-off-by: Brandon Philips <[EMAIL PROTECTED]>
Acked-by: Tejun Heo <[EMAIL PROTECTED]>
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, 17 Jul 2007, Roland Dreier wrote:
>
> > Anyway, here's a totally untested cleanup that compiles but probably
> > doesn't work, because I didn't check that I did the right thing with all
> > the pointer arithmetic (ie when I change "wqe" to a real structure pointer
> > instead of
Signed-off-by: Brandon Philips <[EMAIL PROTECTED]>
---
Documentation/driver-model/devres.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/driver-model/devres.txt
b/Documentation/driver-model/devres.txt
index 6c8d8f2..8569072 100644
---
M: [EMAIL PROTECTED]
L: [EMAIL PROTECTED]
We get the following compile error if CONFIG_BLOCK isn't enabled:
CC arch/powerpc/kernel/setup_32.o
In file included from arch/powerpc/kernel/setup_32.c:14:
include/linux/ide.h:558: error: expected specifier-qualifier-list before
Yes I know that X does it; I'm trying to write a new windowing system
which also does that, and the question is how they did it. I would
have expected if I just open /dev/tty1, set raw mode, and set some
termios flags I'd get every key press and release; and it would be my
choice whether to use
On Wed, 18 Jul 2007, Joe Jin wrote:
>
> With your patch, I have reproduced the panic:
That is... surprising to me. (I hadn't been able to reproduce it with
or without the patches: maybe I just need to try harder.) Please post
your gcc --version, and the disassembly (objdump -d) output for
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
arch/sparc/Kconfig |3 +++
arch/sparc64/Kconfig |3 +++
include/asm-sparc64/io.h |5 -
3 files changed, 6 insertions(+), 5 deletions(-)
This is part of a rash attempt to make allmodconfig builds work for sparc
and
On Wed, 2007-07-11 at 17:16 +0530, Balbir Singh wrote:
> Zhang, Yanmin wrote:
> > struct task_delay_info is used by per process block I/O delay statistics
> > feature which is useful in kernel. This struct is not optimized.
> >
> > My patch against kernel 2.6.22 shrinks it a half.
> >
> > 1)
Paul (??) Menage wrote:
> On 7/17/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>> without too much knowledge of each other. BTW, what are the semantics
>> of css_put() is it expected to free the container/run the release agent
>> when the reference count of the container_subsys_state drops to zero?
Another things I stumbled on lately when toying with some mm rework on
powerpc, is the lack of any locking when manipulating init_mm page
tables. We don't use the pte_lockptr (well, we don't know where the pmd
comes from here, we can't toy around with that struct page), but we
don't use anything
On Wed, 18 Jul 2007, Satyam Sharma wrote:
> On Wed, 18 Jul 2007, Al Viro wrote:
>
> > On Wed, Jul 18, 2007 at 01:24:46AM +0200, Uwe Kleine-Konig wrote:
> > > [...]
> > > a52b1752c07 introduces usage of the WARN_ON macro in , but
> > > doesn't pull in . ( is not enough, at least
> > > for arm,
> Quite frankly, I don't quite understand where you get those enormous balls
> you have, that you can then talk about how ugly it is to just add a "= 0"
> that shuts up a compiler warning. That's the _least_ ugly part of the
> whole damn function!
The clanking when I walk annoys people in
On Wed, 18 Jul 2007, Matthew Garrett wrote:
On Tue, Jul 17, 2007 at 08:19:32AM -0700, [EMAIL PROTECTED] wrote:
On Tue, 17 Jul 2007, Matthew Garrett wrote:
Powering off rather than using S4 means you lose most wakeup device
support. That would be a functional regression compared to the current
On Tue, 17 Jul 2007, Roland Dreier wrote:
>
> I think this patch (on top of the previous one) actually makes the
> code clearer
Quite frankly, calling this "making the code clearer" is a bit ridiculous.
That code still is absolute *crap* from a readability angle. It doesn't
follow any sane
On Wed, 18 Jul 2007, Al Viro wrote:
> On Wed, Jul 18, 2007 at 01:24:46AM +0200, Uwe Kleine-Konig wrote:
> > [...]
> > a52b1752c07 introduces usage of the WARN_ON macro in , but
> > doesn't pull in . ( is not enough, at least
> > for arm, because WARN_ON uses printk there.)
> >
> > The obvious
May be I miss something obvious but most information that was available
in /proc/ide is missing under /sys. At the very least, Mandriva hardware
detection expects /proc/ide/hdX/model; nothing close is under /sys.
Are there any plans to extend IDE /sys interface to provide full range of
Roland Dreier wrote:
In this case the code is basically
u32 x;
for (n = 0; cond; ++n) {
...
if (!n)
x = something;
...
}
if (n) {
...
use(x);
> > But to be fair, it will be difficult to enable both QoS and local PR
> > caching. To me, this would be the strongest reason against using it.
> > However, QoS places additional burden on the SA, which will make scaling
> > even more challenging.
>
> my understanding is that the local
On 7/18/07, Matt Mackall <[EMAIL PROTECTED]> wrote:
> > * Adds new derivative of romfs filesystem (rom2fs) with
> > block aligned regular file data to bring performance
> > parity with ext2/3. This is about 225% of the read
> > speed of the existing romfs.
Doesn't that make these
> > So setting a variable to something meaningless (guaranteeing that a
> > garbage value is used in case of a bug) just to shut up a warning makes
> > no sense -- it's no safer than leaving the code as is.
>
> Wrong.
>
> It's safer for two reasons:
> - now everybody will see the
Hello,
Sorry about late response. -EWASPUBLICHOLIDAY. That's something I've
broken apparently. Will fix soon.
Thanks.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On 7/11/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
Dave Young wrote:
> Hi, randy
>
> how about remove the spec links in the header files as well.
>
> Subject:
> Remove document links in hpet header files.
>
> Signed-off-by: Dave Young <[EMAIL PROTECTED]>
Agreed. Acked-by: Randy Dunlap <[EMAIL
On Tue, 17 Jul 2007, Roland Dreier wrote:
>
> So setting a variable to something meaningless (guaranteeing that a
> garbage value is used in case of a bug) just to shut up a warning makes
> no sense -- it's no safer than leaving the code as is.
Wrong.
It's safer for two reasons:
- now
I think this patch (on top of the previous one) actually makes the
code clearer, and also makes it smaller:
add/remove: 0/0 grow/shrink: 0/3 up/down: 0/-41 (-41)
function old new delta
mthca_tavor_post_send 13441335 -9
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
net/core/dev.c | 28 ++--
1 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index 17c9cbd..6357f54 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2715,20 +2715,6 @@
this two functions could share the dev->_xmit_lock acquired context.
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
net/core/dev.c | 16
1 files changed, 4 insertions(+), 12 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index 3ba63aa..17c9cbd 100644
---
Because this function is only called by unregister_netdevice,
this moving could make this non-global function static,
and also remove its declaration in netdevice.h;
Any further, function __dev_addr_discard is also just called by
dev_mc_discard and dev_unicast_discard, keeping this two functions
> I don't buy that performance argument, in this case. You are already
> dirtying the same cacheline with other variable initializations.
>
> Like I noted in the changeset description (hey, this is precisely why
> I included it, so that we could have this discussion), IMO the flow of
>
On 07/17/2007 01:27 AM, Matt Mackall wrote:
Larger soft pages waste tremendous amounts of memory (mostly in page
cache) for minimal benefit on, say, the typical desktop. While there
are workloads where it's a win, it's probably on a small percentage of
machines.
So it's absolutely no help in
On Wed, 18 Jul 2007, Tony Breeds wrote:
>
> On Tue, Jul 17, 2007 at 06:44:26PM -0700, Linus Torvalds wrote:
>
> > Thanks. I assume this has been boot-tested too, and everything else from
> > the PCI merge was ok?
>
> *cough* umm the boot test fails. I'll look harder at the merge, and
>
On Tue, Jul 17, 2007 at 06:44:26PM -0700, Linus Torvalds wrote:
> Thanks. I assume this has been boot-tested too, and everything else from
> the PCI merge was ok?
*cough* umm the boot test fails. I'll look harder at the merge, and
provide a better patch.
Yours Tony
linux.conf.au
On Tue, Jul 17, 2007 at 08:19:32AM -0700, [EMAIL PROTECTED] wrote:
> On Tue, 17 Jul 2007, Matthew Garrett wrote:
> >Powering off rather than using S4 means you lose most wakeup device
> >support. That would be a functional regression compared to the current
> >code.
>
> only if the kexec isn't
On Tuesday 17 July 2007 8:24:55 pm Linus Torvalds wrote:
> On Tue, 17 Jul 2007, James Morris wrote:
> > These are updated Netlabel/SELinux changes from Paul, reworked so that
> > they don't break userspace. Michal says they work for him. Please apply
> > for 2.6.23.
>
> They don't work AT ALL
Sasa Ostrouska wrote:
I want to ask one question about a custom resolution in the console.
I have a Sony Vaio Laptop VGN-SZ2VP/X, the screen resolution is
1280x800, now I'm using the vga=773 which is an 1024x768 but this is
ugly as I get a border of about 2-3cm on one the sides of the screen.
So
On Tuesday 17 July 2007 14:16, Soeren Sonnenburg wrote:
> On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
> > Hi,
> >
> > On 7/17/07, Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:
> > >
> > > err_free_buffer:
> > > @@ -656,6 +699,7 @@ static void atp_disconnect(struct usb_interface
> >
On Wed, 18 Jul 2007, Tony Breeds wrote:
>
> Fix compile failure in arch/powerpc/kernel/pci-common.c
Thanks. I assume this has been boot-tested too, and everything else from
the PCI merge was ok?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
With your patch, I have reproduced the panic:
Unable to handle kernel paging request at 186a RIP:
[] __alloc_pages+0x2f/0x2c3
PGD 72595067 PUD 72594067 PMD 0
Oops: [1] SMP
CPU 0
Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables cpufreq_ondemand
dm_mirror
On 14/07/07 17:05 -0400, Andrew Paprocki wrote:
> Tony,
>
> Do you have the patch working already? I'd love to try this out in the
> meantime on the LX system I am developing with at the moment. I'm
> assuming you worked this into the existing Arcom framework (gxfb) and
> pulled the necessary
Jonathan Campbell <[EMAIL PROTECTED]> writes:
> I wrote a set of patches out of concern that even if you compile a 386
> kernel a lot of code irrelevent to legacy machines still
> remains. Things like the Pentium TSC register, DMI information, ESCD
> parsing, and the use of CPUID do not apply to
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> Sorry, but I can't be bothered splitting it up. Greg, Chris: please just
> apply the bits which apply and drop the other bits if that's OK.
Yup
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Ingo Molnar wrote:
* Ian Kent <[EMAIL PROTECTED]> wrote:
ah! It passes in a low-res time source into a high-res time interface
(pthread_cond_timedwait()). Could you change the time(NULL) + 1 to
time(NULL) + 2, or change it to:
gettimeofday(, NULL);
wait.tv_sec++;
On Tue, 17 Jul 2007 13:31:29 +0200
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> The fourth argument of sys_futex is ignored when op == FUTEX_WAKE_OP,
> but futex_wake_op expects it as its nr_wake2 parameter.
>
> The only user of this operation in glibc is always passing 1, so this
> bug had no
On Tue, Jul 17, 2007 at 11:04:57AM -0700, Bret Towe wrote:
> this is off my g4 mac mini
> latest git as of when this email was sent
> config file attached
Hi Bret,
the patch below will fix it.
From: Tony Breeds <[EMAIL PROTECTED]>
Fix compile failure in arch/powerpc/kernel/pci-common.c
On Tue, 17 Jul 2007 14:36:10 +0200
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> > On every open/close one struct seq_operations leaks.
> > Kudos to /proc/slab_allocators.
> >
> > Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
>
> ouch ...
>
On Tue, 17 Jul 2007 13:47:32 +0100
David Howells <[EMAIL PROTECTED]> wrote:
> + if (type == AFS_LOCK_READ &&
> + vnode->flags & (1 << AFS_VNODE_READLOCKED)) {
Here we use
vnode->flags & (1 << foo)
> + set_bit(AFS_VNODE_LOCKING, >flags);
and elsewhere we use
On Wed, Jul 18, 2007 at 09:18:36AM +0900, Paul Mundt wrote:
> On Tue, Jul 17, 2007 at 10:00:08PM +0200, Jan Engelhardt wrote:
> > 81cda6626178cd55297831296ba8ecedbfd8b52d is first bad commit
> > commit 81cda6626178cd55297831296ba8ecedbfd8b52d
> > Author: Christoph Lameter <[EMAIL PROTECTED]>
> >
On Wed, 18 Jul 2007, Michal Piotrowski wrote:
>
> Once again I tested both patches, build log shows only this
You clearly didn't test them with CONFIG_NETLABEL set to off, or you have
a buggy compiler.
You had
int netlbl_enabled(void)
{
return 0;
}
Rusty Russell wrote:
> The default function points to the internal stats...
>
Right you are.
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 http://vger.kernel.org/majordomo-info.html
Please
Linus Torvalds pisze:
>
> On Tue, 17 Jul 2007, James Morris wrote:
>> These are updated Netlabel/SELinux changes from Paul, reworked so that
>> they don't break userspace. Michal says they work for him. Please apply
>> for 2.6.23.
>
> They don't work AT ALL for me:
>
>
On Wed, 18 Jul 2007 09:18:36 +0900
Paul Mundt <[EMAIL PROTECTED]> wrote:
> --- a/include/linux/slob_def.h
> +++ b/include/linux/slob_def.h
> @@ -33,14 +33,4 @@ static inline void *__kmalloc(size_t size, gfp_t flags)
> return kmalloc(size, flags);
> }
>
> -/**
> - * kzalloc - allocate
On Tue, 17 Jul 2007, Rafael J. Wysocki wrote:
On Tuesday, 17 July 2007 14:48, Huang, Ying wrote:
On Tue, 2007-07-17 at 01:13 -0700, [EMAIL PROTECTED] wrote:
however, since the resume designed for ACPI won't work would the following
approach work
1. boot one kernel
2. setup a kexec the same
[ James, please remeber to cc: linux-ide on IDE patches, thanks. ]
On Wednesday 18 July 2007, Jeff Garzik wrote:
> James Bottomley wrote:
> > @@ -1052,9 +1054,10 @@ int generic_ide_ioctl(ide_drive_t *drive, struct
> > file *file, struct block_device
> > int err, (*setfunc)(ide_drive_t *,
On Tue, 17 Jul 2007, James Morris wrote:
>
> These are updated Netlabel/SELinux changes from Paul, reworked so that
> they don't break userspace. Michal says they work for him. Please apply
> for 2.6.23.
They don't work AT ALL for me:
security/selinux/ss/sidtab.o: In function
On 07/18/2007 01:39 AM, Jesper Juhl wrote:
On 17/07/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
At hch's suggestion I rewrote the separate IRQ stack configurability
patch into one making IRQ stacks mandatory and unconfigurable, and
hence enabled with 8K stacks.
For what it's
From: James Bottomley <[EMAIL PROTECTED]>
Subject: Re: block/bsg.c
Date: Tue, 17 Jul 2007 13:53:54 -0500
> On Tue, 2007-07-17 at 12:19 +0200, Jens Axboe wrote:
> > > > Since Linus is happily snoring by now, could you test and see if the
> > > > tree works for you?
> > >
> > > It works for me.
Current -git kernels sometimes lock up on my computer during boot. I
guess it happens about 10-20% of the time. I first saw this maybe a
week ago, but never with kernels <= 2.6.22.
The last reported info on the console is that named is started.
SysRq-T still works and reports the non-sleeping
On Tue, Jul 17, 2007 at 10:00:08PM +0200, Jan Engelhardt wrote:
> 81cda6626178cd55297831296ba8ecedbfd8b52d is first bad commit
> commit 81cda6626178cd55297831296ba8ecedbfd8b52d
> Author: Christoph Lameter <[EMAIL PROTECTED]>
> Date: Tue Jul 17 04:03:29 2007 -0700
>
> Slab allocators:
> I can't speak for Fedora, but RHEL disables XFS in their kernel likely
> because it is known to cause problems with 4K stacks.
-was- - the SGI folks submitted patches to deal with some gcc problems
with stack usage.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Mon, 16 Jul 2007 16:15:28 -0700
"Ray Lee" <[EMAIL PROTECTED]> wrote:
> On 7/16/07, Rene Herman <[EMAIL PROTECTED]> wrote:
> > Yes but it's also an argument that the 4K stacks don't make the _current_
> > situation without CONFIG_4KSTACKS selected worse and given that you trust
> > that current
On Wed, 18 Jul 2007, Ben Dooks wrote:
>
> This has broken _all_ ARM builds, due to using WARN_ON()
> in this header.
I think Al's patch already fixes that, since now it's back to being a
macro, and thus the whole WARN_ON() is only visible where the macro is
_used_, not in the header itself.
On Tue, 17 Jul 2007 22:40:06 +0200
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> In the future some drivers may need to use ACPI to determine the low power
> states in which to place their devices, but to provide the drivers with this
>
On Tue, 17 Jul 2007, Jeremy Katz wrote:
On Tue, 17 Jul 2007, Thomas Gleixner wrote:
With 2.6.14 or with current mainline ?
I haven't been keeping notes quite as studiously as I should have been, but
this just occurred with 2.6.22.1 + the hrt6 patch + your proposed fix:
Scratch that. I
On Wed, Jul 18, 2007 at 12:54:17AM +0100, Ben Dooks wrote:
> This has broken _all_ ARM builds, due to using WARN_ON()
> in this header. Warn on needs and this is
> needs to make it compile cleanly on ARM
> which is unfortuantely what we where trying to avoid in
> the first place?
>
> This patch
From: Doug Thompson <[EMAIL PROTECTED]>
Updated the EDAC kernel documentation
Signed-off-by: Doug Thompson <[EMAIL PROTECTED]>
---
edac.txt | 192 ++-
1 file changed, 165 insertions(+), 27 deletions(-)
Index:
On 07/18/2007 01:19 AM, Bodo Eggert wrote:
Please post a list of things you have designed, so I can avoid them.
- The ability to read
- The ability to understand
You're doing a hell of a job already.
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
From: Doug Thompson <[EMAIL PROTECTED]>
Some simple fixes to properly reference counter values from
the block attribute level of edac_device objects. Properly
sequencing the array pointer was added, resulting in correct
identification of block level attributes from their base
class functions.
From: Ranganathan Desikan <[EMAIL PROTECTED]>
New EDAC driver for the i82975x memory controller chipset
Used on ASUS motherboards
Signed-off-by: [EMAIL PROTECTED]
Signed-off-by: Ranganathan Desikan <[EMAIL PROTECTED]>
Signed-off-by: Doug Thompson <[EMAIL PROTECTED]>
---
Kconfig|7
From: Douglas Thompson <[EMAIL PROTECTED]>
Update maintainer information on edac components
Signed-off-by: Doug Thompson <[EMAIL PROTECTED]>
---
MAINTAINERS | 24 +---
1 file changed, 21 insertions(+), 3 deletions(-)
Index: linux-2.6.22-rc6-mm1/MAINTAINERS
From: Doug Thompson <[EMAIL PROTECTED]>
Fix mutex locking deadlock on the device controller linked list.
Was calling a lock then a function that could call the same lock.
Moved the cancel workq function to outside the lock
Added some short circuit logic in the workq code
Added comments of
From: Doug Thompson <[EMAIL PROTECTED]>
This EDAC patch set was applied against: 2.6.22-rc6-mm1
6 Patches in this set
1) tidying EXPORT_SYMBOL to EXPORT_SYMBOL_GPL modes, plus blank line removal
2) workq reset deadlock fix. Moved teardown outside of critical section
3) new i82975x driver
From: Doug Thompson <[EMAIL PROTECTED]>
Change EXPORT_SYMBOLs to EXPORT_SYMBOLS_GPL
Tidy changes: blank lines, inline removal, add comment
Signed-off-by: Doug Thompson <[EMAIL PROTECTED]>
---
Index: linux-2.6.22-rc6-mm1/drivers/edac/edac_stub.c
On Tue, Jul 17, 2007 at 02:40:42PM -0700, David Miller wrote:
> From: Al Viro <[EMAIL PROTECTED]>
> Date: Tue, 17 Jul 2007 22:29:46 +0100
>
> > ... or we end up with header include order problems from hell.
> > E.g. on m68k this is 100% fatal - local_irq_enable() there
> > wants preempt_count(),
On Wed, Jul 18, 2007 at 01:24:46AM +0200, Uwe Kleine-K?nig wrote:
> Hello,
>
> kernel/timer.c (and some others as arch/arm/kernel/irq.c) include
> , but not
>
> a52b1752c07 introduces usage of the WARN_ON macro in , but
> doesn't pull in . ( is not enough, at least
> for arm, because WARN_ON
On Tue, 2007-07-17 at 22:12 +0200, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2007-07-17 at 21:32 +0200, Ingo Molnar wrote:
> > > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > >
> > > > I do get flash 9 (I know, not the best example) and
From: Paul Moore <[EMAIL PROTECTED]>
These changes will make NetLabel behave like labeled IPsec where there is
an access check for both labeled and unlabeled packets as well as
providing the ability to restrict domains to receiving only labeled
packets when NetLabel is in use. The changes to
From: Paul Moore <[EMAIL PROTECTED]>
Create a new NetLabel KAPI interface, netlbl_enabled(), which reports on
the current runtime status of NetLabel based on the existing
configuration. LSMs that make use of NetLabel, i.e. SELinux, can use this
new function to determine if they should perform
Hi Linus,
These are updated Netlabel/SELinux changes from Paul, reworked so that
they don't break userspace. Michal says they work for him. Please apply
for 2.6.23.
The following changes since commit 489de30259e667d7bc47da9da44a0270b050cd97:
Linus Torvalds (1):
Merge branch
On Tue, 2007-07-17 at 10:45 -0400, John Stoffel wrote:
> utz> I have to recompile the fedora kernel rpms (fc6, f7) with 8k
> utz> stacks on my i686 server. It's using NFS -> XFS -> DM -> MD
> utz> (raid1) -> IDE disks. With 4k stacks it crash (hang) within
> utz> minutes after using NFS. With 8k
On Tue, 2007-07-17 at 07:28 -0700, Jeremy Fitzhardinge wrote:
> Stephen Hemminger wrote:
> >> +struct netfront_info {
> >> + struct list_head list;
> >> + struct net_device *netdev;
> >> +
> >> + struct net_device_stats stats;
> >>
> >
> > There is now a net_device_stats element inside
On Tue, 17 Jul 2007 12:06:56 -0400, rob wrote:
> On Sunday 15 July 2007 12:46:42 pm Tsugikazu Shibata wrote:
> > On Sat, 14 Jul 2007 22:12:35 -0400, rob wrote:
> > > On Friday 13 July 2007 9:46:59 pm Tsugikazu Shibata wrote:
> > > > > > How about adding;
> > > > > > kernel-doc-nano-HOWTO.txt
> > >
Hi;
18 Tem 2007 Çar tarihinde, Anthony Liguori şunları yazmıştı:
> Can you reproduce without the appArmor patchset?
Tomorrow i'll also try with vanilla one but just for records same patchset
worked without a problem until latest kvm merge :)
Cheers
--
S.Çağlar Onur <[EMAIL PROTECTED]>
S.Çağlar Onur wrote:
Hi;
17 Tem 2007 Sal tarihinde, Avi Kivity şunları yazmıştı:
I fixed the issue with the previous patchset. Please provide further
feedback, or pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
This contains kvm updates for the 2.6.23
On 17/07/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
At some point in the past, I wrote:
>> If at some point one of the pro-4k stacks crowd can prove that all
>> code paths are safe, or introduce another viable alternative (such as
>> Matt's idea for extending the stack dynamically),
James Bottomley wrote:
@@ -1052,9 +1054,10 @@ int generic_ide_ioctl(ide_drive_t *drive, struct file
*file, struct block_device
int err, (*setfunc)(ide_drive_t *, int);
u8 *val;
- err = scsi_cmd_ioctl(file, bdev->bd_disk->queue, bdev->bd_disk, cmd, p);
- if (err !=
> 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
another angle is that while correctness rules, userspace correctness
rules as well. If you can't fork enough threads for what you need the
machine
O> In that case, we might as well just always do the scheduled_delayed_work()
> with a zero timeout as per the earlier patch. I'd still like to know who
> *cares*, though? Why not leave it at 1?
I don't think it really matters too much on modern systems so long as we
keep the flush_to_ldisc out
Andrew Morton ha scritto:
> Seems harmless enough ;)
>
> Could you please send in a suitable update to Documentation/sysrq.txt?
sorry, I should have written a few lines here...
issue solved (sorry for not CCing here, I'm shy ((: ) resulting in no
need for a patch, just the need of a recent
1 - 100 of 1345 matches
Mail list logo
