On Wed, Aug 20, 2008 at 10:09:08PM +0900, [EMAIL PROTECTED] wrote:
>
> Hello Louis,
>
> Louis Rilling:
> > I observed a similar bug (BUG_ON in i_op.c:236) without vserver-patch. My s=
> > etup
> > was debian kernel 2.6.22-3-amd64 + aufs 20080804. aufs 20080728 was ok.
> >
> > I don't observe this anymore with debian kernel 2.6.25-2-amd64 + aufs 20080=
> > 818 +
> > (security_inode_permission() calls disabled because I did not want to compi=
> > le my
> > own kernel).
>
> It is an unknown problem for me.
> I understand that you have no such problem anymore, but if you know
> surely reproducible way, please let me know.
The problem is still there with debian kernel 2.6.22-3-amd64 + aufs 20080818.
Note that it disappears with kernel 2.6.25.
I setup aufs like this:
# /sbin/mke2fs -q -m 0 /dev/ram14
# /bin/mount /dev/ram14 /srv/.nfsroot64-scratch
# /bin/mount -t aufs -o
noplink,br:/srv/.nfsroot64-scratch=rw,br:/srv/.nfsroot64-base=ro none
/srv/nfsroot64
Relevant parts of /proc/mounts:
/dev/ram14 /srv/.nfsroot64-scratch ext2 rw 0 0
/dev/sda10 /srv ext3 rw,data=ordered 0 0
none /srv/nfsroot64 aufs
rw,si=ffff810037ec7c00,xino=/srv/.nfsroot64-scratch/.aufs.xino,noplink,br:/srv/.nfsroot64-scratch=rw:/srv/.nfsroot64-base=ro
0 0
Here is the result of Alt+SysRq+A:
SysRq : Aufs
si=ffff810037ec7c00
aufs: superblock
s-1: {perm 0x0, cnt 0}, aufs, flags 0x40000c00, cnt(BIAS) 0, active 1, xino 0
dev 0x14
s0: {perm 0x0, cnt 0}, ext2, flags 0x40000000, cnt(BIAS) 0, active 1, xino 1
s1: {perm 0x1, cnt 0}, ext3, flags 0x40000000, cnt(BIAS) 0, active 20, xino 1
aufs: root dentry
d-1: ///, aufs, cnt 3, flags 0x10, intent 0
i-1: i2, aufs, cnt 1, nl 23, 040755, ntfy 0, sz 1024, blk 2, ct 8192, np 0, st
0x0, f 0x0, g 0
d-1: bstart 0, bend 1, bwh -1, bdiropq -1, gen 0
d0: ///, ext2, cnt 8, flags 0x10, intent 0
i0: i2, ext2, cnt 2, nl 3, 040755, ntfy 0, sz 1024, blk 2, ct 8192, np 1, st
0x0, f 0x0, g 0
d1: //.nfsroot64-base, ext3, cnt 3, flags 0x0, intent 0
i1: i667809, ext3, cnt 2, nl 22, 040755, ntfy 0, sz 4096, blk 8, ct 23040, np
0, st 0x0, f 0x0, g 8f3e6903
aufs: isolated inode
As in the vserver case, simply doing 'cd /srv/nfsroot64' triggers the bug:
------------[ cut here ]------------
kernel BUG at /home/louis/aufs/fs/aufs/i_op.c:236!
invalid opcode: 0000 [3] SMP
CPU 1
Modules linked in: netconsole aufs ext2 nfs ipv6 nfsd exportfs lockd nfs_acl
sunrpc button ac battery dm_snapshot dm_mirror dm_mod loop snd_hda_intel
snd_pcm snd_timer snd soundcore parport_pc i2c_i801 intel_agp sg serio_raw
snd_page_alloc iTCO_wdt parport i2c_core sr_mod psmouse evdev pcspkr cdrom ext3
jbd mbcache sd_mod ata_generic usbhid hid piix ahci ehci_hcd libata scsi_mod
generic ide_core tg3 r8169 uhci_hcd thermal processor fan
Pid: 2610, comm: bash Not tainted 2.6.22-3-amd64 #1
RIP: 0010:[<ffffffff883ada69>] [<ffffffff883ada69>]
:aufs:aufs_permission+0x4a8/0x633
RSP: 0018:ffff81007a65ddf8 EFLAGS: 00010286
RAX: 0000000000004000 RBX: ffff810079e93c28 RCX: 000000000073db49
RDX: 0000000000000000 RSI: 0000000000000296 RDI: ffff8100790a9ce8
RBP: 0000000000000000 R08: ffffffff8028b316 R09: ffff810079c9c005
R10: 0000000000000007 R11: ffffffff802d2a2a R12: ffff8100790a9c00
R13: ffff8100790a9ce8 R14: 0000000000000000 R15: ffff81007a65ded8
FS: 00002b65f0c71af0(0000) GS:ffff81000115ecc0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002b65f051071d CR3: 000000007ab05000 CR4: 00000000000006e0
Process bash (pid: 2610, threadinfo ffff81007a65c000, task ffff81007d093630)
Stack: 00007fffba5b5c90 00007fffba5b5c40 000000000f3938cf 00007fffba5b5c58
00002b65f05109c0 ffffffff803f396d 01002b6500000001 ffff810037bfb400
0000000037c78780 0000000000008784 ffff81007a65ded8 0000000000000803
Call Trace:
[<ffffffff803f396d>] error_exit+0x0/0x84
[<ffffffff8028a0a1>] permission+0xaf/0xf7
[<ffffffff802829f7>] sys_chdir+0x29/0x62
[<ffffffff802861f9>] sys_newstat+0x28/0x31
[<ffffffff803f396d>] error_exit+0x0/0x84
[<ffffffff80209d8e>] system_call+0x7e/0x83
Code: 0f 0b eb fe 48 8b 7c 24 38 41 0f be f4 e8 71 f5 fd ff 8b 74
RIP [<ffffffff883ada69>] :aufs:aufs_permission+0x4a8/0x633
RSP <ffff81007a65ddf8>
The aufs mount is meant to be exported by NFS, but the bug actually triggers
without even attempting to export it. Exporting it fails.
Thanks,
Louis
--
Dr Louis Rilling Kerlabs
Skype: louis.rilling Batiment Germanium
Phone: (+33|0) 6 80 89 08 23 80 avenue des Buttes de Coesmes
http://www.kerlabs.com/ 35700 Rennes
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
