When we want to hot-add a new cpu, it should be on cpu_possible_map. On some archs, we have to specify additional_cpus= boot option. (x86_64, ia64, s390 seems to need this. others ?) If a user enable a cpu which is not counted as possible_cpu, the system will panic. This patch disables to register cpu control if cpu is not in possible_map. Works as expected on ia64/cpu-hotplug-by-ACPI case. Consideration: handling this issue in cpu_up() is an another way. Signed-off-by: KAMEZAWA Hiroyuki ...

Hi, This is a resend of this patch with more details. I'd like it can be accepted this time. The problem: In icmp_reply and ip_send_reply function, we now use rt->rt_src as destination to send out packets. For packets received in loopback device, this is wrong sometimes. Here is an example (NOTE: eth0 address is set to 10.10.10.1/24): #tcpdump -n -i lo icmp & [1] 3155 ... # hping3 --icmp --spoof 10.10.10.3 10.10.10.1 ... 09:53:49.508449 IP 10.10.10.3 > ...

Both these patches have built and booted for me. I will send a patch for the following error separately, in what will hopefully be canonical patch submission format, in case that's of any use. -- Joseph Fannin jfannin@gmail.com -

ops_complete_biofill tried to avoid calling handle_stripe since all the state necessary to return read completions is available. However the process of determining whether more read requests are pending requires locking the stripe (to block add_stripe_bio from updating dev->toead). ops_complete_biofill can run in tasklet context, so rather than upgrading all the stripe locks from spin_lock to spin_lock_bh this patch just moves read completion handling back into handle_stripe. Found-by: Yuri Tik...

Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- Documentation/crypto/async-tx-api.txt | 217 +++++++++++++++++++++++++++++++++ 1 files changed, 217 insertions(+), 0 deletions(-) diff --git a/Documentation/crypto/async-tx-api.txt b/Documentation/crypto/async-tx-api.txt new file mode 100644 index 0000000..48d685a --- /dev/null +++ b/Documentation/crypto/async-tx-api.txt @@ -0,0 +1,217 @@ + Asynchronous Transfers/Transforms API + +1 INTRODUCTION + +2 GENEALOGY + +3 USAG...

Hi, I am testing NFS on loopback locks up entire system with 2.6.23-rc6 kernel. I have mounted a local ext3 partition using loopback NFS (version 3) and started my test program. The test program forks 20 threads allocates 10MB for each thread, writes & reads a file on the loopback NFS mount. After running for about 5 min, I cannot even login to the machine. Commands like ps etc, hang in a live session. The machine is a DELL 1950 with 4Gig of RAM, so there is plenty of RAM & CPU to play...

Thanks Trond, for clarifying this for me. I have seen similar behavior when a remote NFS server is not available. Many processes wait end up waiting in nfs_release_page. So, what will happen if the remote server is not available, nfs_release_page cannot free the memory since it waits on rpc request to complete, which never completes and processes wait in there for ever? And unfortunately in my case, I cannot use "mount --bind". I want to use the same file system from two different nodes, and I w...

