From: Adrian Bunk <[EMAIL PROTECTED]>
Date: Sat, 27 Oct 2007 04:34:48 +0200
> This patch fixes the following compile errors in some configurations:
>
> <-- snip -->
>
> ...
> CC net/ipv4/esp4.o
> /home/bunk/linux/kernel-2.6/git/linux-2.6/net/ipv4/esp4.c: In function
> 'esp_output':
>
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri, 26 Oct 2007 23:42:40 -0400
>
> net/ipv6/tcp_ipv6.c: In function 'tcp_v6_rcv':
> net/ipv6/tcp_ipv6.c:1736: error: implicit declaration of function
> 'get_softnet_dma'
> net/ipv6/tcp_ipv6.c:1736: warning: assignment makes pointer from integer
>
On Wed, Oct 24, 2007 at 10:36:21 -0700, Paul Jackson wrote:
> From: Paul Jackson <[EMAIL PROTECTED]>
>
> Simplify the space stripping code in cgroup file write.
>
> Signed-off-by: Paul Jackson <[EMAIL PROTECTED]>
>
> ---
>
> This patch applies after both:
> Adrian Bunk's: [2.6 patch]
On Fri, 26 Oct 2007 12:21:55 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 26 Oct 2007 17:22:21 +0200
> Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> >
> > * Martin Knoblauch <[EMAIL PROTECTED]> wrote:
> >
> > > Hi ,
> > >
> > > just to give some feedback on 2.6.24-rc1. For some time
On Fri, 26 Oct 2007 20:37:47 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Arjan van de Ven wrote:
> > the other serious question is.. how is IRQ_HANDLER_V3 different
> > from a #ifdef VERSION >= 2.6.24 .
> > it's not really ;)
>
> Note my mention of backport -- kernel version isn't
Greetings,
For quite a while now, RT kernels have been locking up on me
occasionally while my back is turned. Yesterday, the little bugger
finally pounced while my serial console box was up and waiting.
[10138.162953] WARNING: at arch/i386/kernel/smp.c:581
native_smp_call_function_mask()
On Fri, Oct 26, 2007 at 10:40:12PM -0600, Eric W. Biederman wrote:
> Adrian Bunk <[EMAIL PROTECTED]> writes:
>
> > There isn't any hard semantics behind what is marked EXPERIMENTAL and
> > what not. In it's current state, we could even consider removing the
> > EXPERIMENTAL option and all
I'm still confused, Christoph.
Are you saying:
1) The kernel continues to default to Choice A, unless
the flag enables Choice B, or
2) The kernel defaults to the new Choice B, unless the
flag reverts to the old Choice A?
Alternative (2) breaks libnuma and hence numactl until it is
> You did it in your output directory I assume.
No.
> kbuild complains that the source directory is not clean - which
> is what you need to clean up.
I am looking for the real reasons for the occuring error messages. Let us look
at another
test example ...
Sonne:~ # ls -ld /usr/src/linux
On Sun, 21 Oct 2007 12:12:38 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
>
> After the bisecting, i found that the patch git-net.patch is the cause for
> the link failure.
The actual cause is my patch to mark some things in head_64.S as
init_refok. I have a test patch which I will tidy up
On Fri, 26 Oct 2007 21:46:59 -0600 [EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
> >> On Sat, 27 Oct 2007 04:04:08 +0200 Adrian Bunk <[EMAIL PROTECTED]> wrote:
> >> > be happy to hear if someone has a better idea.
> >>
> >> There is a difference
Adrian Bunk <[EMAIL PROTECTED]> writes:
> There isn't any hard semantics behind what is marked EXPERIMENTAL and
> what not. In it's current state, we could even consider removing the
> EXPERIMENTAL option and all dependencies on EXPERIMENTAL.
Well I do know at least some of the things that
On Fri, Oct 26, 2007 at 09:46:59PM -0600, Eric W. Biederman wrote:
>...
> It hurts me to even ponder what thinking makes it that
> CONFIG_EXPERIMENTAL isn't enough to keep a stable distro
> from shipping the code in their stable kernel, and locking us into
> trouble.
>...
There isn't any hard
On Fri, 26 Oct 2007 15:51:44 +0900 Keiichi KII wrote:
> From: Keiichi Kii <[EMAIL PROTECTED]>
>
> Fix typo.
>
> Signed-off-by: Keiichi Kii <[EMAIL PROTECTED]>
> Cc: Andy Whitcroft <[EMAIL PROTECTED]>
> ---
> Index: trunk/Documentation/SubmittingPatches
>
Andrew Morton <[EMAIL PROTECTED]> writes:
>> On Sat, 27 Oct 2007 04:04:08 +0200 Adrian Bunk <[EMAIL PROTECTED]> wrote:
>> > be happy to hear if someone has a better idea.
>>
>> There is a difference between "complete the feature" and "early adopters
>> to start playing with the feature" on the
net/ipv6/tcp_ipv6.c: In function 'tcp_v6_rcv':
net/ipv6/tcp_ipv6.c:1736: error: implicit declaration of function
'get_softnet_dma'
net/ipv6/tcp_ipv6.c:1736: warning: assignment makes pointer from integer
without a cast
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
---
diff --git
On Thu, Oct 25, 2007 at 05:04:40PM +0530, Balbir Singh wrote:
>
>
> Fix the compilation error
>
> arch/um/kernel/sysrq.c: In function 'show_stack':
> arch/um/kernel/sysrq.c:63: error: 'UESP' undeclared (first use in this
> function)
> arch/um/kernel/sysrq.c:63: error: (Each undeclared
On Thu, Oct 25, 2007 at 05:06:30PM +0530, Balbir Singh wrote:
>
>
> Fix stat.h to not use __i386__, but use BITS_PER_LONG. The UML architecture
> in turn includes this file. This helps resolve one build failure in the
> current UML code
NACK
-
To unsubscribe from this list: send the line
We are pleased to announce the 2.6.23.1-rt4 tree, which can be
downloaded from the location:
http://www.kernel.org/pub/linux/kernel/projects/rt/
Changes since 2.6.23-rt3
- Updated to stable release 2.6.23.1
- Added latest High Resolution timers work
- RT Balance CPU weight optimization
On Thu, Oct 25, 2007 at 09:01:52PM +0530, Balbir Singh wrote:
> Thats nice, I wonder why I missed them searching on lkml in my gmail box
> :(
>
> Is __arch_um__ the right thing to do or BITS_PER_LONG == 32? I prefer
> BITS_PER_LONG == 32 over #if defined(__i386__) || defined(__arch__um__).
> I
Fix an incompatible-pointer warning.
Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
---
arch/um/drivers/ubd_kern.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
index e184b44..7e6cdde 100644
---
From: Rob Landley <[EMAIL PROTECTED]>
Update kerneldoc comments in drivers/scsi/scsicam.c
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
---
drivers/scsi/scsicam.c | 39 ++-
1 file changed, 26 insertions(+), 13 deletions(-)
diff -r a868e8217782
On Fri, Oct 26, 2007 at 09:59:45AM -0700, Jesse Barnes wrote:
> On Thursday, October 25, 2007 7:54 pm Greg KH wrote:
> > On Thu, Oct 25, 2007 at 04:22:35PM -0700, Jesse Barnes wrote:
> > > I think Greg doesn't like it, even though we don't have an
> > > alternative at this point...
> >
> > Yes, I
On Fri, 26 Oct 2007, Paul Jackson wrote:
> Christoph wrote:
> > Yes. We should default to Choice B. Add an option MPOL_MF_RELATIVE to
> > enable that functionality? A new version of numactl can then enable
> > that by default for newer applications.
>
> I'm confused. If B is the default, then
Christoph wrote:
> Yes. We should default to Choice B. Add an option MPOL_MF_RELATIVE to
> enable that functionality? A new version of numactl can then enable
> that by default for newer applications.
I'm confused. If B is the default, then we don't need a flag to
enable it, rather we need a
On Sat, Oct 27, 2007 at 03:18:08AM +0200, Peter Zijlstra wrote:
>
> On Fri, 2007-10-26 at 22:04 +0200, Peter Zijlstra wrote:
> > This crashes and burns on bootup, but I'm too tired to figure out what I
> > did wrong... will give it another try tomorrow..
>
> Ok, can't sleep.. took a look. I have
This patch fixes the following compile errors in some configurations:
<-- snip -->
...
CC net/ipv4/esp4.o
/home/bunk/linux/kernel-2.6/git/linux-2.6/net/ipv4/esp4.c: In function
'esp_output':
/home/bunk/linux/kernel-2.6/git/linux-2.6/net/ipv4/esp4.c:113: error: implicit
declaration of
On Fri, Oct 26, 2007 at 08:07:44PM +0200, Kay Sievers wrote:
> On Fri, 2007-10-26 at 12:05 -0500, Larry Finger wrote:
> > On my openSUSE 10.3 x86_64 system running v2.6.24-rc1-281-g22d2aa1,
> > I get the sysfs rename messages.
>
> Care to try this? Seems like a silly bug in the core if
>
> On Sat, 27 Oct 2007 04:04:08 +0200 Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > be happy to hear if someone has a better idea.
>
> There is a difference between "complete the feature" and "early adopters
> to start playing with the feature" on the one side, and making something
> available in a
On Fri, Oct 26, 2007 at 07:31:04PM -0600, Eric W. Biederman wrote:
> Adrian Bunk <[EMAIL PROTECTED]> writes:
>
> > CONFIG_EXPERIMENTAL is a weak hint that some code might not (yet) be in
> > a perfect state, but it does not have any semantics regarding
> > userspace ABIs.
>
> Code that might
Adrian Bunk <[EMAIL PROTECTED]> writes:
> CONFIG_EXPERIMENTAL is a weak hint that some code might not (yet) be in
> a perfect state, but it does not have any semantics regarding
> userspace ABIs.
Code that might not (yet) be in a perfect state sums it up pretty
well. There is not plan or
On Fri, 26 Oct 2007 12:30:28 -0500 James Bottomley wrote:
> There was a missed conversion in the voyager architecture setup file
> which this corrects.
>
> Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
Oh.
http://lkml.org/lkml/2007/10/22/180
even cc-ed to you.
> ---
>
> James
>
> diff
On Fri, 26 Oct 2007, Paul Jackson wrote:
> Choice B lets the task calculate its mempolicy mask as if it owned
> the entire system, and express whatever elaborate mempolicy placement
> it might need, when blessed with enough memory nodes to matter.
> The system would automatically scrunch that
On Fri, 2007-10-26 at 22:04 +0200, Peter Zijlstra wrote:
> This crashes and burns on bootup, but I'm too tired to figure out what I
> did wrong... will give it another try tomorrow..
Ok, can't sleep.. took a look. I have several problems here.
The thing that makes it go *boom* is the
Hiroshi Shimamoto wrote:
> Thomas Gleixner wrote:
>> On Fri, 26 Oct 2007, Hiroshi Shimamoto wrote:
>>
>> Added Venki to CC
>>
I'm now testing crash on 32bit, but there is an issue before
applying the patches. My machine stopped at checking 'hlt'
after kexec, showing below message.
Issue:
Are the nodes and nodemasks passed into set_mempolicy() to be
presumed relative to the cpuset or not? [Careful, this question
doesn't mean what you might think it means.]
Let's say our system has 100 nodes, numbered 0-99, and we have a task
in a cpuset that includes the
Stuff that is unconditional in both compiler-gcc3.h and compiler-gcc4.h
belongs into compiler-gcc.h.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
include/linux/compiler-gcc.h |8
include/linux/compiler-gcc3.h |8
include/linux/compiler-gcc4.h |7 ---
3
This patch fixes a bug introduced by
commit b22817b3c81cdb18ffe3d2debfee968731a8b5f4.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
155ad66379582067ef2ce73d28e3cf6eedf21b14
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index 177e78e..49a91c5 100644
---
Arjan van de Ven wrote:
the other serious question is.. how is IRQ_HANDLER_V3 different from a
#ifdef VERSION >= 2.6.24 .
it's not really ;)
Note my mention of backport -- kernel version isn't relevant when the
various enterprise distros have random featuresets under random kernel
On Sat, Oct 27, 2007 at 12:39:41AM +0400, Alexey Dobriyan wrote:
> > > - if ((task->state != TASK_STOPPED) && (task->state !=
> > > TASK_TRACED)) {
> > > + if (!is_task_stopped_or_traced(task)) {
> ^^
>
> I think this is horrible. Are
On Fri, Oct 26, 2007 at 03:59:29PM -0600, Eric W. Biederman wrote:
> "Kir Kolyshkin" <[EMAIL PROTECTED]> writes:
>
> > Eric,
> >
> > Could you please hold off the horses a bit and wait till Pavel Emelyanov
> > returns? It means next Monday; he's currently at a conference whose
> > organisers
> >
On Fri, 26 Oct 2007 20:12:40 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Arjan van de Ven wrote:
> > On Fri, 26 Oct 2007 17:47:58 -0400
> > Jeff Garzik <[EMAIL PROTECTED]> wrote:
> >
> >> Andrew Morton wrote:
> >>> That was a goofup. I proposed that we should add a #define
> >>>
On Fri, Oct 26, 2007 at 11:18:49AM -0700, Mark Gross wrote:
> The following patch clears the portect memory region enable bit at
> boot time by default. It also provides a kernel parrameter for
> disabling this behavior and leave the PMEN_REG untouched if so
> wanted.
>
> If the boot loader or
* remove unnecessary cast
* remove unnecessary use of 'irq' function arg
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
---
drivers/scsi/NCR5380.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/NCR5380.c b/drivers/scsi/NCR5380.c
index
* Bug fix: Make sure request_irq() and free_irq() are called
with the same dev_id pointer argument.
* Bug fix: always pass 'irq' and 'dev_id' (aka 'dummy')
arguments to NCE5380_intr() when calling it manully. For some drivers
this doesn't matter, depending on whose copy of NCR5380_intr()
Thomas Gleixner wrote:
> On Fri, 26 Oct 2007, Hiroshi Shimamoto wrote:
>
> Added Venki to CC
>
>>> I'm now testing crash on 32bit, but there is an issue before
>>> applying the patches. My machine stopped at checking 'hlt'
>>> after kexec, showing below message.
>>>
>>> CPU: Intel(R) Xeon(TM)
Arjan van de Ven wrote:
On Fri, 26 Oct 2007 17:47:58 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
Andrew Morton wrote:
That was a goofup. I proposed that we should add a #define
TWO_ARG_IRQ_HANDLERS (or whatever) and I think I actually wrote the
patch, but it got lost.
I agree it would be a
David Miller <[EMAIL PROTECTED]> writes:
> From: Rick Jones <[EMAIL PROTECTED]>
> Date: Fri, 26 Oct 2007 16:31:47 -0700
>
>> Eric W. Biederman wrote:
>> > Adrian Bunk <[EMAIL PROTECTED]> writes:
>> >
>> >
>> >>This patch fixes the following build error with CONFIG_SYSCTL=n:
>> >>
>> >><-- snip
> often I get "CIFS VFS: server not responding".
> together with "CIFS VFS: No response for cmd 50 mid xxx" The xxx number
> seems to vary. The problem seems to be triggered by any operation
> which touches lots of files quickly. E.g.
> by copying source file directories onto or from it or
On Fri, 26 Oct 2007 17:47:58 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > That was a goofup. I proposed that we should add a #define
> > TWO_ARG_IRQ_HANDLERS (or whatever) and I think I actually wrote the
> > patch, but it got lost.
> >
> > I agree it would be a kind
From: Rick Jones <[EMAIL PROTECTED]>
Date: Fri, 26 Oct 2007 16:46:36 -0700
> David Miller wrote:
> > If DLM really wants minimum, it can use SO_SNDBUFFORCE and
> > SO_RCVBUFFORCE socket options and use whatever limits it
> > likes.
> >
> > But even this is questionable.
>
> Drift...
>
> Is
David Miller wrote:
If DLM really wants minimum, it can use SO_SNDBUFFORCE and
SO_RCVBUFFORCE socket options and use whatever limits it
likes.
But even this is questionable.
Drift...
Is that something netperf should be using though? Right now it uses the regular
SO_[SND|RCV]BUF calls and
All,
The following is an extra entry to enable the touch screen on the new LG
C1 EXPRESS DUAL machine.
Thanks,
D.
diff -uprN -X linux-2.6.21.4__vanilla/Documentation/dontdiff
linux-2.6.21.4__vanilla/drivers/serial/8250_pnp.c
linux-2.6.21.4__C1-PB11A3/drivers/serial/8250_pnp.c
---
From: Rick Jones <[EMAIL PROTECTED]>
Date: Fri, 26 Oct 2007 16:31:47 -0700
> Eric W. Biederman wrote:
> > Adrian Bunk <[EMAIL PROTECTED]> writes:
> >
> >
> >>This patch fixes the following build error with CONFIG_SYSCTL=n:
> >>
> >><-- snip -->
> >>
> >>...
> >>ERROR: "sysctl_rmem_max"
Introduce FIBMAP64. This is the same as FIBMAP, but takes a u64.
This new routine requires filesystems to implement bmap64 if they want to
support > 2^31 blocks in a logical file. We do this to give time for
filesystems to be properly audited.
Signed-off-by: Mike Waychison <[EMAIL
Propagate an error (EFBIG) to userspace if the physical block is too large to
return in a 32bit int instead of truncating it.
Signed-off-by: Mike Waychison <[EMAIL PROTECTED]>
fs/ioctl.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
Index: linux-2.6.23/fs/ioctl.c
Remove the need for having CAP_SYS_RAWIO when doing a FIBMAP call on an open
file descriptor.
It would be nice to allow users to have permission to see where their data is
landing on disk, and there really isn't a good reason to keep them from getting
at this information.
Signed-off-by: Mike
Attempt to deal with races with truncate paths.
I'm not really sure on the locking here, but these seem to be taken by the
truncate path. BKL is left as some filesystem may(?) still require it.
Signed-off-by: Mike Waychison <[EMAIL PROTECTED]>
fs/ioctl.c |8
1 file changed, 8
Move FIBMAP logic out of file_ioctl() in preparation for introducing FIBMAP64.
Signed-off-by: Mike Waychison <[EMAIL PROTECTED]>
fs/ioctl.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
Index: linux-2.6.23/fs/ioctl.c
Return an error if the user requests a negative logical block in a file.
Signed-off-by: Mike Waychison <[EMAIL PROTECTED]>
fs/ioctl.c |2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6.23/fs/ioctl.c
===
---
The following series is meant to clean up FIBMAP paths with the eventual goal
of allowing users to be able to FIBMAP their data.
I'm sending this as an RFC as I've only tested this on a x86_64 kernel with a
32bit binary on ext2 and I've noticed a couple ext2_warnings already.
I'm unsure of the
This is a kernel patch to add support LZO compression in cramfs.
I used LZO kernel library patch done by Richard Purdie
[EMAIL PROTECTED], and my cramfs patch requires his LZO library
patch.
Richard's LZO kernel library patch can be found at:
http://lwn.net/Articles/238723/
This patch is
This patch adds support LZO compression in mkcramfs tool, so it can
generate a cramfs image compress with LZO.
To compile mkcramfs with this patch, liblzo2-dev package must be
installed.
The patch is created against mkcramfs tool ver 1.1 which can be found
at:
Linus Torvalds wrote:
>
> On Fri, 26 Oct 2007, Zach Brown wrote:
>> I can throw together a patch if you haven't already committed one by the
>> time you read this ;).
>
> I'm not touching that code except to send out possible patches for others
> to test and comment on. I have no test-cases,
Eric W. Biederman wrote:
Adrian Bunk <[EMAIL PROTECTED]> writes:
This patch fixes the following build error with CONFIG_SYSCTL=n:
<-- snip -->
...
ERROR: "sysctl_rmem_max" [fs/dlm/dlm.ko] undefined!
ERROR: "sysctl_wmem_max" [drivers/net/rrunner.ko] undefined!
ERROR: "sysctl_rmem_max"
Linus Torvalds wrote:
>
> On Fri, 26 Oct 2007, Zach Brown wrote:
>> I can throw together a patch if you haven't already committed one by the
>> time you read this ;).
>
> I'm not touching that code except to send out possible patches for others
> to test and comment on. I have no test-cases,
On Fri, Oct 26, 2007 at 11:46:39AM +0200, Tilman Schmidt wrote:
> On Thu, 25 Oct 2007 19:56:47 -0700, Greg KH wrote:
> > On Fri, Oct 26, 2007 at 01:09:14AM +0200, Tilman Schmidt wrote:
> >> Am 25.10.2007 00:31 schrieb Adrian Bunk:
> >> > Generally, the goal is to get external modules included into
On Friday, 26 October 2007 03:03, CSights wrote:
> Hi LKML,
> My computer running kernel 2.6.23 does not "hibernate" (suspend to disk
> using
> the kernel's methods) with a program (named stringTest) running in gdb, but
> has received a SIGABRT.
> The hibernate is successful when
Adrian Bunk <[EMAIL PROTECTED]> writes:
> This patch fixes the following build error with CONFIG_SYSCTL=n:
>
> <-- snip -->
>
> ...
> ERROR: "sysctl_rmem_max" [fs/dlm/dlm.ko] undefined!
> ERROR: "sysctl_wmem_max" [drivers/net/rrunner.ko] undefined!
> ERROR: "sysctl_rmem_max"
On Fri, 26 Oct 2007, Zach Brown wrote:
>
> I can throw together a patch if you haven't already committed one by the
> time you read this ;).
I'm not touching that code except to send out possible patches for others
to test and comment on. I have no test-cases, nor any real interest in it.
So
This patch fixes the following build error with CONFIG_SYSCTL=n:
<-- snip -->
...
ERROR: "sysctl_rmem_max" [fs/dlm/dlm.ko] undefined!
ERROR: "sysctl_wmem_max" [drivers/net/rrunner.ko] undefined!
ERROR: "sysctl_rmem_max" [drivers/net/rrunner.ko] undefined!
make[2]: *** [__modpost] Error 1
<--
The list of options that the fd transport accepts is missing end-of-options
marker. This patch adds it.
Signed-off-by: Latchesar Ionkov <[EMAIL PROTECTED]>
---
commit 70ec0c7936c2516d128fdb1a32d749071b8846ec
tree 8de5495f83b94096825f8bfe0767e4fcbaf36ef3
parent
v9fs_match_trans function returns arbitrary transport module instead of NULL
when the requested transport is not registered. This patch modifies the
function to return NULL in that case.
Signed-off-by: Latchesar Ionkov <[EMAIL PROTECTED]>
---
commit 25ed88ed319e40fb6426e2aaefcc5f136aadd4ee
tree
v9fs_parse_options function uses strsep which modifies the value of the
v9ses->options field. That modified value is later passed to the function
that creates the transport potentially making the transport creation
function to fail.
This patch creates a copy of v9ses->option field that
On 25 Oct 2007, Ph. Marek told this:
> -) use some ramfs/shmfs or similar, and overwrite the data occasionally
>- not current data
>- runtime overhead (processor load)
This is roughly what the nscd implementation in glibc does: the client
can work over a socket, but prefers to ask the
Linus Torvalds wrote:
>
> On Fri, 26 Oct 2007, Zach Brown wrote:
>> I think that test should be changed to
>
> How about not testing at all? Which was what the old code did.
>
> Just do the invalidate unconditionally for any writes, and screw the end
> result of the invalidate, since we cannot
Jason Uhlenkott wrote:
On Fri, Oct 26, 2007 at 14:59:57 -0700, Mike Waychison wrote:
Jason Uhlenkott wrote:
Additionally, ext3_bmap() has this to say about it:
if (EXT3_I(inode)->i_state & EXT3_STATE_JDATA) {
/*
* This is a REALLY heavyweight approach,
On Fri, Oct 26, 2007 at 01:07:50PM -0400, bfields wrote:
> On Thu, Oct 18, 2007 at 02:57:59PM -0400, George G. Davis wrote:
> > On Wed, Oct 17, 2007 at 02:51:57PM -0400, George G. Davis wrote:
> > > ---
> > > Not sure if this is the correct fix but it does resolve the hangs we're
> > > observing
On Fri, 26 Oct 2007, Zach Brown wrote:
>
> I think that test should be changed to
How about not testing at all? Which was what the old code did.
Just do the invalidate unconditionally for any writes, and screw the end
result of the invalidate, since we cannot afford to overwrite the previous
* Tony Jones ([EMAIL PROTECTED]) wrote:
> From: Tony Jones <[EMAIL PROTECTED]>
> Minor performance enhancement.
>
> Thread flag TIF_SYSCALL_AUDIT is not cleared for new children when audit
> context creation has been disabled (auditctl -e0). This can cause new
> children
> forked from a parent
Karsten Keil wrote:
* change #warning to a code comment
* add comment and special ifdef'd 64-bit code for a situation where
we must store a pointer into a CAPI field 'Data', which is fixed by
the interface at 32 bits.
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
Acked-by: Karsten Keil
Zach Brown wrote:
> Linus Torvalds wrote:
>> Hmm. If I read this right, this bug seems to have been introduced by
>> commit 65b8291c4000e5f38fc94fb2ca0cb7e8683c8a1b ("dio: invalidate clean
>> pages before dio write") back in March.
>
> Agreed. And it's a really dumb bug. ->direct_io will
On Fri, Oct 26, 2007 at 14:59:57 -0700, Mike Waychison wrote:
> Jason Uhlenkott wrote:
> >Additionally, ext3_bmap() has this to say about it:
> >
> >if (EXT3_I(inode)->i_state & EXT3_STATE_JDATA) {
> >/*
> > * This is a REALLY heavyweight approach, but the
On Fri, 26 Oct 2007, Hiroshi Shimamoto wrote:
Added Venki to CC
> > I'm now testing crash on 32bit, but there is an issue before
> > applying the patches. My machine stopped at checking 'hlt'
> > after kexec, showing below message.
> >
> > CPU: Intel(R) Xeon(TM) CPU 3.80GHz stepping 0a
> >
"Kir Kolyshkin" <[EMAIL PROTECTED]> writes:
> Speaking of this particular patch -- I don't understand how you fix
> "innumerable little bugs" by providing stubs instead of real functions.
I think it would be a disaster to use pid namespaces as currently
implemented 2.6.24-rc1 in a production
On Fri, 26 Oct 2007 14:59:01 -0700
Martin Bligh <[EMAIL PROTECTED]> wrote:
> Rik van Riel wrote:
> > On Fri, 26 Oct 2007 14:11:12 -0700
> > Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> >> Sure, but in terms of high-level userspace interface, being able to
> >> select() on a group of priority
Linus Torvalds wrote:
> Hmm. If I read this right, this bug seems to have been introduced by
> commit 65b8291c4000e5f38fc94fb2ca0cb7e8683c8a1b ("dio: invalidate clean
> pages before dio write") back in March.
Agreed. And it's a really dumb bug. ->direct_io will almost always
return
Andrew Morton <[EMAIL PROTECTED]> wrote:
> hm, seems a bit ungainly. Why can't we just make all the aout things in
> binfmt_elf.c depend upon CONFIG_BINFMT_AOUT?
That works too, I guess. I'll change it.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Fri, 26 Oct 2007 15:16:53 -0700
Crispin Cowan <[EMAIL PROTECTED]> wrote:
>
> > On the first part (discussion of the model) I doubt we can get
> > people to agree, that's pretty much phylosophical... on the second
> > part (how well the code/design lives up to its own goals) the
> > analysis
On Fri, 26 Oct 2007, Giacomo Catenazzi wrote:
>
> So we have the great opportunity to change the standard, then
> gcc will change ;-)
I see the smiley, but sadly, new standards take ten years or more to
mature. Which means that even if the upcoming one is "perfect", things
will be wrong with
Arjan van de Ven wrote:
> My main concern for now is a description of what it tries to protect
> against/in what cases you would expect to use it. THe reason for asking
> this explicitly is simple: Until now the LSM discussions always ended
> up in a nasty mixed up mess around disagreeing on the
"Kir Kolyshkin" <[EMAIL PROTECTED]> writes:
> Eric, this problem is a known one. Currently Pavel and Sukadev are working on
> a
> appropriate signal management for namespaces.
I'm fairly certain that the signal issue you they are dealing with
is how to keep children from killing the init of a
Linus Torvalds wrote:
> So we may
> actually end up doing some IO, but then returning the "wrong" error code
> from the invalidate. Hmm?
>
A point. In an all-seeing, all-caring universe, it would be the read
hitting the cached page that couldn't be invalidated that would get
the error, not
On Friday 26 October 2007 22:58:11 Miklos Szeredi wrote:
> For special files, f_op->fsetattr will be NULL, since
> init_special_inode() will set up i_fop that way.
>
> So the filesystem's fsetattr() will only be called for regular files
> and/or directories, depending on how it sets up i_fop.
>
>
On Fri, Oct 26, 2007 at 01:22:17 +0100, Alan Cox wrote:
> On Thu, 25 Oct 2007 16:06:40 -0700
> Mike Waychison <[EMAIL PROTECTED]> wrote:
>
> > Remove the need for having CAP_SYS_RAWIO when doing a FIBMAP call on an
> > open file descriptor.
> >
> > It would be nice to allow users to have
Jason Uhlenkott wrote:
On Fri, Oct 26, 2007 at 01:22:17 +0100, Alan Cox wrote:
On Thu, 25 Oct 2007 16:06:40 -0700
Mike Waychison <[EMAIL PROTECTED]> wrote:
Remove the need for having CAP_SYS_RAWIO when doing a FIBMAP call on an open
file descriptor.
It would be nice to allow users to have
"Kir Kolyshkin" <[EMAIL PROTECTED]> writes:
> Eric,
>
> Could you please hold off the horses a bit and wait till Pavel Emelyanov
> returns? It means next Monday; he's currently at a conference whose organisers
> don't provide internet access.
When we decided to go top down (i.e. user interface
Rik van Riel wrote:
On Fri, 26 Oct 2007 14:11:12 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
Sure, but in terms of high-level userspace interface, being able to
select() on a group of priority buckets (spread across different
nodes, zones and cgroups) seems a lot more flexible than any
On Fri, Oct 26, 2007 at 05:40:22AM -0400, Jeff Garzik wrote:
> arch/arm/mach-pxa/ssp.c|2 +-
> arch/arm/mach-s3c2410/usb-simtec.c |2 +-
> arch/arm/plat-omap/mailbox.c |2 +-
FWIW
Acked-by: Lennert Buytenhek <[EMAIL PROTECTED]>
-
To
On Fri, Oct 26, 2007 at 05:40:25AM -0400, Jeff Garzik wrote:
> mach-integrator/pci_v3.c: no need to reference 'irq' arg, its constant
>
> mach-omap1/pm.c: remove extra whitespace
>
> arch/arm/mach-sa1100/ssp.c: remove braces around single C stmt
>
> arch/arm/plat-omap/mcbsp.c:
> - remove
1 - 100 of 1126 matches
Mail list logo
