lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <87skhf8b48.wl%chamas@h4.dion.ne.jp>
Date:	Thu, 02 Jul 2009 22:31:35 +0900
From:	Ken-ichirou MATSUZAWA <chamas@...dion.ne.jp>
To:	netdev@...r.kernel.org
Subject: kernel BUG at fs/sysfs/group.c:65!

 Hello,

I could not create bridge in container created by lxc-exec. This relys
on bridge's sysfs or kobject creation, I thought it can be avoided by
comparing dev_net(dev) and &init_net before touching sysfs.

This seemed works fine, but exit or lxc-stop before deleting bridge

	WARNING: at kernel/sysctl.c:2046 unregister_sysctl_table+0xa9/0x110()
or
	kernel: unregister_netdevice: waiting for lo to become free. Usage count = 2

It's hard for me to avoid those. Could someone help me?

Thanks,

Jun 30 22:32:13 toptor kernel: ------------[ cut here ]------------
Jun 30 22:32:13 toptor kernel: kernel BUG at fs/sysfs/group.c:65!
Jun 30 22:32:13 toptor kernel: invalid opcode: 0000 [#1] PREEMPT SMP
Jun 30 22:32:13 toptor kernel: last sysfs file: /sys/devices/virtual/net/lo/operstate
Jun 30 22:32:13 toptor kernel: CPU 0
Jun 30 22:32:13 toptor kernel: Modules linked in: veth nfsd exportfs ctr twofish twofish_common camellia serpent blowfish xcbc rmd160 sha256\
_generic crypto_null dm_crypt dm_snapshot dm_mirror dm_region_hash dm_log dm_mod rt2500usb rt2x00usb rt2x00lib input_polldev ide_cd_mod ehci\
_hcd cdrom amd_rng rng_core uhci_hcd ohci_hcd usbcore floppy
Jun 30 22:32:13 toptor kernel: Pid: 12568, comm: brctl Not tainted 2.6.30 #1 To be filled by O.E.M.
Jun 30 22:32:13 toptor kernel: RIP: 0010:[<ffffffff8113ddfe>]  [<ffffffff8113ddfe>] internal_create_group+0x11e/0x1b0
Jun 30 22:32:13 toptor kernel: RSP: 0018:ffff8800134c9d18  EFLAGS: 00010246
Jun 30 22:32:13 toptor kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Jun 30 22:32:13 toptor kernel: RDX: ffffffff816454c0 RSI: 0000000000000000 RDI: ffff88003ddfe3c0
Jun 30 22:32:13 toptor kernel: RBP: ffff8800134c9d68 R08: 0000000000000000 R09: 0000000000000000
Jun 30 22:32:13 toptor kernel: R10: ffffffff81487f5b R11: 0000000000000000 R12: ffff88003ddfe000
Jun 30 22:32:13 toptor kernel: R13: ffff88003ddfe3c0 R14: ffff880024515280 R15: ffff88003ddfe3c0
Jun 30 22:32:13 toptor kernel: FS:  00007f3a38e356e0(0000) GS:ffff8800017ce000(0000) knlGS:0000000000000000
Jun 30 22:32:13 toptor kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jun 30 22:32:13 toptor kernel: CR2: 00007f3a389a6270 CR3: 0000000027981000 CR4: 00000000000006e0
Jun 30 22:32:13 toptor kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 30 22:32:13 toptor kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jun 30 22:32:13 toptor kernel: Process brctl (pid: 12568, threadinfo ffff8800134c8000, task ffff880036984830)
Jun 30 22:32:13 toptor kernel: Stack:
Jun 30 22:32:13 toptor kernel:  ffff88003ddfe000 ffffffff816454c0 00000000134c9d68 ffffffff8148b23f
Jun 30 22:32:13 toptor kernel:  ffff8800134c9d58 0000000000000000 ffff88003ddfe000 ffff88003ddfe3c0
Jun 30 22:32:13 toptor kernel:  ffff880024515280 ffff8800134c9e08 ffff8800134c9d78 ffffffff8113dec3
Jun 30 22:32:13 toptor kernel: Call Trace:
Jun 30 22:32:13 toptor kernel:  [<ffffffff8148b23f>] ? notifier_call_chain+0x3f/0x80
Jun 30 22:32:13 toptor kernel:  [<ffffffff8113dec3>] sysfs_create_group+0x13/0x20
Jun 30 22:32:13 toptor kernel:  [<ffffffff814218d2>] br_sysfs_addbr+0x32/0x100
Jun 30 22:32:13 toptor kernel:  [<ffffffff8141d520>] br_addbridge+0x1b0/0x1d0
Jun 30 22:32:13 toptor kernel:  [<ffffffff8141e32d>] br_ioctl_deviceless_stub+0x22d/0x250
Jun 30 22:32:13 toptor kernel:  [<ffffffff813142c2>] sock_ioctl+0xf2/0x290
Jun 30 22:32:13 toptor kernel:  [<ffffffff810f0c96>] vfs_ioctl+0x36/0xb0
Jun 30 22:32:13 toptor kernel:  [<ffffffff810f0da0>] do_vfs_ioctl+0x90/0x560
Jun 30 22:32:13 toptor kernel:  [<ffffffff811da6a1>] ? __up_read+0x91/0xb0
Jun 30 22:32:13 toptor kernel:  [<ffffffff8105c5ae>] ? up_read+0xe/0x10
Jun 30 22:32:13 toptor kernel:  [<ffffffff810f1309>] sys_ioctl+0x99/0xa0
Jun 30 22:32:13 toptor kernel:  [<ffffffff8148860c>] ? _spin_lock_irqsave+0x2c/0x50
Jun 30 22:32:13 toptor kernel:  [<ffffffff8100c0db>] system_call_fastpath+0x16/0x1b
Jun 30 22:32:13 toptor kernel: Code: c0 74 2c 41 ff c6 8b 55 c4 85 d2 74 b0 48 8b 30 4c 89 e7 e8 25 c1 ff ff eb a3 48 83 7f 30 00 66 0f 1f 4\
4 00 00 0f 85 24 ff ff ff <0f> 0b eb fe 4c 8b 65 d0 45 31 ed 4d 85 e4 74 14 f0 41 ff 0c 24
Jun 30 22:32:13 toptor kernel: RIP  [<ffffffff8113ddfe>] internal_create_group+0x11e/0x1b0
Jun 30 22:32:13 toptor kernel:  RSP <ffff8800134c9d18>
Jun 30 22:32:13 toptor kernel: ---[ end trace 6c904257cc01c1b6 ]---
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