Stress testing revealed the need for (yet more) revision. sorry. This is a revision of Andrew's mspec-handle-shrinking-virtual-memory-areas.patch Version 4: clear/release fetchop pages only when vma_data is no longer shared The vma_data structure may be shared by vma's from multiple tasks, with no way of knowing which areas are shared or not shared, so release/clear pages only when the refcount (of vma's) goes to zero. Diffed against 2.6.23-rc7 Signed-off-by: Cliff Wickman <cpw@sgi.com...

PATCH 2.6.23-rc6-mm1 - Panic in blk_rq_map_sg() from CCISS driver New scatter/gather list chaining [sg_next()] treats 'page' member of struct scatterlist with low bit set [0x01] as a chain pointer to another struct scatterlist [array]. The CCISS driver request function passes an uninitialized, temporary, on-stack scatterlist array to blk_rq_map_sq(). sg_next() interprets random data on the stack as a chain pointer and eventually tries to de-reference an invalid pointer, resulting in: [<fff...

v2: rebasing on 2.6.23-rc6-mm1 Analyzing various data structures when NR_CPU count is raised to 4096 shows the following arrays over 128k. If the maximum number of cpus are not installed (about 99.99% of the time), then a large percentage of this memory is wasted. -- 151289856 CALNDATA irq_desc 135530496 RMDATATA irq_cfg 3145728 CALNDATA cpu_data 2101248 BSS irq_lists 2097152 RMDATATA cpu_sibling_map 2097152 RMDATATA cpu_core_map 1575936 BSS irq_2_pi...

Connect two machines with a serial cable. On the victim: willy@rowlf:~$ cat </dev/ttyS1 Now, let's find out which ttyS on the other machine is connected ... willy@teeth:~$ echo foo >/dev/ttyS1 -bash: echo: write error: Input/output error Oops, that's not a serial port. No output on rowlf, as expected. OK, carrying on ... willy@teeth:~$ echo bar >/dev/ttyS0 And yet on rowlf, we now see: foo bar Looks like there's an error path that doesn't throw away data on -EIO. T...

Thanks, Andreas. I tested it with /bin/echo instead of the built-in echo and the problem disappeared. Both machines were running bash 3.1.17(1)-release. "Not all bugs are kernel bugs" x10. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -

I just noticed that 2.6.23-rc6-mm1 is now available. I will rebase this patch on that version as there are some significant differences. -

Stress testing revealed the need for more revision. This is a revision of Andrew's mspec-handle-shrinking-virtual-memory-areas.patch Version 4: clear/release fetchop pages only when vma_data is no longer shared Version 3: single thread the clearing of vma_data maddr[] Version 2: refcount maintained as atomic_t (as before the version 1 patch) The shrinking of a virtual memory area that is mmap(2)'d to a memory special file (device drivers/char/mspec.c) can cause a panic. If the mapped size o...

Fixes from Alan, PCI IDs from ATI/AMD. Please pull from 'upstream-linus' branch of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git upstream-linus to receive the following updates: drivers/ata/ahci.c | 10 ++++++---- drivers/ata/libata-core.c | 4 ++++ drivers/ata/libata-sff.c | 5 ++++- 3 files changed, 14 insertions(+), 5 deletions(-) Alan Cox (2): libata: Update the blacklist with a few more devices libata-sff: Fix documentation henry ...

This is against 2.6.23-rc6. Compared to 2.6.23-rc6-mm1, there are a few (trivial) merge conflicts with the audit git tree, and one slightly more complicated one with ext2-reservations.patch. Changes from last post: - added several kerneldoc comments for exported functions - broke out the 'mnt' variable patch - removed WARN_ON() in ioctl patch The first four patches here are very simple cleanups, and can go in ahead of the rest of the patches. If you are reviewing this, the things that need ...

Originally from: Herbert Poetzl <herbert@13thfloor.at> This is the core of the read-only bind mount patch set. Note that this does _not_ add a "ro" option directly to the bind mount operation. If you require such a mount, you must first do the bind, then follow it up with a 'mount -o remount,ro' operation. Signed-off-by: Dave Hansen <haveblue@us.ibm.com> --- lxc-dave/fs/namespace.c | 46 ++++++++++++++++++++++++++++++++++------- lxc-dave/include/linux/mount.h | ...

Acked-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Dave Hansen <haveblue@us.ibm.com> --- lxc-dave/fs/namei.c | 4 ++++ lxc-dave/ipc/mqueue.c | 5 ++++- 2 files changed, 8 insertions(+), 1 deletion(-) diff -puN fs/namei.c~elevate-mnt-writers-for-vfs-unlink-callers fs/namei.c --- lxc/fs/namei.c~elevate-mnt-writers-for-vfs-unlink-callers 2007-09-20 12:16:21.000000000 -0700 +++ lxc-dave/fs/namei.c 2007-09-20 12:16:21.000000000 -0700 @@ -2228,7 +2228,11 @@ static...

This basically audits the callers of xattr_permission(), which calls permission() and can perform writes to the filesystem. This conflicts with the current (~2.6.23-rc7) audit git tree in -mm. wiggle'ing the patch merges it. Acked-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Dave Hansen <haveblue@us.ibm.com> --- lxc-dave/fs/nfsd/nfs4proc.c | 7 ++++++- lxc-dave/fs/xattr.c | 16 ++++++++++++++-- 2 files changed, 20 insertions(+), 3 deletions(-) diff...

Acked-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Dave Hansen <haveblue@us.ibm.com> --- lxc-dave/fs/inode.c | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff -puN fs/inode.c~elevate-write-count-for-do-sys-utime-and-touch-atime fs/inode.c --- lxc/fs/inode.c~elevate-write-count-for-do-sys-utime-and-touch-atime 2007-09-20 12:16:20.000000000 -0700 +++ lxc-dave/fs/inode.c 2007-09-20 12:16:20.000000000 -0700 @@ -1176,22 +1176,23 @@ void to...

Acked-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Dave Hansen <haveblue@us.ibm.com> --- lxc-dave/fs/open.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff -puN fs/open.c~elevate-writer-count-for-do-sys-truncate fs/open.c --- lxc/fs/open.c~elevate-writer-count-for-do-sys-truncate 2007-09-20 12:16:19.000000000 -0700 +++ lxc-dave/fs/open.c 2007-09-20 12:16:19.000000000 -0700 @@ -244,21 +244,21 @@ static long do_sys_truncate(const char _ i...

If we depend on the inodes for writeability, we will not catch the r/o mounts when implemented. This patches uses __mnt_want_write(). It does not guarantee that the mount will stay writeable after the check. But, this is OK for one of the checks because it is just for a printk(). The other two are probably unnecessary and duplicate existing checks in the VFS. This won't make them better checks than before, but it will make them detect r/o mounts. Acked-by: Christoph Hellwig <hch@infra...

This also uses the little helper in the NFS code to make an if() a little bit less ugly. We introduced the helper at the beginning of the series. Signed-off-by: Dave Hansen <haveblue@us.ibm.com> Acked-by: Christoph Hellwig <hch@infradead.org> --- lxc-dave/fs/namei.c | 4 ++++ lxc-dave/fs/nfsd/vfs.c | 15 +++++++++++---- 2 files changed, 15 insertions(+), 4 deletions(-) diff -puN fs/namei.c~elevate-write-count-over-calls-to-vfs-rename fs/namei.c --- lxc/fs/namei.c~elev...

Pretty self-explanatory. Fits in with the rest of the series. Signed-off-by: Dave Hansen <haveblue@us.ibm.com> Acked-by: Christoph Hellwig <hch@infradead.org> --- lxc-dave/fs/namei.c | 5 +++++ lxc-dave/fs/nfsd/nfs4recover.c | 4 ++++ 2 files changed, 9 insertions(+) diff -puN fs/namei.c~elevate-mnt-writers-for-callers-of-vfs-mkdir fs/namei.c --- lxc/fs/namei.c~elevate-mnt-writers-for-callers-of-vfs-mkdir 2007-09-20 12:16:14.000000000 -0700 +++ lxc-dave/fs/nam...

chown/chmod,etc... don't call permission in the same way that the normal "open for write" calls do. They still write to the filesystem, so bump the write count during these operations. This conflicts with the current (~2.6.23-rc7) audit git tree in -mm. wiggle'ing the patch merges it. Signed-off-by: Dave Hansen <haveblue@us.ibm.com> Acked-by: Christoph Hellwig <hch@infradead.org> --- lxc-dave/fs/open.c | 39 ++++++++++++++++++++++++++++++--------- 1 file changed, 30 inser...