The __MANDATORY_LOCK(inode) macro makes the same check, but
makes the code more readable.
Signed-off-by: Pavel Emelyanov <[EMAIL PROTECTED]>
Cc: Steven Whitehouse <[EMAIL PROTECTED]>
---
fs/gfs2/ops_file.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, Sep 11, 2007 at 12:01:10PM +0200, Bernhard Walle wrote:
> * Vivek Goyal <[EMAIL PROTECTED]> [2007-09-11 08:15]:
> >
> > "offset" seems to be optional in the new syntax. What happens if user does
> > not specify offset. I think crash_base will be set to zero and system will
> > try to
The combination of S_ISGID bit set and S_IXGRP bit unset is
used to mark the inode as "mandatory lockable" and there's a
macro for this check called MANDATORY_LOCK(inode). However,
fs/locks.c and some filesystems still perform the explicit
i_mode checking.
Switch the fs/locks.c to macro
Code used for DEBUG_SHIRQ in free_irq() is unreachable -- the for() loop
within never terminates otherwise than by return. This is an obvious fix.
Signed-off-by: Maciej W. Rozycki <[EMAIL PROTECTED]>
---
Please apply.
While at it, I have a question about the complementary code within
In message <[EMAIL PROTECTED]> you wrote:
> On Wed, 12 Sep 2007 12:20:32 +0200 Heiko Carstens <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Sep 12, 2007 at 12:04:39PM +1000, Michael Neuling wrote:
> > > The "tty: termios locking functions break with new termios type" patch
> > >
Hello Greg
Am Mittwoch, den 12.09.2007, 03:01 -0700 schrieb Greg KH:
> On Wed, Sep 12, 2007 at 07:32:07AM +0200, Robert Schwebel wrote:
> > On Tue, Sep 11, 2007 at 11:43:17AM +0200, Heiko Schocher wrote:
> > > I have developed a device driver and use the sysFS to export some
> > > registers to
Kees Cook wrote:
This patch against 2.6.23-rc6 fixes a couple drivers that do not
correctly terminate their pci_device_id lists. This results in garbage
being spewed into modules.pcimap when the module happens to not have
28 NULL bytes following the table, and/or the last PCI ID is actually
On Wednesday 12 September 2007, Michael Ellerman wrote:
> Because the SPU coredump code might be built as part of a module (spufs),
> we have a stub which is called by the coredump code, this routine then calls
> into spufs if it's loaded.
>
> Unfortunately the stub returns -ENOSYS if spufs is
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Make hibernation_platform_enter() execute the enter-a-sleep-state sequence
instead of the mixed shutdown-with-entering-S4 thing.
Replace the shutting down of devices done by kernel_shutdown_prepare(), before
entering the ACPI S4 sleep state, with
On Wed, 12 Sep 2007 12:20:32 +0200 Heiko Carstens <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 12, 2007 at 12:04:39PM +1000, Michael Neuling wrote:
> > The "tty: termios locking functions break with new termios type" patch
> > (f629307c857c030d5a3dd777fee37c8bb395e171) breaks the powerpc compile.
> >
On Wednesday 12 September 2007 12:17:45 Paul Mundt wrote:
> On Wed, Sep 12, 2007 at 12:09:09PM +0200, Michael Buesch wrote:
> > On Wednesday 12 September 2007 04:11:00 Paul Mundt wrote:
> > > SSB uses a bool (SSB_PCMCIAHOST_POSSIBLE) to determine whether to
> > > build in PCMCIA support or not, as
On Tue, 11 Sep 2007 09:56:05 -0500
Emil Medve <[EMAIL PROTECTED]> wrote:
> Other pr_*() macros are already defined in kernel.h, but pr_err() was defined
> multiple times in several other places
>
> Signed-off-by: Emil Medve <[EMAIL PROTECTED]>
pr_error seems better than pr_err
Please add the
Arne Georg Gleditsch <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > + case RTC_SPEED_UP:
> > + err = rtc_speed_up(rtc);
> > + break;
> > +
> > + case RTC_SLOW_DOWN:
> > + err = rtc_speed_up(rtc);
> > + break;
> This
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
The following scenario leads to total confusion of the platform firmware on
some boxes (eg. HPC nx6325):
* Hibernate with ACPI enabled
* Resume passing "acpi=off" to the boot kernel
To prevent this from happening it's necessary to check if ACPI is
On Wed, 2007-09-05 at 05:14 -0700, Christoph Lameter wrote:
> Using the VM to throttle networking is a pretty bad thing because it
> assumes single critical user of memory. There are other consumers of
> memory and if you have a load that depends on other things than networking
> then you
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> + case RTC_SPEED_UP:
> + err = rtc_speed_up(rtc);
> + break;
> +
> + case RTC_SLOW_DOWN:
> + err = rtc_speed_up(rtc);
> + break;
This doesn't look quite right. rtc_slow_down, surely?
--
[EMAIL PROTECTED] wrote:
> But if you really want to read or try it, you can get all source files
> from sourceforge. Read http://aufs.sf.net and try,
> $ cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aufs login
> (CVS password is empty)
> $ cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/aufs co
> aufs
On Wed, Jun 20, 2007 at 12:38:48PM -0400, Hank Leininger wrote:
> On Wed, 20 Jun 2007, H. Peter Anvin wrote:
> >Bj�rn Steinbrink wrote:
> >>
> >>marc.info supports that.
> >>http://marc.info/[EMAIL PROTECTED]
> >Excellent! Didn't see that documented anywhere.
>
> You're right, it's not really.
On Wed, Sep 12, 2007 at 12:04:39PM +1000, Michael Neuling wrote:
> The "tty: termios locking functions break with new termios type" patch
> (f629307c857c030d5a3dd777fee37c8bb395e171) breaks the powerpc compile.
> [...]
> I'm guessing other architectures are broken too?
FWIW, the above quoted
On Wed, Sep 12, 2007 at 12:09:09PM +0200, Michael Buesch wrote:
> On Wednesday 12 September 2007 04:11:00 Paul Mundt wrote:
> > SSB uses a bool (SSB_PCMCIAHOST_POSSIBLE) to determine whether to
> > build in PCMCIA support or not, as the PCMCIA host code itself is
> > also only a bool, make
On Wednesday 12 September 2007 04:11:00 Paul Mundt wrote:
> SSB uses a bool (SSB_PCMCIAHOST_POSSIBLE) to determine whether to
> build in PCMCIA support or not, as the PCMCIA host code itself is
> also only a bool, make SSB_PCMCIAHOST_POSSIBLE depend on PCMCIA=y.
>
> Without this,
Paul Menage wrote:
> Hi Balbir/Pavel,
>
> As I mentioned to you directly at the kernel summit, I think it might
> be cleaner to integrate resource counters more closely with control
> groups. So rather than controllers such as the memory controller
> having to create their own boilerplate cf_type
On Wed, Sep 12, 2007 at 07:32:07AM +0200, Robert Schwebel wrote:
> On Tue, Sep 11, 2007 at 11:43:17AM +0200, Heiko Schocher wrote:
> > I have developed a device driver and use the sysFS to export some
> > registers to userspace.
>
> Uuuh, uggly. Don't do that. Device drivers are there to abstract
RDMA/CMA: Use neigh_event_send() to initiate neighbour discovery.
Calling arp_send() to initiate neighbour discovery (ND) doesn't do the
full ND protocol. Namely, it doesn't handle retransmitting the arp
request if it is dropped. The function neigh_event_send() does all this.
Without doing full
Hi,
randconfig [1] causes this link errors:
ERROR: "netpoll_cleanup" [drivers/net/kgdboe.ko] undefined!
ERROR: "netpoll_setup" [drivers/net/kgdboe.ko] undefined!
ERROR: "netpoll_parse_options" [drivers/net/kgdboe.ko] undefined!
ERROR: "netpoll_poll" [drivers/net/kgdboe.ko] undefined!
ERROR:
Hi,
I did a make randconfig and then make C=1.
hci_sock.c fails to build because it doesnt know compat_timeval (i
guess).
find the error message and the config attached.
regards,
Andre
LD net/ax25/ax25.o
LD net/ax25/built-in.o
CHECK net/bluetooth/af_bluetooth.c
CC
On Wed, Sep 12, 2007 at 11:06:10AM +0900, Paul Mundt wrote:
> There's nothing that is problematic for file_fsync() with CONFIG_BLOCK=n,
> and it's built in unconditionally anyways, so move the prototype out to
> reflect that. Without this, the unionfs build bails out.
Unionfs should stop using it
On Tue, Sep 11, 2007 at 10:34:13PM +0200, Adrian Bunk wrote:
> As an example, visws.c is as much non-64bit as it is pre-i686.
Bullshit. visws were shipped with P3s.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Tue, 11 Sep 2007 23:49:47 +0200 Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-09-11 at 21:52 +0200, Thomas Gleixner wrote:
> > > C1: type[C1] promotion[C2] demotion[--] latency[001]
> > > usage[0010] duration[]
> > >*C2:
On Tue, 11 Sep 2007 21:52:01 +0200 Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-09-11 at 11:44 -0700, Andrew Morton wrote:
> > > > there doesn't seem to be a lot of difference in the time handling,
> > > > except
> > > > there are large changes in when things happen in the bootup
Hi;
Commit 66eb50d5c972cc16df2be730497b7f06d75d8132 introduces runtime check of
CONFIG_COMPAT but without following patch compiliation failed with following
error;
...
CC [M] net/bluetooth/hci_event.o
CC [M] net/bluetooth/hci_sock.o
net/bluetooth/hci_sock.c: In function `hci_sock_cmsg':
On Tue, 2007-09-11 at 22:31 -0400, John Stoffel wrote:
I hope the snipped questions were sufficiently answered in the other
mail. If not, holler :-)
> Peter> 3 is done by also scaling the dirty limit proportional to the
> Peter> current task's recent dirty rate.
>
> Do you mean task or device
On Wednesday 12 September 2007, Michael Ellerman wrote:
> The spufs_coredump_read array is NULL terminated, and we also store the size.
> We only need one or the other, and storing the size should save a teensy bit
> of memory vs NULL terminating, so do that.
Given that we have another array in
On Wednesday 12 September 2007, Michael Ellerman wrote:
> The SPUFS attribute get routines take a void * because the generic attribute
> code doesn't know what sort of data it's passing around.
>
> However our internal __spufs_get_foo() routines can take a spu_context *
> directly, which saves
On Wednesday 12 September 2007, Michael Ellerman wrote:
> Because spufs might be built as a module, we can't have other parts of the
> kernel calling directly into it, we need stub routines that check first if the
> module is loaded.
>
> Currently we have two structures which hold callbacks for
On Wednesday 12 September 2007, Michael Ellerman wrote:
> Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Acked-by: Arnd Bergmann <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi.
Stephen Smalley pointed out possibility of race condition
in off-list discussion.
Stephen Smalley said:
> One other observation about the patch: it presently leaves open a
> (small) race window in which the file could get relabeled or policy gets
> reloaded between the time of the normal
On Wednesday 12 September 2007, Michael Ellerman wrote:
> On Wed, 2007-09-12 at 17:43 +1000, Michael Ellerman wrote:
> > This patch adds DEFINE_SPUFS_ATTRIBUTE(), a wraper around
> > DEFINE_SIMPLE_ATTRIBUTE which does the specified locking for the get
> > routine for us.
> >
> > Unfortunately we
On Tue, 2007-09-11 at 22:36 -0400, John Stoffel wrote:
> Peter> Scale writeback cache per backing device, proportional to its
> Peter> writeout speed. By decoupling the BDI dirty thresholds a
> Peter> number of problems we currently have will go away, namely:
>
> Ah, this clarifies my questions!
On Wed, 12 Sep 2007 18:17:42 +1000 Jeremy Kerr <[EMAIL PROTECTED]> wrote:
> This series looks good to me, thanks for the fixes. I'll do some testing
> tomorrow but it looks like it'll be fine as-is.
>
> Andrew - almost all of these are for spufs, the notable exception being:
>
> [PATCH 12/15]
On (12/09/07 16:51), KAMEZAWA Hiroyuki didst pronounce:
> On Tue, 11 Sep 2007 22:31:27 +0100 (IST)
> Mel Gorman <[EMAIL PROTECTED]> wrote:
>
> > Using two zonelists per node requires very frequent use of zone_idx(). This
> > is costly as it involves a lookup of another structure and a
Andrew Morton napsal(a):
> On Fri, 17 Aug 2007 00:08:58 +0200 Jesper Juhl <[EMAIL PROTECTED]> wrote:
>
>> Fix this tiny compiler warning in Moxa driver :
>> drivers/char/mxser.c:386: warning: 'mxser_get_PCI_conf' declared 'static'
>> but never defined
>> when building without CONFIG_PCI.
>>
On Tue, Sep 11, 2007 at 05:04:41PM -0700, Christoph Lameter wrote:
> I would think that your approach would be slower since you always have to
> populate 1 << N ptes when mmapping a file? Plus there is a lot of wastage
I don't have to populate them, I could just map one at time. The only
reason
Hi Michael,
This series looks good to me, thanks for the fixes. I'll do some testing
tomorrow but it looks like it'll be fine as-is.
Andrew - almost all of these are for spufs, the notable exception being:
[PATCH 12/15] Cleanup ELF coredump extra notes logic
which touches the generic
From: "Kövedi_Krisztián" <[EMAIL PROTECTED]>
Date: Wed, 12 Sep 2007 09:47:45 +0200
> The patch work fine the kernel booting up without error messages.
Thanks for testing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Wed, 2007-09-12 at 17:43 +1000, Michael Ellerman wrote:
> This patch adds DEFINE_SPUFS_ATTRIBUTE(), a wraper around
> DEFINE_SIMPLE_ATTRIBUTE which does the specified locking for the get
> routine for us.
>
> Unfortunately we need two get routines (a locked and unlocked version) to
> support
while killing some time between compiles and ridding the
kernel-parameters.txt file of out-of-date or incorrect cruft, it
occurs to me that that file is borderline valueless since it
apparently tries to document every possible boot-time parameter,
including those associated with individual
A working system begins hanging and it seems to be stuck on I/O
processes that use ext3 partitions that are running on top of LVM.
The system is AMD 64-bit running Gentoo. Kernel is Gentoo 2.6.22-r3
and LVM lvm2-2.02.27. Here is the disk setup:
Boot disk, attached to motherboard via SATA
1)
2007/9/11, David Miller <[EMAIL PROTECTED]>:
>
> I think this patch should fix the problem.
>
> Please give it a try, thanks.
>
> diff --git a/arch/sparc64/kernel/pci.c b/arch/sparc64/kernel/pci.c
> index 139b4cf..e8dac81 100644
> --- a/arch/sparc64/kernel/pci.c
> +++ b/arch/sparc64/kernel/pci.c
>
On Tue, 11 Sep 2007 22:31:27 +0100 (IST)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> Using two zonelists per node requires very frequent use of zone_idx(). This
> is costly as it involves a lookup of another structure and a substraction
> operation. As struct zone is always word aligned and normally
Currently the spu coredump code doesn't respect the ulimit, it should.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/coredump.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spufs/coredump.c
This patch adds DEFINE_SPUFS_ATTRIBUTE(), a wraper around
DEFINE_SIMPLE_ATTRIBUTE which does the specified locking for the get
routine for us.
Unfortunately we need two get routines (a locked and unlocked version) to
support the coredump code. This patch hides one of those (the locked version)
To start with, arch_notes_size() etc. is a little too ambiguous a name for
my liking, so change the function names to be more explicit.
Calling through macros is ugly, especially with hidden parameters, so don't
do that, call the routines directly.
Use ARCH_HAVE_EXTRA_ELF_NOTES as the only flag,
Rework spufs_coredump_extra_notes_write() to check for and return errors.
If we're coredumping to a pipe we can't trust file->f_pos, we need to
maintain the foffset value passed to us. The cleanest way to do this is
to have the low level write routine increment foffset when we've
successfully
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/file.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spufs/file.c
b/arch/powerpc/platforms/cell/spufs/file.c
index d19220f..52f020a 100644
---
Because spufs might be built as a module, we can't have other parts of the
kernel calling directly into it, we need stub routines that check first if the
module is loaded.
Currently we have two structures which hold callbacks for these stubs, the
syscalls are in spufs_calls and the coredump calls
The spufs_coredump_read array is NULL terminated, and we also store the size.
We only need one or the other, and storing the size should save a teensy bit
of memory vs NULL terminating, so do that.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
The SPUFS attribute get routines take a void * because the generic attribute
code doesn't know what sort of data it's passing around.
However our internal __spufs_get_foo() routines can take a spu_context *
directly, which saves plonking it in and out of a void * again.
Signed-off-by: Michael
The routine to dump the local store, __spufs_mem_read(), does not take the
spu_lslr_RW value into account - so we shouldn't check it when we're
calculating the size either.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/coredump.c | 16
Because the SPU coredump code might be built as part of a module (spufs),
we have a stub which is called by the coredump code, this routine then calls
into spufs if it's loaded.
Unfortunately the stub returns -ENOSYS if spufs is not loaded, which is
interpreted by the coredump code as an extra
Unfortunately GDB expects some of the SPU coredump values to be identical
in format to what is found in spufs. This means we need to dump some of
the values as ASCII strings, not the actual values.
Because we don't know what the values will be, we always print the values
with the format
The spufs_coredump_reader array contains the size of the data that will be
returned by the read routine. Currently these are specified as literals, and
though some are obvious, sizeof(u32) == 4, others are not, 69 * 8 == ???
Instead, use sizeof() whatever type is returned by each routine, or in
Extract the logic for searching through the file descriptors for spu contexts
into a separate routine, coredump_next_context(), so we can use it elsewhere
in future. In the process we flatten the for loop, and move the NOSCHED test
into coredump_next_context().
Signed-off-by: Michael Ellerman
Remove the ctx_info struct entirely, and also the ctx_info_list. This fixes
a race where two processes can clobber each other's ctx_info structs.
Instead of using the list, we just repeat the search through the file
descriptor table.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
It makes sense to stop the SPU processes as soon as possible. Also if we
dont acquire_saved() I think there's a possibility that the value in
csa.priv2.spu_lslr_RW won't be accurate.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/coredump.c |2 ++
1
From: Nathanael Nerode
Stop building and configuring driver for Digi RightSwitch, which was
never actually sold to anyone, and remove it from MAINTAINERS.
In response to an investigation into the firmware of the "Digi Rightswitch"
driver, Andres Salomon discovered:
>
> Dear Andres:
>
> After
Hi Adrian, Maneesh,
Maneesh Soni wrote:
> On Mon, Sep 10, 2007 at 02:20:40PM +0200, Adrian Bunk wrote:
>> On Mon, Sep 10, 2007 at 11:55:49AM +0900, Ken'ichi Ohmichi wrote:
>>> Hi Adrian,
>>>
>>>
>>> 2007/09/09 22:25:16 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote:
On Fri, Aug 31, 2007 at
This patch against 2.6.23-rc6 fixes a couple drivers that do not
correctly terminate their pci_device_id lists. This results in garbage
being spewed into modules.pcimap when the module happens to not have
28 NULL bytes following the table, and/or the last PCI ID is actually
truncated from the
Hi!
Michal Piotrowski:
> On 06/09/07, Daniel Exner <[EMAIL PROTECTED]> wrote:
> > I'm not really sure if this is a regression or if I simply hit a hardware
> > problem.
> > After some time of work (mostly hours sometimes minutes) my system will
> > freeze including Blinking LED's and
On Wednesday 12 September 2007 11:49, David Chinner wrote:
> On Tue, Sep 11, 2007 at 04:00:17PM +1000, Nick Piggin wrote:
> > > > OTOH, I'm not sure how much buy-in there was from the filesystems
> > > > guys. Particularly Christoph H and XFS (which is strange because they
> > > > already do
On 11 Sep 2007 at 17:04, Al Viro wrote:
> On Tue, Sep 11, 2007 at 05:54:38PM +0200, Ulrich Windl wrote:
>
> > If not, any clues on debugging/tracing? There's a
> > /usr/src/linux/Documentation/oops-tracing.txt, but no "segfault-tracing".
>
> That would be because it has fsck-all to do with the
On Tue, 2007-09-11 at 22:04 +0200, Ingo Molnar wrote:
> fresh back from the Kernel Summit, Peter Zijlstra and me are pleased to
> announce the latest iteration of the CFS scheduler development tree. Our
> main focus has been on simplifications and performance - and as part of
> that we've also
On Tue, 2007-09-11 at 20:23 -0700, Andrew Morton wrote:
> On Fri, 17 Aug 2007 13:28:38 +0800 "Huang, Ying" <[EMAIL PROTECTED]> wrote:
>
> > This patch fixes a bug of change_page_attr/change_page_attr_addr on
> > Intel x86_64 CPU. After changing page attribute to be executable with
> > these
On Mon, 10 Sep 2007 23:35:02 -0700
Greg KH <[EMAIL PROTECTED]> wrote:
>
> > Sep 9 13:49:01 prizm kernel: [ 584.407498] drivers/usb/core/inode.c:
> > creating file '003'
> > Sep 9 13:49:01 prizm kernel: [ 584.407509] hub 5-0:1.0: state 7 ports 8
> > chg evt 0004
> > Sep 9 13:49:01
Coly Li 写道:
David Miller 写道:
From: Greg KH [EMAIL PROTECTED]
Date: Wed, 12 Sep 2007 05:02:53 -0700
It's not even a randconfig issue, my build dies too (this is Linus's
current tree.)
Time to poke through the 10 bluetooth patches that were just added...
I'll push the following fix to
Christoph Lameter wrote:
On Tue, 11 Sep 2007, Nick Piggin wrote:
But that's not my place to say, and I'm actually not arguing that high
order pagecache does not have uses (especially as a practical,
shorter-term solution which is unintrusive to filesystems).
So no, I don't think I'm really
The idea is not to hide the unlikely, but to leave the opportunity to
make this primitive evolve in something that won't depend on a load
immediate and only require patching of a jump, given the appropriate gcc
support (yet to come).
If that ever happens the code can be still changed. But i
On 9/12/07, Andy Whitcroft [EMAIL PROTECTED] wrote:
The following commit just hit mainline and all my powerpc test boxes are
failing during compilation:
commit f629307c857c030d5a3dd777fee37c8bb395e171
tty: termios locking functions break with new termios type
I think this is
From: Herbert Xu [EMAIL PROTECTED]
Date: Tue, 11 Sep 2007 20:43:27 +0800
On Tue, Sep 11, 2007 at 08:01:46AM -0400, jamal wrote:
[NET_SCHED] protect action config/dump from irqs
Looks good! Thanks Jamal.
Applied, I'll try to push this in some time soon.
-
To unsubscribe from this list:
Robert P. J. Day wrote:
p.s. by basic, i mean those boot-time parms defined by either
__setup() or early_param(). which means that module writers
should, as much as possible, stop using those macros to define
command-line parameters for their modules. that would go a long way
to restoring
On Tuesday 11 September 2007 16:51, Nathan Lynch wrote:
- get_paca()-paca_index, __FUNCTION__, \
+ smp_processor_id(), __FUNCTION__, \
I think I see these macros used in preemptible code (e.g. ehca_probe),
where smp_processor_id()
We can use raw_smp_processor_id() here because the processor ID is only used
for debug output and may therefore be preemption-unsafe.
Signed-off-by: Joachim Fenkes [EMAIL PROTECTED]
---
This is the same patch, but with smp_processor_id() replaced by
raw_smp_processor_id(), as kindly pointed out
On Wed, 12 Sep 2007, Rogan Dawes wrote:
Robert P. J. Day wrote:
p.s. by basic, i mean those boot-time parms defined by either
__setup() or early_param(). which means that module writers
should, as much as possible, stop using those macros to define
command-line parameters for their
From: Divy Le Ray [EMAIL PROTECTED]
Date: Sun, 09 Sep 2007 00:09:17 -0700
From: Divy Le Ray [EMAIL PROTECTED]
Embed napi_struct directly into sge_qset.
Use napi_schedule/napi_complete.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
Patch applied, thanks a lot!
-
To unsubscribe from this
Am Mittwoch, 12. September 2007 15:37 schrieb J. Bruce Fields:
On Wed, Sep 12, 2007 at 02:07:10PM +0200, Wolfgang Walter wrote:
as already described old temporary sockets (client is gone) of lockd
aren't closed after some time. So, with enough clients and some time
gone, there are 80 open
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Thu, 06 Sep 2007 16:07:35 -0400 Mathieu Desnoyers wrote:
[snip]
This patch:
Add Kconfig menus for the marker code.
[EMAIL PROTECTED]: Never ever select MODULES]
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Reviewed-by:
This version brings a number of new checks, and a number of bug
fixes. Of note:
- better categorisation and space checks for dual use unary/binary
operators
- warn on deprecated use of {SPIN,RW}_LOCK_UNLOCKED
- check if/for/while with trailing ';' for hanging statements
- detect DOS
Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
on all architectures. However, powerpc, s390, avr32 and frv don't
currently define those functions since their termios struct didn't
need to be changed when the
Robin Holt writes:
I have been experiencing hangs on a newly setup machine. Unfortunately,
it appears to be hanging inside the interrupt handler as sysrq and
caps-lock led seem to stop working when the event occurs. I am guessing
it is related to the sata_promise driver, but that is
I just narrowed down a weird problem where I was losing more than 50% of
my vblank interrupts to what seems to be the hires timers patch. Stock
2.6.23-rc5 works fine, but the latest (171) kernel from rawhide drops
most of my interrupts unless I also have another interrupt source
running (e.g.
On Wed, Sep 12, 2007 at 11:09:47AM -0400, Lee Schermerhorn wrote:
Interesting, I don't see a memory controller function in the stack
trace, but I'll double check to see if I can find some silly race
condition in there.
right. I noticed that after I sent the mail.
Also, config
On Wed, Sep 12, 2007 at 08:02:29AM -0700, Randy Dunlap wrote:
Adrian Bunk wrote:
On Wed, Sep 12, 2007 at 01:24:13PM +0800, WANG Cong wrote:
On Tue, Sep 11, 2007 at 08:29:26PM +0200, Adrian Bunk wrote:
On Tue, Sep 11, 2007 at 10:16:44AM -0700, Randy Dunlap wrote:
...
On Thursday 23 August 2007 01:28, Satyam Sharma wrote:
* Replace {un}register_cpu_notifier with {un}register_hotcpu_notifier
thereby losing a couple of #ifdef HOTPLUG_CPU pairs.
* Move comp_pool_callback_nb declaration to below that of callback
function so that initialization of
Hi Chris,
On 11/09/2007, Chris Friesen [EMAIL PROTECTED] wrote:
Hi all,
We're running a modified 2.6.10 on a dual-Xeon system. We've had a
number of instances where we've seen oopses in the pipe code. I've
included the most recent one below. This bug left us with a hung
process as the
I'm still seeing the warnings below (2.6.22 started off with lots of
section mismatch warning) but I have no idea if it is safe to ignore
these:
WARNING: arch/i386/kernel/built-in.o(.text+0xea62): Section mismatch: reference
to .init.data:trampoline_end (between 'setup_trampoline' and
Hi Dave,
It's not even a randconfig issue, my build dies too (this is Linus's
current tree.)
Time to poke through the 10 bluetooth patches that were just added...
I'll push the following fix to Linus.
the patch looks absolutely fine to me. You can put an Acked-by line to
it. Sorry
I sent this to kernel newbies first, and while I got one response there,
it answered a different question than the one I was asking...
I'm on a SuSE system.
I'm working on automating the install of said system, but it needs a
Linus kernel - 2.6.21.7 specifically, and it needs kernel source too
Since -rc6:
- i386/allmodconfig: broke
CC [M] net/bluetooth/hci_core.o
CC [M] net/bluetooth/hci_conn.o
CC [M] net/bluetooth/hci_event.o
CC [M] net/bluetooth/hci_sock.o
net/bluetooth/hci_sock.c: In function 'hci_sock_cmsg':
net/bluetooth/hci_sock.c:352: error: storage size
On Wednesday, September 12, 2007, Randy Dunlap wrote:
On Wed, 12 Sep 2007 08:33:15 -0700 Jesse Barnes wrote:
I just narrowed down a weird problem where I was losing more than
50% of my vblank interrupts to what seems to be the hires timers
patch. Stock 2.6.23-rc5 works fine, but the latest
Platform i386 seems to be missing struct compat_timeval, which causes
the i386 allmodconfig build to break in current -git:
net/bluetooth/hci_sock.c: In function ‘hci_sock_cmsg’:
net/bluetooth/hci_sock.c:352: error: storage size of ‘ctv’ isn’t known
net/bluetooth/hci_sock.c:352: warning: unused
301 - 400 of 740 matches
Mail list logo
