Hi, I back ported the CS5536 MFGPT based watchdog timer from Kernel 2.6 to Kernel 2.4 (I have to). I am using the Alix2c0 board with TinyBios v0.99. I have been following the discussion on this thread “Re: 2.6.24-rc8 hangs at mfgpt-timer". I disabled the MFGPT workaround in the BIOS and it seems to load the module just fine (no more hangs). I get this when I load geode-mfgpt.o: ################ Found vendor: 0x1022h, device: 0x2090h reading from: 6206 reading from: 620e reading from: 6216 read...

I think this pattern should be added to checkpatch Signed-off-by: Joe Perches <joe@perches.com> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index 579f50f..147e573 100755 --- a/scripts/checkpatch.pl +++ b/scripts/checkpatch.pl @@ -1337,6 +1337,11 @@ sub process { } } +# Check for bitwise tests written as boolean + if ($line =~ /\&\&\s*0[xX]/) { + WARN("boolean test with hexadecimal, perhaps just 1 \&?\n" . $herecurr); + } + # if and else sho...

Hi! I have Asus p5b-v motherboard with Intel ICH8R + JMicron 20360/20363. I am currently using zen-sources 2.6.24-rc7-zen2-g7c7e9c4a (zen-sources.org) based on kernel 2.6.24-rc7. I have also these sources directly with no solution to below problem (the mm-sources also don't help). I have ATA turned off completely and SCSI stuff (generic, disk, cdrom) compiled in. SATA for Intel ICH8, AHCI also compiled in. JMicron PATA as a module. I have SATA drive connected to SATA0 and Maxtor IDE drive ...

From: Pekka Enberg <penberg@cs.helsinki.fi> If the node we're booting on doesn't have memory, bootstrapping kmalloc() caches resorts to fallback_alloc() which requires ->nodelists set for all nodes. Fix that by calling set_up_list3s() for CACHE_CACHE in kmem_cache_init(). Tested-by: Mel Gorman <mel@csn.ul.ie> Reviewed-by: Christoph Lameter <clameter@sgi.com> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> --- Olaf, can you please test this against a clean git he...

Hi, I believe this work is very important especially in the context of virtual machines. I think it would be more useful though implemented in the context of the IO scheduler. Since we already support a notion of IO priority, it seems reasonable to add a notion of an IO cap. Regards, Anthony Liguori --

Hi, everyone. I have a question regarding to select system call's code. In do_select() function, after check each fd in the set, do_select() call cond_resched(). That line, according to my view, is to reduce the system freeze time when do the busy querying. But before the call, when entering into the big loop, do_select call set_current_state(TASK_INTERRUPTIBLE). Then, if the reschedule really taken up, the current process will not return unless it catch a signal, or one of already registered fd sen...

I could test it, but it'll have to wait until I get back from LCA in a couple of weeks time. David --

This reminds me of unoionfs - it also had this issue, but IIRC, it eventually got solved. (Should now display /union/exe rather than /lowerlevel/exe.) Unionfs developers should know more. --

From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> Subject: [PATCH] x86_64: remove struct cpu_model_info No one uses struct cpu_model_info on x86_64 now. Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> --- arch/x86/kernel/setup_64.c | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c index 2643a8f..eb722b0 100644 --- a/arch/x86/kernel/setup_64.c +++ b/arch/x86/kernel/setup_64.c @@ -88...

The right fix for cluster filesystem is to have a coherent maximum file size for the whole cluster. If that can't be done due to protocol reason we need to lock around i_size update and revoke access to the inode on the client that doesn't support it. Which of course would require a working revoke to start with.. --

Use KSYM_NAME_LEN instead of numeric value Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- Index: linux-2.6.git/arch/sh64/kernel/unwind.c =================================================================== --- linux-2.6.git.orig/arch/sh64/kernel/unwind.c 2008-01-21 19:35:06.000000000 +0300 +++ linux-2.6.git/arch/sh64/kernel/unwind.c 2008-01-23 19:16:41.000000000 +0300 @@ -46,7 +46,7 @@ static int lookup_prev_stack_frame(unsig struct pt_regs *regs) { const char *sym; ...

Use KSYM_NAME_LEN instead of numeric value Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- Index: linux-2.6.git/net/core/dev.c =================================================================== --- linux-2.6.git.orig/net/core/dev.c 2008-01-21 19:35:33.000000000 +0300 +++ linux-2.6.git/net/core/dev.c 2008-01-23 19:22:17.000000000 +0300 @@ -2599,7 +2599,7 @@ static void ptype_seq_decode(struct seq_ unsigned long offset = 0, symsize; const char *symname; char *modname; - cha...

Use KSYM_NAME_LEN instead of numeric value Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- Index: linux-2.6.git/arch/x86/kernel/traps_64.c =================================================================== --- linux-2.6.git.orig/arch/x86/kernel/traps_64.c 2008-01-23 19:18:27.000000000 +0300 +++ linux-2.6.git/arch/x86/kernel/traps_64.c 2008-01-23 19:19:05.000000000 +0300 @@ -105,7 +105,7 @@ void printk_address(unsigned long addres const char *symname; char *modname; char *d...

The patch series looks like a nice cleanup, except for a few things in I don't think there is. "tmp" is not being passed to kallsyms to be filled with a symbol name, but it's being used to hold a name written by the user to lookup an address. If the powerpc/xmon people feel that 63 characters is enough to hold a This one is completely out of the blue. Why "sizeof(tmpstr) / 2"? It would make more sense to use "sizeof(tmpstr) - 1", but either way it This also introduces a change in b...

Ah, now I understand your confusion: kallsyms_lookup_name doesn't fill the name. It searches the name and returns the address. It is the _caller_ that fills the name, not kallsyms_lookup_name. It is used for stuff like: "give me the address of function foo": I think that using KSYM_NAME_LEN would be a nice cleanup for xmon, but it is for the powerpc guys to decide if they want to do it. I just wanted to point the change in behavior so that it wouldn't go unnoticed. For all we know, the st...

This patch series does convert explicitly defined lengths of buffers being passed to kallsyms_lookup to KSYM_NAME_LEN - Cyrill - --

These patches add local caching for network filesystems such as NFS. The patches can roughly be broken down into a number of sets: (*) 01-keys-inc-payload.diff (*) 02-keys-search-keyring.diff (*) 03-keys-callout-blob.diff Three patches to the keyring code made to help the CIFS people. Included because of patches 05-08. (*) 04-keys-get-label.diff A patch to allow the security label of a key to be retrieved. Included because of patches 05-08. (*) 05-...

The attached patch makes it possible for the NFS filesystem to make use of the network filesystem local caching service (FS-Cache). To be able to use this, an updated mount program is required. This can be obtained from: http://people.redhat.com/steved/fscache/util-linux/ To mount an NFS filesystem to use caching, add an "fsc" option to the mount: mount warthog:/ /a -o fsc Signed-off-by: David Howells <dhowells@redhat.com> --- fs/nfs/Makefile | 1 fs/nfs/client....

Changes to the kernel configuration defintions and to the NFS mount options to allow the local caching support added by the previous patch to be enabled. Signed-off-by: David Howells <dhowells@redhat.com> --- fs/Kconfig | 8 ++++++++ fs/nfs/client.c | 2 ++ fs/nfs/internal.h | 1 + fs/nfs/super.c | 14 ++++++++++++++ 4 files changed, 25 insertions(+), 0 deletions(-) diff --git a/fs/Kconfig b/fs/Kconfig index e95b11c..39b1981 100644 --- a/fs/Kconfig +++ b/fs/...

Export a number of functions for CacheFiles's use. Signed-off-by: David Howells <dhowells@redhat.com> --- fs/super.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/fs/super.c b/fs/super.c index ceaf2e3..cd199ae 100644 --- a/fs/super.c +++ b/fs/super.c @@ -266,6 +266,7 @@ int fsync_super(struct super_block *sb) __fsync_super(sb); return sync_blockdev(sb->s_bdev); } +EXPORT_SYMBOL_GPL(fsync_super); /** * generic_shutdown_super - common helpe...

Add a function to install a monitor on the page lock waitqueue for a particular page, thus allowing the page being unlocked to be detected. This is used by CacheFiles to detect read completion on a page in the backing filesystem so that it can then copy the data to the waiting netfs page. Signed-off-by: David Howells <dhowells@redhat.com> --- include/linux/pagemap.h | 5 +++++ mm/filemap.c | 18 ++++++++++++++++++ 2 files changed, 23 insertions(+), 0 deletions(-) di...

The attached patch adds a generic intermediary (FS-Cache) by which filesystems may call on local caching capabilities, and by which local caching backends may make caches available: +---------+ | | +--------------+ | NFS |--+ | | | | | +-->| CacheFS | +---------+ | +----------+ | | /dev/hda5 | | | | | +--------------+ +---------+ +-->| | | ...

This one-line patch fixes the missing export of copy_page introduced by the cachefile patches. This patch is not yet upstream, but is required for cachefile on ia64. It will be pushed upstream when cachefile goes upstream. Signed-off-by: Prarit Bhargava <prarit@redhat.com> Signed-off-by: David Howells <dhowells@redhat.com> --- arch/ia64/kernel/ia64_ksyms.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/ia64/kernel/ia64_ksyms.c b/arch/ia64/kernel/...

Recruit a couple of page flags to aid in cache management. The following extra flags are defined: (1) PG_fscache (PG_private_2) The marked page is backed by a local cache and is pinning resources in the cache driver. (2) PG_fscache_write (PG_owner_priv_2) The marked page is being written to the local cache. The page may not be modified whilst this is in progress. If PG_fscache is set, then things that checked for PG_private will now also check for that. This inclu...

Make NFSD work with detached security, using the patches that excise the security information from task_struct to struct task_security as a base. Each time NFSD wants a new security descriptor (to do NFS4 recovery or just to do NFS operations), a task_security record is derived from NFSD's *objective* security, modified and then applied as the *subjective* security. This means (a) the changes are not visible to anyone looking at NFSD through /proc, (b) there is no leakage between two consecutive op...