Date: Tue, 6 Sep 2005 18:19:10 +0200 (CEST) From: Harald Schmalzbauer <harry@schmalzbauer.de> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/85804: panic after chown -R from chrooted shell Message-ID: <200509061619.j86GJAwn011659@cale.flintsbach.schmalzbauer.de> Resent-Message-ID: <200509061620.j86GKIoA026688@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 85804 >Category: kern >Synopsis: panic after chown -R from chrooted shell >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 06 16:20:17 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Harald Schmalzbauer >Release: FreeBSD 6.0-BETA4 i386 >Organization: >Environment: System: FreeBSD cale.flintsbach.schmalzbauer.de 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Mon Sep 5 19:47:14 UTC 2005 harry@cale.flintsbach.schmalzbauer.de:/usr/obj/usr/src/sys/CALE i386 Maybe uncommon mount points: /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ufs/usr on /usr (ufs, NFS exported, local, soft-updates) /dev/ufs/compat on /compat (ufs, local, soft-updates) /dev/ufs/var on /var (ufs, local, soft-updates) /dev/ufs/tmp on /tmp (ufs, local, soft-updates) gune:/home on /home (nfs) /dev/ufs/builder on /builder (ufs, local, soft-updates) /dev/ufs/src on /builder/usr/src (ufs, local, soft-updates) /dev/ufs/obj on /builder/usr/obj (ufs, local, soft-updates) devfs on /builder/dev (devfs, local) Exemplary glabel list output: Geom name: ad0s2p8 Providers: 1. Name: ufs/builder Mediasize: 786432000 (750M) Sectorsize: 512 Mode: r1w1e1 secoffset: 0 offset: 0 seclength: 1536000 length: 786432000 index: 0 Consumers: 1. Name: ad0s2p8 Mediasize: 786432000 (750M) Sectorsize: 512 Mode: r1w1e2 So as you can see I use GPT inside slices and UFS labels w/ glabel! >Description: This is very hard to reproduce but I had a panic the second time after I chown'd the user of files from a chrooted jail. Directory of the chroot was /builder, command was 'chroot -R harry /usr/obj/stith6' Like mentioned, I already saw this panic with 6.0-BETA Here's all I got from a serial console: panic: handle_workitem_remove: bad file delta KDB: enter: panic [thread pid 54 tid 100059 ] Stopped at kdb_enter+0x30: leave db> where Tracing pid 54 tid 100059 td 0xc1e75780 kdb_enter(c0791b35,c0801560,c07a421e,d58b2c3c,100) at kdb_enter+0x30 panic(c07a421e,11970,0,d58b2c50,3b7) at panic+0xd5 handle_workitem_remove(c2d81de0,0,2,32e,0) at handle_workitem_remove+0x107 process_worklist_item(0,0,c07a39e1,2de,431db271) at process_worklist_item+0x20b softdep_process_worklist(0,0,c079a93a,678,0) at softdep_process_worklist+0x130 sched_sync(0,d58b2d38,c078ef39,30d,0) at sched_sync+0x2ee fork_exit(c06078c0,0,d58b2d38) at fork_exit+0xc1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd58b2d6c, ebp = 0 --- db> >How-To-Repeat: Don't know, just redoing a chown from a chrooted shell after reboot doesn't lead to the panic, seems the machine must be some days up.... >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509061619.j86GJAwn011659>