Date: Mon, 26 Jun 2006 08:15:35 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= <V.Haisman@sh.cvut.cz> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: LOR in vnode interlock and system map Message-ID: <449F7B87.1070907@sh.cvut.cz> In-Reply-To: <20060626041747.GH79678@deviant.kiev.zoral.com.ua> References: <447A1F94.7020809@sh.cvut.cz> <449F2790.80700@sh.cvut.cz> <20060626041747.GH79678@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Kostik Belousov wrote, On 26.6.2006 6:17: > On Mon, Jun 26, 2006 at 02:17:20AM +0200, V??clav Haisman wrote: >> >> V??clav Haisman wrote, On 29.5.2006 0:09: >>> See attached file. The kernel is todays CVS 6.1. >>> >>> -- >>> Vaclav Haisman >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> May 28 19:16:55 logout kernel: lock order reversal: >>> May 28 19:16:55 logout kernel: 1st 0xc3d4bb1c vnode interlock (vnode interlock) @ /usr/src/sys/kern/vfs_subr.c:2218 >>> May 28 19:16:55 logout kernel: 2nd 0xc1043144 system map (system map) @ /usr/src/sys/vm/vm_kern.c:295 >>> May 28 19:16:55 logout kernel: KDB: stack backtrace: >>> May 28 19:16:55 logout kernel: kdb_backtrace(c081a0c7,c1043144,c0819bfa,c0819bfa,c082f5af) at kdb_backtrace+0x2e >>> May 28 19:16:55 logout kernel: witness_checkorder(c1043144,9,c082f5af,127,c08bdbc0) at witness_checkorder+0x5ef >>> May 28 19:16:55 logout kernel: _mtx_lock_flags(c1043144,0,c082f5af,127,c104e460) at _mtx_lock_flags+0x32 >>> May 28 19:16:55 logout kernel: _vm_map_lock(c10430c0,c082f5af,127,c3375900,c3375900) at _vm_map_lock+0x37 >>> May 28 19:16:55 logout kernel: kmem_malloc(c10430c0,1000,101,d5688afc,c0766493) at kmem_malloc+0x3a >>> May 28 19:16:55 logout kernel: page_alloc(c104d300,1000,d5688aef,101,c05e0ed6) at page_alloc+0x27 >>> May 28 19:16:55 logout kernel: slab_zalloc(c104d300,101,c082ed67,8a2,80246) at slab_zalloc+0xd3 >>> May 28 19:16:55 logout kernel: uma_zone_slab(c104d300,1,c082ed67,8a2,c082ed67) at uma_zone_slab+0x112 >>> May 28 19:16:55 logout kernel: uma_zalloc_internal(c104d300,0,1,0,d5688b94) at uma_zalloc_internal+0x41 >>> May 28 19:16:55 logout kernel: bucket_alloc(80,1,c082ed67,95e,105) at bucket_alloc+0x3b >>> May 28 19:16:55 logout kernel: uma_zfree_arg(c104dc00,c389712c,0,d5688bbc,c072e964) at uma_zfree_arg+0x253 >>> May 28 19:16:55 logout kernel: mac_labelzone_free(c389712c) at mac_labelzone_free+0x22 >>> May 28 19:16:55 logout kernel: mac_vnode_label_free(c389712c,c3d4baa0,d5688be8,c061aa00,c3d4baa0) at mac_vnode_label_free+0x94 >>> May 28 19:16:55 logout kernel: mac_destroy_vnode(c3d4baa0,0,c081e172,30a,c3d4baa0) at mac_destroy_vnode+0x18 >>> May 28 19:16:55 logout kernel: vdestroy(c3d4baa0,d5688c1c,0,c3d4e9cc,c3d4e9cc) at vdestroy+0x60 >>> May 28 19:16:55 logout kernel: vdropl(c3d4baa0,d5688c1c,c081e172,835,c08b1440) at vdropl+0x50 >>> May 28 19:16:55 logout kernel: vput(c3d4baa0,0,c082c8a2,df7,c09117a0) at vput+0x1ae >>> May 28 19:16:55 logout kernel: handle_workitem_remove(c36de9e0,0,2,3b3,1) at handle_workitem_remove+0x15a >>> May 28 19:16:55 logout kernel: process_worklist_item(c35a0400,0,c082c8a2,348,4479db07) at process_worklist_item+0x1e1 >>> May 28 19:16:55 logout kernel: softdep_process_worklist(c35a0400,0,c082c8a2,2f2,3e8) at softdep_process_worklist+0x73 >>> May 28 19:16:55 logout kernel: softdep_flush(0,d5688d38,c08150d4,31d,0) at softdep_flush+0x193 >>> May 28 19:16:55 logout kernel: fork_exit(c0744170,0,d5688d38) at fork_exit+0x78 >>> May 28 19:16:55 logout kernel: fork_trampoline() at fork_trampoline+0x8 >>> May 28 19:16:55 logout kernel: --- trap 0x1, eip = 0, esp = 0xd5688d6c, ebp = 0 --- >> One more data point for this LOR. It happens only once early (with >> minutes or hours) after reboot and then never again. >> >> -- >> Vaclav Haisman >> > > Try manually MFC rev. 1.637 of sys/kern/vfs_subr.c. > Please, report the results (at least to me). I have never done it manual patching before. Do you mean this <http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_subr.c.diff?r1=1.636&r2=1.637>; patch? -- Vaclav Haisman [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRJ97jm56zbtzMDG0AQKS7gf8DKjgquNsK5FtRICcQDXccPC6agmPkxHe ClH6A/5DBX0xnSIlFrzFLFfoUhiaVm+lZbar3zgZlmIhGpO3XW0Tjj5Qa9kUcoNU 2ncqLwgwJiW4bmQn3BQhO47lQEHnR9HyGDO/XEpw/BfwmSHg9lYldXdDXo2gLczA O/i+jD1lqAt8gSMSo05tWSc2sz5+PNc5+JhVvWqxtX/Y0UpG54+GkQOgpLrkEzmU dQkykGtxbEj3zaNGevQAkSsJIFdvSQL0au0JFSpg9TVu8LFCL+9/sRuLf/CibdiP 2r/VYA2opcB0LTY6bZYnnYpeqGbdYLk5FQWsPRo5wJDKPNOAuOFwtA== =bluf -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?449F7B87.1070907>