Re: Linux 2.6.17-rc2 - notifier chain problem?

[Keith Owens <kaos@sgi.com>]

Herbert Poetzl (on Fri, 21 Apr 2006 13:01:40 +0200) wrote:
>On Tue, Apr 18, 2006 at 08:27:37PM -0700, Linus Torvalds wrote:
>> 
>> Instead of the normal one-week release schedule, there was now two weeks 
>> between 2.6.17-rc1 and -rc2, partly because I was travelling for one of 
>> those weeks, but partly because it was really quiet for a while. Likely a 
>> lot of people are concentrating on 2.6.16 and vendor releases.
>
>[rest zapped]
>
>here is the 'updated' bug report on the xfs issue which
>seems to have been introduced with 2.6.17-rc1
>
>note: 2.6.16.8 does not have this issue
>
>best,
>Herbert
>
>
>Linux (none) 2.6.17-rc2 #1 SMP Fri Apr 21 11:52:19 CEST 2006 i686 unknown
>
>/ # mkfs.xfs -f /dev/hdc1
>meta-data=/dev/hdc1              isize=256    agcount=8, agsize=8189 blks
>data     =                       bsize=4096   blocks=65512, imaxpct=25
>         =                       sunit=0      swidth=0 blks, unwritten=0
>naming   =version 2              bsize=4096  
>log      =internal log           bsize=4096   blocks=1200
>realtime =none                   extsz=65536  blocks=0, rtextents=0
>/ # mount /dev/hdc1 /mnt/
>
>
>[   64.289157] BUG: unable to handle kernel paging request at virtual address c056a680
>[   64.290085]  printing eip:
>[   64.290402] c0129290
>[   64.290686] *pde = 005bd027
>[   64.291037] *pte = 0056a000
>[   64.291504] Oops: 0000 [#1]
>[   64.291823] SMP DEBUG_PAGEALLOC
>[   64.292820] Modules linked in:
>[   64.293453] CPU:    0
>[   64.293485] EIP:    0060:[<c0129290>]    Not tainted VLI
>[   64.293529] EFLAGS: 00000286   (2.6.17-rc2 #1) 
>[   64.295055] EIP is at notifier_chain_register+0x20/0x50
>[   64.295648] eax: c056a678   ebx: cf5e23f8   ecx: 00000000   edx: c04bea9c
>[   64.296362] esi: cf5e23f8   edi: cffc5000   ebp: cf5e2800   esp: cffdad5c
>[   64.297140] ds: 007b   es: 007b   ss: 0068
>[   64.297613] Process mount (pid: 34, threadinfo=cffda000 task=cff7e570)
>[   64.298258] Stack: <0>c04bea80 c0129454 c04bea9c cf5e23f8 cf5e2000 cf5e2000 c01367f7 c04bea80 
>[   64.299558]        cf5e23f8 c02d4b26 cf5e23f8 00000404 cf5e2000 cfd1f520 cffc5000 c02d1f53 
>[   64.300700]        cf5e2000 00000001 c02e65ef 00000424 00000001 cffc5000 cfd1f520 c02f2880 
>[   64.301841] Call Trace:
>[   64.302278]  <c0129454> blocking_notifier_chain_register+0x54/0x90   <c01367f7> register_cpu_notifier+0x17/0x20
>[   64.303684]  <c02d4b26> xfs_icsb_init_counters+0x46/0xb0   <c02d1f53> xfs_mount_init+0x23/0x160
>[   64.304844]  <c02e65ef> kmem_zalloc+0x1f/0x50   <c02f2880> bhv_insert_all_vfsops+0x10/0x50
>[   64.305940]  <c02f1f65> xfs_fs_fill_super+0x35/0x1f0   <c0313e97> snprintf+0x27/0x30
>[   64.307124]  <c01a24f4> disk_name+0x64/0xc0   <c0168f1f> sb_set_blocksize+0x1f/0x50
>[   64.308140]  <c0168869> get_sb_bdev+0x109/0x160   <c02f2150> xfs_fs_get_sb+0x30/0x40
>[   64.309129]  <c02f1f30> xfs_fs_fill_super+0x0/0x1f0   <c0168b10> do_kern_mount+0xa0/0x160
>[   64.310156]  <c0181187> do_new_mount+0x77/0xc0   <c018184f> do_mount+0x1bf/0x230
>[   64.311177]  <c03f4a68> iret_exc+0x3d4/0x6ab   <c0181633> copy_mount_options+0x63/0xc0
>[   64.312246]  <c03f427f> lock_kernel+0x2f/0x50   <c0181c5f> sys_mount+0x9f/0xe0
>[   64.313237]  <c0102b27> syscall_call+0x7/0xb  
>[   64.313917] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90 
>[   64.318371] EIP: [<c0129290>] notifier_chain_register+0x20/0x50 SS:ESP 0068:cffdad5c

Apply this debugging patch.  It uses KERN_EMERG instead of KERN_DEBUG
to ensure that the messages appear on the console.  Capture the boot
log, extract all the notify register and unregister messages.  Convert
the addresses of *nl and n to symbols[*] and mail the result to lkml.

[*] A quick way of converting text with possible addresses to symbols is
      ksymoops -m System.map -A `cat log.extract` < /dev/null
    ksymoops -A extracts anything that might be an address, looks it up
    in the system map and prints the corresponding symbol.


Index: linux/kernel/sys.c
===================================================================
--- linux.orig/kernel/sys.c	2006-04-19 17:33:07.000000000 +1000
+++ linux/kernel/sys.c	2006-04-22 16:28:19.593794509 +1000
@@ -105,6 +105,8 @@ static BLOCKING_NOTIFIER_HEAD(reboot_not
 static int notifier_chain_register(struct notifier_block **nl,
 		struct notifier_block *n)
 {
+	printk(KERN_EMERG "%s start *nl=%p n=%p\n",
+		__FUNCTION__, *nl, n);
 	while ((*nl) != NULL) {
 		if (n->priority > (*nl)->priority)
 			break;
@@ -112,19 +114,27 @@ static int notifier_chain_register(struc
 	}
 	n->next = *nl;
 	rcu_assign_pointer(*nl, n);
+	printk(KERN_EMERG "%s return *nl=%p n=%p\n",
+		__FUNCTION__, *nl, n);
 	return 0;
 }
 
 static int notifier_chain_unregister(struct notifier_block **nl,
 		struct notifier_block *n)
 {
+	printk(KERN_EMERG "%s start *nl=%p n=%p\n",
+		__FUNCTION__, *nl, n);
 	while ((*nl) != NULL) {
 		if ((*nl) == n) {
 			rcu_assign_pointer(*nl, n->next);
+			printk(KERN_EMERG "%s return 1 *nl=%p n=%p\n",
+				__FUNCTION__, *nl, n);
 			return 0;
 		}
 		nl = &((*nl)->next);
 	}
+	printk(KERN_EMERG "%s return 2 *nl=%p n=%p\n",
+		__FUNCTION__, *nl, n);
 	return -ENOENT;
 }
 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/