Recent testing has turned up some bugs in the new Intel suspend/resume code for old, 8xx chipsets. So for 2.6.25 it probably makes sense to apply this patch, which should prevent the new code from getting called on those chipsets. We should have this fixed soon, but not in time for 2.6.25 unfortunately. Note that this patch (along with the suspend/resume code in general) could use more testing. Signed-off-by: Jesse Barnes <jesse.barnes@intel.com> diff --git a/drivers/char/drm/i915_...

Generally, we might not be able to handle memory unplugged at a wrong time (eg. after we've created the image). Which part of Kconfig says that exactly? Rafael --

ia32 XFS QA machine, ext3 root on a raw partition. 2.6.25-rc3. kjournald hung journal_commit_transaction(): Stack traceback for pid 2046 0xf6e0b350 2046 2 0 0 D 0xf6e0b550 kjournald esp eip Function (args) 0xf68d5e70 0xc04c20b2 schedule+0x51e 0xf68d5ec0 0xc04c2394 io_schedule+0x1d 0xf68d5ecc 0xc0179b64 sync_buffer+0x33 (invalid) 0xf68d5ed4 0xc04c2570 __wait_on_bit+0x36 (0xc2000b78, 0xf68d5f00, 0xc0179b31, 0x2) 0xf68d5ef0 0xc04c25ef out_of_line_wait_on_bit+0x58 (...

Hi, The following three patches are intended to start the redesign of the suspend and hibernation framework for devices. The first one is the 4th revision of the patch introducing new callbacks for suspend and hibernation. The other two patches implement the new suspend and hibernation callbacks for the platform and PCI bus types. Please review. Thanks, Rafael --

This is the 4th revision of the patch. The most important changes from the previous revision are: * The _noirq methods are executed with dpm_list_mtx held, so they are forbidden to unregister any device. This behavior has been introduced to prevent the problem in which, on a preemptible kernel, a thread concurrent to the suspend thread might be caught with dpm_list_mtx locked and in the process of modifying dpm_list when the suspend thread turns interrupts off. * Devices for which one of t...

I added the _noirq part to the names of the callbacks, since otherwise the second struct looks confusingly similar to the first one. I also could have put the _noirq callbacks into the first struct, but that would have been wasteful, since device types and device classes don't use them. Also, the majority of bus types won't use them and the vast majority of drivers won't use them as well. Thanks, Rafael --

OK Thanks, Rafael --

This cleans up the permission checks done for /proc/PID/mem i/o calls. It puts all the logic in a new function, check_mem_permission(). The old code repeated the (!MAY_PTRACE(task) || !ptrace_may_attach(task)) magical expression multiple times. The new function does all that work in one place, with clear comments. The old code called security_ptrace() twice on successful checks, once in MAY_PTRACE() and once in __ptrace_may_attach(). Now it's only called once, and only if all other checks have ...

Hi All, I am passing the bd_info structure from u-boot to bd_t (bd info) structure of the kernel. And within my platform_init, I am have the below line which assigns the u-boot parameter to the bd structure. Will this be enough .. memcpy(&bd, (bd_t *)r3, sizeof(bd)); Reason is, I am not seeing the same values that I am passing from the u-boot. Hence the question. Is there any kernel hacking that I need to set or any thing that I may need to be aware of? Appreciate your help. Th...

Applied to git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm -- James Morris <jmorris@namei.org> --

This set of five patches moves XPC and XPNET to drivers/misc/xp in preparation for enabling X86_64 support. I discovered that the previous versions of this patch were missing the replacement of kernel_thread() by kthread_run() and the elimination of daemonize(). --

Addressed issues raised by scripts/checkpatch.pl. Removed unnecessary curly braces. Eliminated uses of volatiles and use of kernel_thread() and daemonize(). Signed-off-by: Dean Nelson <dcn@sgi.com> --- There are still three false positives from checkpatch.pl concerning WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable. I've sent mail to the maintainers of checkpatch.pl. drivers/misc/xp/xp_main.c | 68 ++++------ drivers/misc/xp/xp_sn2.c | 23...

Prepared XPC and XPNET for future support of SGI's UV architecture. Made changes so it compiles on x86_64. Added support for up to 256 partitions. Cleaned up BTE error conversion for is64 sn2. Signed-off-by: Dean Nelson <dcn@sgi.com> --- arch/ia64/sn/kernel/setup.c | 4 drivers/misc/Kconfig | 2 drivers/misc/xp/Makefile | 5 drivers/misc/xp/xp.h | 382 ++++++++++---------- drivers/misc/xp/xp_main.c | 181 ++++++--- drivers/misc/xp/xp_n...

Enable the uncached allocator to allocate multiple pages of contiguous uncached memory. Signed-off-by: Dean Nelson <dcn@sgi.com> --- arch/ia64/kernel/uncached.c | 21 ++++++++++++--------- drivers/char/mspec.c | 12 ++++++------ include/asm-ia64/uncached.h | 4 ++-- 3 files changed, 20 insertions(+), 17 deletions(-) Index: linux-2.6/arch/ia64/kernel/uncached.c =================================================================== --- linux-2.6.orig/arch/ia64/kernel/unc...

Hi Ingo, This should be in 2.6.25 if possible. Thanks ! -- From: Florian Fainelli <florian.fainelli@telecomint.eu> Subject: [PATCH] [x86] rdc321x: GPIO routines bugfixes This patch fixes the use of GPIO routines which are in the PCI configuration space of the RDC321x, therefore reading/writing to this space without spinlock protection can be problematic. We also now request and free GPIOs and support the MGB100 board, previous code was very AR525W-centric. Signed-off-by: Volker Weiss...

Add a new function that accepts a pointer to the "newly allowed cpus" cpumask argument. int set_cpus_allowed_ptr(struct task_struct *p, const cpumask_t *new_mask) The current set_cpus_allowed() function is modified to use the above but this does not result in an ABI change. And with some compiler optimization help, it may not introduce any additional overhead. Additionally, to enforce the read only nature of the new_mask arg, the "const" property is migrated to sub-functions called by set_cpus...

Move the setting of nr_cpu_ids from sched_init() to start_kernel() so that it's available as early as possible. Note that an arch has the option of setting it even earlier if need be, but it should not result in a different value than the setup_nr_cpu_ids() function. Based on: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git Signed-off-by: Mike Travis <travis@sgi.com> --- init/main.c | 17 ++...

*Ugh* Why bother with vfsmount_lock here? All allocations are done under namespace_sem. Moreover, I'd rather replace that 'goto retry' with ... and I'd rather do that earlier, e.g. in umount_tree(). At that point we (a) have namespace_sem and (b) irrevocably kick the sucker out of any namespace. I'd rather minimize banging vfsmount_lock like that... --

Here's an updated mountinfo patch with the following changes relative to the last submission (the one currently in -mm): - in __d_path() don't add extra parameter for checking unreachable path - reduce proliferation of #ifdef CONFIG_PROC_FS into dcache.c and seq_file.c - make peer group ID allocation a separate pass from setting mount shared - change order and format of fields in /proc/<pid>/mountinfo - remove dubious cleanups - consolidate locking: don't use vfsmount_lock where namespa...

From: Miklos Szeredi <mszeredi@suse.cz> Show peer group ID of nearest dominating group that has intersection with the mount's namespace. Signed-off-by: Miklos Szeredi <mszeredi@suse.cz> --- Documentation/filesystems/proc.txt | 6 ++++ fs/namespace.c | 9 +++++-- fs/pnode.c | 45 +++++++++++++++++++++++++++++++++++++ fs/pnode.h | 1 4 files changed, 59 insertions(+), 2 deletions(-) Index: vfs-2.6/Docu...

From: Ram Pai <linuxram@us.ibm.com> [mszeredi@suse.cz] rewrite and split big patch into managable chunks /proc/mounts in its current form lacks important information: - propagation state - root of mount for bind mounts - the st_dev value used within the filesystem - identifier for each mount and it's parent It also suffers from the following problems: - not easily extendable - ambiguity of mountpoints within a chrooted environment - doesn't distinguish between filesystem dep...

From: Miklos Szeredi <mszeredi@suse.cz> Allow /proc/<pid>/mountinfo to use the root of <pid> to calculate mountpoints. - move definition of 'struct proc_mounts' to <linux/mnt_namespace.h> - add the process's namespace and root to this structure - pass a pointer to 'struct proc_mounts' into seq_operations In addition the following cleanups are made: - use a common open function for /proc/<pid>/{mounts,mountstat} - surround namespace.c part of these proc file...

Erm... What if that sucker has zero group ID to start with? You What is that renaming doing here? --

This patch set builds on Andi Kleen's patches for GB pages for hugetlb posted on March 16th. This set adds support for 16G huge pages on ppc64. Supporting multiple huge page sizes on ppc64 as defined in Andi's patches is not a part of this set; that will be included in a future patch. The first patch here adds an arch callback since the 16G pages are not allocated from bootmem. The 16G pages have to be reserved prior to boot-time. The location of these pages are indicated in the device tree. ...

The huge page size is setup for 16G pages if that size is specified at boot-time. The support for multiple huge page sizes is not being utilized yet. That will be in a future patch. Signed-off-by: Jon Tollefson <kniht@linux.vnet.ibm.com> --- hugetlbpage.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/mm/hugetlbpage.c b/arch/powerpc/mm/hugetlbpage.c index 44d3d55..b6a02b7 100644 --- a/arch/powerpc/mm/hugetlbpage.c +++ b/arch/powerp...