What was preventing you from just using the x86_64 code here?
Some was borrowed - but not much. since we don't support vga, or 16550 UARTs
(Blackfin has it's own on-chip UART), I don't think this would work.
Maybe I'm missing something - but I don't think so. Every one who implements
git-bisect bad ab144f5ec64c42218a555ec1dbde6b60cf2982d6
Also breaks booting in VMWare's WS 6 if paravirtual support is enabled for the
guest.
Hope this helps narrow it down.
Sean
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Sat, Aug 18, 2007 at 10:48:31AM +0800, Fengguang Wu wrote:
Matt,
On Fri, Aug 17, 2007 at 11:58:08AM -0500, Matt Mackall wrote:
On Fri, Aug 17, 2007 at 02:47:27PM +0800, Fengguang Wu wrote:
It's not easy to do direct performance comparisons between pmaps and
pagemap/kpagemap. However
From: Roland Dreier [EMAIL PROTECTED]
Date: Fri, 17 Aug 2007 22:23:01 -0700
Also, looking at the complexity and bug-fixing effort that go into
making TSO work vs the really pretty small gain it gives also makes
part of me wonder whether the noble proclamations about
maintainability are always
On Monday 13 August 2007, Bjorn Helgaas wrote:
On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote:
This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable
PnP by default; it is apparently enabled now and fails to activte IrDA
completely. So it moves to
Stephen Hemminger a écrit :
Optimize uses of memset with small constant offsets.
This will generate smaller code, and avoid the slow rep/string instructions.
Code copied from i386 with a little cleanup.
You obviously didnt test it, did you ?
How can you be sure this is going to speedup
On Fri, 2007-08-17 at 11:56 -0400, Josef Sipek wrote:
On Thu, Aug 16, 2007 at 09:45:34AM +0200, Peter Zijlstra wrote:
Index: linux-2.6/fs/ext2/super.c
===
--- linux-2.6.orig/fs/ext2/super.c
+++ linux-2.6/fs/ext2/super.c
@@
On 8/18/07, Thomas Gleixner [EMAIL PROTECTED] wrote:
If yes, who invented this 1980s reminiscence, where you got valid
pointers for malloc(0) ?
Well, kmalloc(0) has always been legal and traditionally returned a
pointer to a smallest non-zero sized object. We did try to make
kmalloc(0) illegal
On Aug 18 2007 01:40, Thomas Gleixner wrote:
Do we really ?
If yes, who invented this 1980s reminiscence, where you got valid
pointers for malloc(0) ?
This is completely stupid. You do not go into a bar and order an empty
glass, just because you might eventually become thirsty later.
Matt,
On Sat, Aug 18, 2007 at 01:40:42AM -0500, Matt Mackall wrote:
- On memory pressure,
- as VSZ goes up, RSS will be bounded by physical memory.
So VSZ:RSS ratio actually goes up with memory pressure.
And yes.
But that's not what I'm talking about. You're likely to have more
The email you sent seems to be pure text, from my email client.
Xu Yang wrote:
how to send a email of text format?
-
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!
If we exhaust the reserves in the page allocator when PF_MEMALLOC is set
then no longer give up but call into reclaim with PF_MEMALLOC set.
This is in essence a recursive call back into page reclaim with another
page flag (__GFP_NOMEMALLOC) set. The recursion is bounded since potential
fs/select, remove unused macros
this is due to preparation for global BIT macro
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 8754d87e5b6221e7d34cccef473588d5170b689e
tree 52ac6a983077ab5854dcacfa4b0e3323c7bbd9c8
parent 7129cd56f4f7f8d9f7cc9deb9a62291fc989cf91
author Jiri Slaby [EMAIL
cyber2000fb, rename BIT macro
BIT will be global macro for (1 x)
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit e99a73f0e9d20869736b5cbd106f63fe31d63c85
tree 33d5589b80148507614fb5c203c752a744b999be
parent 8754d87e5b6221e7d34cccef473588d5170b689e
author Jiri Slaby [EMAIL PROTECTED]
i2c-pxa, rename BIT macro to PXA_BIT
BIT macro will be global definiton of (1 x)
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 6aec5d2e526e319488e6cdd627ca370086d458df
tree 322ca256a63baf90c75688c6aff3e253352c2321
parent e99a73f0e9d20869736b5cbd106f63fe31d63c85
author Jiri Slaby
s2io, rename BIT macro
BIT macro will be global definiton of (1x)
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 0d66c4337fec02f0b9bd1c1fd783b60fbab5438b
tree c2027e1c366255dbec6ae061aed2c5cf809232b0
parent 6aec5d2e526e319488e6cdd627ca370086d458df
author Jiri Slaby [EMAIL PROTECTED]
amba-pl011, rename BIT macro
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 4e7c777ee287082c3185d50a5dab813f562f70de
tree 6f3888ad93bef885d9b9e7641a25e0d1ab16b19e
parent 0d66c4337fec02f0b9bd1c1fd783b60fbab5438b
author Jiri Slaby [EMAIL PROTECTED] Sun, 12 Aug 2007 21:48:05 +0200
committer
define first set of BIT* macros
- move BITOP_MASK and BITOP_WORD from asm-generic/bitops/atomic.h to
include/linux/bitops.h and rename it to BIT_MASK and BIT_WORD
- move BITS_TO_LONGS and BITS_PER_BYTE to bitops.h too and allow easily
define another BITS_TO_something (e.g. in event.c) by
define global BIT macro
move all local BIT defines to the new globally define macro.
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 19b14b967521eda7011bd70891bbe5044882d739
tree cd49de4f9f8d991ee7af22037a86978ea227abb8
parent fef5bcc8e5a7bfd66920df6d02c3448314dfe4b2
author Jiri Slaby
FlashPoint, use BIT instead of BITW
BITW was an ushort variant of BIT, use BIT instead
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
commit 5c0addab96a66ef8b8fc7f8fc404873f7744f7bd
tree c6e584d120ff637ed769925c7240e8078ecb56bd
parent 19b14b967521eda7011bd70891bbe5044882d739
author Jiri Slaby
Xu Yang wrote:
When I was porting kernel 2.6.19 to my realview_eb_mpcore system, I
got the following information.
...
does anyone know what does these information tell ? and where might be
the problem?
...
5Linux version 2.6.19-arm2 ([EMAIL PROTECTED]) (gcc
version 4.2.0 20070413
On Saturday 18 August 2007 01:34:46 Stephen Hemminger wrote:
Optimize uses of memset with small constant offsets.
This will generate smaller code, and avoid the slow rep/string instructions.
Code copied from i386 with a little cleanup.
Newer gcc should do all this on its own. That is why I
This patch breaks Xen booting.
Check the latest git head. Does it still break?
-Andi
-
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
Willy Tarreau wrote:
On Fri, Aug 17, 2007 at 06:24:17PM +0200, Xu Yang wrote:
I have built up a software virtual prototype system with ARM11MPCORE.
my system is similar with realview_eb_mpcore. but my system is
simpler, which has only a mpcore , uart0, console,timer0_1, and
memorys.
I want
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss driver).
I compiled XFS as a module and tried it out since I'm used to using it
on Debian, which runs much more efficiently. However, every so often the
kernel
Hi Willy ,
thanks for your reply.
I am sure that my timer is working( TIMER0_1), because I checked the
register , it was counting , and the interrupt flag register also
gives out interrupts periodicly.
the problem is that it seems that the program just toggles here:
interrupt rountines,
Ok I will try that.
thanks :)
2007/8/18, Stefan Richter [EMAIL PROTECTED]:
Willy Tarreau wrote:
On Fri, Aug 17, 2007 at 06:24:17PM +0200, Xu Yang wrote:
I have built up a software virtual prototype system with ARM11MPCORE.
my system is similar with realview_eb_mpcore. but my system is
Hi Stefan,
thanks for your explaination:)
I will try the kernel 2.6.22 and reprot the results later.
regards,
yang
2007/8/18, Stefan Richter [EMAIL PROTECTED]:
Xu Yang wrote:
When I was porting kernel 2.6.19 to my realview_eb_mpcore system, I
got the following information.
...
does
On Sat, Aug 18, 2007 at 01:40:42AM -0500, Matt Mackall wrote:
- you don't get page frame numbers
True. I guess PFNs are meaningless to a normal user?
They're useful for anyone who's trying to look at the system as a
whole.
To answer the question: who are sharing this page with me?
This commit broke my master volume control:
5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 is first bad commit
commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1
Author: Ivan N. Zlatev [EMAIL PROTECTED]
Date: Tue May 29 16:03:00 2007 +0200
[ALSA] hda-codec - Fix pin configs for Intel Macs
*
On Fri, Aug 17, 2007 at 10:19:00AM -0400, Dave Jones wrote:
On Wed, Aug 15, 2007 at 12:48:35AM +0200, Andi Kleen wrote:
In general the .data protection is only considered a debugging
feature. I don't know why Fedora enables it in their production
kernels.
That would be
On Fri, 2007-08-17 at 21:06 -0700, David Brownell wrote:
On Friday 17 August 2007, Kay Sievers wrote:
I'm not the one who's advocating a change here. If you want to
first change/break and then fix things, all of that is up to you.
I'm happy to do that. Patch is attached.
NAK.
On 13 Aug, Jan Engelhardt wrote:
On Aug 13 2007 19:59, Michal Piotrowski wrote:
Subject : Kconfig prompts without help text
References : http://lkml.org/lkml/2007/7/16/326
Last known good : ?
Submitter : Stefan Richter [EMAIL PROTECTED]
Caused-By : ?
Handled-By :
This patch just move duplicated code from end_buffer_read_XXX
methods to separate helper function.
Signed-off-by: Dmitry Monakhov [EMAIL PROTECTED]
---
fs/buffer.c | 32 +---
1 files changed, 17 insertions(+), 15 deletions(-)
diff --git a/fs/buffer.c b/fs/buffer.c
--- Willy Tarreau [EMAIL PROTECTED] wrote:
No Stephen, look again, he says that moving the
video card into the broken
system does not change anything.
Correct, I've used three different video cards in the
broken machine. I've used an old PCI vid card, the
PCI-X vid card from the working
On Sat, Aug 18, 2007 at 02:22:28AM +0400, Oleg Nesterov wrote:
Neil Horman wrote:
+static int proc_pid_limits(struct task_struct *task, char *buffer)
+{
+ unsigned int i;
+ int count = 0;
+ char *bufptr = buffer;
+
+ struct rlimit rlim[RLIM_NLIMITS];
+
+
On Sat, Aug 18, 2007 at 04:45:26AM -0700, Kevin E wrote:
--- Willy Tarreau [EMAIL PROTECTED] wrote:
No Stephen, look again, he says that moving the
video card into the broken
system does not change anything.
Correct, I've used three different video cards in the
broken machine. I've
Chris Boot [EMAIL PROTECTED] writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS as a module and tried it out since I'm used to
using it on Debian, which runs much more
On Friday 17 August 2007 23:07:33 Christoph Lameter wrote:
On Fri, 17 Aug 2007, Mel Gorman wrote:
Opinions as to why FASTCALL breaks on one machine are welcome.
Could we get rid of FASTCALL? AFAIK the compiler should automatically
choose the right calling convention?
It was a nop for
On Aug 18 2007 13:31, Måns Rullgård wrote:
BUG: unable to handle kernel paging request at virtual address b8af9d60
printing eip:
c0415974
*pde =
Oops: [#1]
SMP last sysfs file: /block/loop7/dev
Modules linked in: loop nfsd exportfs lockd nfs_acl iscsi_trgt(U)
autofs4 hidp
On 08/18, Neil Horman wrote:
On Sat, Aug 18, 2007 at 02:22:28AM +0400, Oleg Nesterov wrote:
Neil Horman wrote:
+static int proc_pid_limits(struct task_struct *task, char *buffer)
+{
+ unsigned int i;
+ int count = 0;
+ char *bufptr = buffer;
+
+ struct rlimit
[ LOL, you _are_ shockingly petty! ]
On Sat, 18 Aug 2007, Segher Boessenkool wrote:
The documentation simply doesn't say +m is allowed. The code to
allow it was added for the benefit of people who do not read the
documentation. Documentation for +m might get added later if it
is
On Fri, 17 Aug 2007, Linus Torvalds wrote:
On Sat, 18 Aug 2007, Satyam Sharma wrote:
No code does (or would do, or should do):
x.counter++;
on an atomic_t x; anyway.
That's just an example of a general problem.
No, you don't use x.counter++. But you *do* use
Martin K. Petersen wrote:
Stefan == Stefan Richter [EMAIL PROTECTED] writes:
Stefan There were some similar reports involving that status write
Stefan for unknown orb. I haven't found a way to reproduce it; I
Stefan noticed it only once in the logs here so far.
I get those all the time.
It seems unlikely, but access to self_id_cpu[0] could at least in theory
be deferred until after the loop over self_id_cpu[1..n] or even after
the subsequent reg_read. Enforce the desired order by a read barrier.
Also prevent the reg_read from being reordered relative to the for loop.
This isn't
--- Willy Tarreau [EMAIL PROTECTED] wrote:
OK, in this trace, both controllers are on the same
bus. The broken
one has 'Capabilities: [100] Advanced Error
Reporting' the other
does not have, and the bridge to this bus has two
more capabilities :
'Capabilities: [100] Virtual Channel' and
When 'Show debug info' is checked then a list of links
to dependant symbols is shown in info view right bottom pane.
Currently all links are in standard blue. With this patch
links to disabled symbols are shown in red instead.
This, together with 'Show all options', allows to quickly
check out
On Fri, 17 Aug 2007, Jeff Dike wrote:
Style fixes in hostfs.
Index: linux-2.6.22/fs/hostfs/hostfs_kern.c
[...]
@@ -6,22 +6,15 @@
* 2003-02-10 Petr Baudis [EMAIL PROTECTED]
*/
-#include linux/stddef.h
#include linux/fs.h
#include linux/module.h
-#include linux/init.h
On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
On Thu, 16 Aug 2007, NeilBrown wrote:
[...]
dev_dbg(dev-sbd.core,
%s:%u: bio %u: %u segs %u sectors from %lu\n,
- __func__, __LINE__, i, bio_segments(bio),
-
Hi list,
I am facing a very strange issue about device probe order.
I have a piece of code to support network interface card for an embedded box.
It likes following:
...
static struct platform_device *custom_devices[] __initdata = {
a_device,
b_device,
c_device,
};
On Sat, 18 Aug 2007, Segher Boessenkool wrote:
GCC manual, section 6.1, When
^^
is a Volatile Object Accessed? doesn't say anything of the
^^^
kind.
^
True,
On Aug 18 2007 20:07, Satyam Sharma wrote:
On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
On Thu, 16 Aug 2007, NeilBrown wrote:
[...]
dev_dbg(dev-sbd.core,
%s:%u: bio %u: %u segs %u sectors from %lu\n,
- __func__, __LINE__, i,
On Sat, 18 Aug 2007, Jan Engelhardt wrote:
On Aug 18 2007 20:07, Satyam Sharma wrote:
On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
On Thu, 16 Aug 2007, NeilBrown wrote:
[...]
dev_dbg(dev-sbd.core,
%s:%u: bio %u: %u segs %u sectors from
Nick Piggin wrote:
Stefan Richter wrote:
Nick Piggin wrote:
I don't know why people would assume volatile of atomics. AFAIK, most
of the documentation is pretty clear that all the atomic stuff can be
reordered etc. except for those that modify and return a value.
Which documentation is
Måns Rullgård wrote:
Chris Boot [EMAIL PROTECTED] writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS as a module and tried it out since I'm used to
using it on Debian, which
On Sat, 18 Aug 2007 11:46:24 +0200
Andi Kleen [EMAIL PROTECTED] wrote:
On Saturday 18 August 2007 01:34:46 Stephen Hemminger wrote:
Optimize uses of memset with small constant offsets.
This will generate smaller code, and avoid the slow rep/string instructions.
Code copied from i386 with a
On Sat, Aug 18, 2007 at 12:08:54AM -0700, Joe Perches wrote:
KERNEL NFSD
P: J. Bruce Fields
M: [EMAIL PROTECTED]
P: Neil Brown
M: [EMAIL PROTECTED]
L: [EMAIL PROTECTED]
W: http://nfs.sourceforge.net/
S: Supported
+F: fs/nfsd/
+F: include/linux/nfsd/
Also, some
On 2007/08/16 , at 13:01, Karsten Keil wrote:
On Thu, Aug 16, 2007 at 01:22:04PM +0300, Ilpo Järvinen wrote:
...I guess those guys hunting for broken busyloops in the other
thread
could also benefit from similar searching commands introduced in this
thread... ...Ccing Satyam to caught
These don't appear anywhere else in the kernel anymore.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
Cc: Bryan Wu [EMAIL PROTECTED]
Cc: Yoshinori Sato [EMAIL PROTECTED]
Cc: Greg Ungerer [EMAIL PROTECTED]
Cc: Paul Mundt [EMAIL PROTECTED]
Cc: Miles Bader [EMAIL PROTECTED]
---
On Sat 18 Aug 2007 02:23, Sam Ravnborg pondered:
What was preventing you from just using the x86_64 code here?
Some was borrowed - but not much. since we don't support vga, or
16550 UARTs (Blackfin has it's own on-chip UART), I don't think
this would work. Everyone implements
Chris Boot [EMAIL PROTECTED] writes:
Måns Rullgård wrote:
Chris Boot [EMAIL PROTECTED] writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS as a module and tried it out since
On Sat, Aug 18, 2007 at 05:32:05PM +0200, Stefan Richter wrote:
These don't appear anywhere else in the kernel anymore.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
Cc: Bryan Wu [EMAIL PROTECTED]
Cc: Yoshinori Sato [EMAIL PROTECTED]
Cc: Greg Ungerer [EMAIL PROTECTED]
Cc: Paul Mundt
* Fengguang Wu ([EMAIL PROTECTED]) wrote:
Al Viro,
Does this sounds like a good fix?
===
seq_file version fixes
- f_version is 'unsigned long', it's pointless to do more than that.
Hrm, this is weird...
fs.h:
struct inode
u64 i_version;
and
struct file
In embedded system design, it may be useful to poweroff the disks (as opposed
to merely spinning them down). We want to leave the system running while
the disk is powered down, and let the disk powerup when it needs to be
spun up.
While the power off mechanism would be platform dependent, is
Fix f_version type: should be u64 instead of long
There is a type inconsistency between struct inode i_version and struct file
f_version.
fs.h:
struct inode
u64 i_version;
and
struct file
unsigned long f_version;
Users do:
fs/ext3/dir.c:
if (filp-f_version
On Aug 18 2007 12:08, Marty Leisner wrote:
In embedded system design, it may be useful to poweroff the disks (as opposed
to merely spinning them down). We want to leave the system running while
the disk is powered down, and let the disk powerup when it needs to be
spun up.
That means you also
Måns Rullgård wrote:
Chris Boot [EMAIL PROTECTED] writes:
Måns Rullgård wrote:
Chris Boot [EMAIL PROTECTED] writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS as
On Aug 18 2007 17:28, Chris Boot wrote:
I will. This will probably be on Monday now, since the machine isn't
accepting SysRq requests over the serial console. :-(
Ah yeah, stupid null-modem cables!
You can also trigger sysrq from /proc/sysrq-trigger (well, as long
as the system lives)
Hi Joe,
Patch removed until there is a consensus on how to proceed with your
proposal.
Hi Wim.
I think that's wise.
I've got all the changes that people have CC'd me.
I expect it'll be an all or nothing sort of thing.
My opinion: the patch you sent me was just adding the differen
On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
define global BIT macro
move all local BIT defines to the new globally define macro.
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
include/linux/bitops.h |1 +
include/video/sstfb.h
--- Kyle Moffett [EMAIL PROTECTED] wrote:
On Aug 17, 2007, at 15:01:48, Phillip Susi wrote:
[EMAIL PROTECTED] wrote:
It will become even *more* of a not that common
if the lock will
block moves and ACL changes *across the
filesystem* for
potentially *minutes* at a time.
It
On Sat, 18 Aug 2007 00:08:54 -0700 Joe Perches wrote:
Added patterns to describe files maintained.
Signed-off-by: Joe Perches [EMAIL PROTECTED]
diff --git a/MAINTAINERS b/MAINTAINERS
index d3a0684..d7fe1c5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19,40 +19,44 @@ trivial patch
On Sat, 2007-08-18 at 11:00 -0400, J. Bruce Fields wrote:
Also, some paths that are shared with the client:
+F: fs/lockd/
+F: fs/nfs_common/
+F: net/sunrpc/
+F: include/linux/lockd/
+F: include/linux/sunrpc/
This is what I have now:
KERNEL NFSD
P: J. Bruce Fields
M:
On Sat, 2007-08-18 at 10:05 -0700, Randy Dunlap wrote:
+ PLEASE include the appropriate maintainers and developers
+ that have modified files touched by your patch by using the
s/that/who/
+ automated CC generator (scripts/get_maintainer.pl)
Right.
-
To unsubscribe from this list:
On Sat, Aug 18, 2007 at 10:00:42AM -0700, Joe Perches wrote:
On Sat, 2007-08-18 at 11:00 -0400, J. Bruce Fields wrote:
Also, some paths that are shared with the client:
+F: fs/lockd/
+F: fs/nfs_common/
+F: net/sunrpc/
+F: include/linux/lockd/
+F: include/linux/sunrpc/
This is what
Randy Dunlap napsal(a):
On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
define global BIT macro
move all local BIT defines to the new globally define macro.
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
include/linux/bitops.h |1 +
On Sat, Aug 18, 2007 at 04:45:31PM +0800, Fengguang Wu wrote:
Matt,
On Sat, Aug 18, 2007 at 01:40:42AM -0500, Matt Mackall wrote:
- On memory pressure,
- as VSZ goes up, RSS will be bounded by physical memory.
So VSZ:RSS ratio actually goes up with memory pressure.
And yes.
Hmm. I think this is wrong.
Why? Because the regular 32-bit x86 code does this all completely
differently, and doesn't use dma_mask at all. Instead, it _only_ uses
dev-coherent_dma_mask (which, considering the name of the function,
would seem to make sense).
Considering that the oops comes
There is no any reason to do recalc_sigpending() after changing -sighand.
To begin with, recalc_sigpending() does not take -sighand into account.
This means we don't need to take newsighand-siglock while changing sighands.
rcu_assign_pointer() provides a necessary barrier, and if another process
de_thread() pre-allocates newsighand to make sure that exec() can't fail after
killing all sub-threads. Imho, this buys nothing, but complicates the code:
- this is (mostly) needed to handle CLONE_SIGHAND without CLONE_THREAD
tasks, this is very unlikely (if ever used) case
de_thread:
if (atomic_read(oldsighand-count) = 1)
BUG_ON(atomic_read(sig-count) != 1);
This is not safe without the rmb() in between. The results of two correctly
ordered __exit_signal()-atomic_dec_and_test()'s could be seen out of order
on our CPU.
The same is true for
Now that we don't pre-allocate the new -sighand, we can kill the first fast
path, it doesn't make sense any longer. At best, it can save one list_empty()
check but leads to the code duplication.
Signed-off-by: Oleg Nesterov [EMAIL PROTECTED]
--- t/fs/exec.c~4_FASTPATH 2007-08-18
de_thread() yields waiting for -group_leader to be a zombie. This deadlocks
if an rt-prio execer shares the same cpu with -group_leader. Change the code
to use -group_exit_task/notify_count mechanics.
This patch certainly uglifies the code, perhaps someone can suggest something
better.
this latest project of cramming the full definition of each kernel
subsystem into the MAINTAINERS file has been bothering me, and i've
finally figured out why. it's because the MAINTAINERS file is being
asked to now be the source of reference information that just doesn't
match its name. it's
Jiri Slaby wrote:
Randy Dunlap napsal(a):
On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
define global BIT macro
move all local BIT defines to the new globally define macro.
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
---
include/linux/bitops.h |1 +
On Thu, Aug 09, 2007 at 05:36:39PM +0100, Maciej W. Rozycki wrote:
On Thu, 9 Aug 2007, Olaf Hering wrote:
include/linux/if_fddi.h is an exported header.
It uses __be16. Include linux/types.h to get this prototype.
Please note that for userland it does not matter. With glibc you should
On Sat, Aug 18, 2007 at 09:45:54AM -0700, Marc Perkel wrote:
Linux isn't going to make progress when people try to
figure out how to make something NOT work rather than
to make something work. So if you are going to put
effort into this then why not try to figure out how to
get around the
The problem is that on x86-64 you are overriding memset()
I don't. You must be looking at old source
asm-x86_64/string.h 2.6.23rc3:
#define __HAVE_ARCH_MEMSET
void *memset(void *s, int c, size_t n);
I wanted to do the same on i386 too, but there were some minor obstacles.
The problem is
Ok, I think I see your point. Thanks for the input. New patch attached which
adds the use of the sighand lock to the patch.
Currently, there exists no method for a process to query the resource
limits of another process. They can be inferred via some mechanisms but
they cannot be explicitly
On 08/18, Neil Horman wrote:
+static int proc_pid_limits(struct task_struct *task, char *buffer)
+{
+ unsigned int i;
+ int count = 0;
+ unsigned long flags;
+ char *bufptr = buffer;
+
+ struct rlimit rlim[RLIM_NLIMITS];
+
+ read_lock(tasklist_lock);
+
On Saturday 18 August 2007 19:22:18 Linus Torvalds wrote:
Hmm. I think this is wrong.
Why? Because the regular 32-bit x86 code does this all completely
differently, and doesn't use dma_mask at all. Instead, it _only_ uses
dev-coherent_dma_mask (which, considering the name of the
On Fri 17 Aug 2007 18:34, David Brownell pondered:
On Friday 17 August 2007, Robin Getz wrote:
On Fri 17 Aug 2007 14:24, David Brownell pondered:
Just for the record, this is an unusual way to use these calls.
That is part of the natural evolution of the kernel isn't it - per
James's
On 8/18/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
On Aug 18 2007 12:08, Marty Leisner wrote:
In embedded system design, it may be useful to poweroff the disks (as opposed
to merely spinning them down). We want to leave the system running while
the disk is powered down, and let the disk
Am Freitag, 17. August 2007 schrieben Sie:
On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote:
I need some kernel event that has both DEVICE and MODALIAS set.
up to including kernel 2.6.21 this seems to come from
drivers/usb/core/driver.c if I read the code correctly, and then
it was
Package: linux-image-2.6.22-1-amd64
Version: 2.6.22-3
Severity: grave
Justification: renders package unusable
hi all,
I encountered the same problem than
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg182088.html.
/var/log/dmesg.2.gz:
- = - = - = - = - = - = - = - = - = - =
Package: linux-image-2.6.22-1-amd64
Version: 2.6.22-3
Severity: grave
Justification: renders package unusable
hi all,
I encountered the same problem than
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg182088.html.
/var/log/dmesg.2.gz:
- = - = - = - = - = - = - = - = - = - =
* Rafael J. Wysocki ([EMAIL PROTECTED]) wrote:
On Sunday, 12 August 2007 01:43, Dr. David Alan Gilbert wrote:
* Pavel Machek ([EMAIL PROTECTED]) wrote:
Hi!
Two things which I think would be nice to consider are:
1) Encryption - I'd actually prefer if my luks device did not
Hi Jesper,
I tried as what you told me. and the vmlinux does contain debug
information. but the start address of this vmlinux is 0xc0008000. when
I tried to run this vmlinux, the program always exit at 0x80a0. I
checked out that here is the place mmu is turned on.
so I used objcopy
On Aug 18 2007 21:49, Xu Yang wrote:
I tried as what you told me. and the vmlinux does contain debug
information. but the start address of this vmlinux is 0xc0008000. when
I tried to run this vmlinux, the program always exit at 0x80a0. I
checked out that here is the place mmu is turned on.
so I
subscribe linux-kernel
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
1 - 100 of 274 matches
Mail list logo
