Date: Wed, 6 Jul 2016 21:08:44 +0000 (UTC) From: Giorgio Lago via LinkedIn <convites@linkedin.com> To: <freebsd-stable@freebsd.org> Subject: =?UTF-8?Q?O_convite_de_Giorgio_Lago_est=C3=A1_aguardando_sua_resposta?= Message-ID: <1009064032.2811332.1467839324186.JavaMail.app@lva1-app4794.prod.linkedin.com>
next in thread | raw e-mail | index | archive | help
Giorgio Lago would like to connect on LinkedIn. How would you like to respo= nd? Accept: https://www.linkedin.com/e/v2?e=3D-hwzlvm-iqb4171m-ge&t=3Dssuw&ek= =3Dsecond_guest_reminder_01&li=3D13&m=3Dhero&ts=3Daccept_text&sharedKey=3Dd= lXI--ld&invitationId=3D6151415342305464320 View Giorgio Lago's profile: https://www.linkedin.com/e/v2?e=3D-hwzlvm-= iqb4171m-ge&t=3Dssuw&ek=3Dsecond_guest_reminder_01&li=3D3&m=3Dhero&ts=3Dpro= file_text&sharedKey=3DdlXI--ld&invitationId=3D6151415342305464320 Eu gostaria de adicion=C3=A1-lo =C3=A0 minha rede profissional no LinkedIn. -Giorgio Voc=C3=AA recebeu um convite para se conectar. O LinkedIn utiliza seu ender= e=C3=A7o de e-mail para fazer sugest=C3=B5es a nossos usu=C3=A1rios em recu= rsos como Pessoas que talvez voc=C3=AA conhe=C3=A7a. Cancelar inscri=C3=A7= =C3=A3o: https://www.linkedin.com/e/v2?e=3D-hwzlvm-iqb4171m-ge&t=3Dlun&midT= oken=3DAQFmrFVhGEd36Q&ek=3Dsecond_guest_reminder_01&li=3D15&m=3Dunsub&ts=3D= HTML&eid=3D-hwzlvm-iqb4171m-ge&loid=3DAQEBxxkC5Zj2AgAAAVXCCp_8QtS1iDRa0yUyQ= RztSvf98jhLoL-W3mo31rM3KJ1C7LIvMyA9BzfdJHx5upnkYC8A Este e-mail foi enviado para freebsd-stable@freebsd.org. If you need assistance or have questions, please contact LinkedIn Customer = Service: https://www.linkedin.com/e/v2?e=3D-hwzlvm-iqb4171m-ge&a=3Dcustomer= ServiceUrl&ek=3Dsecond_guest_reminder_01 © 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View, CA 94= 043. LinkedIn e a logomarca do LinkedIn s=C3=A3o marcas registradas da Link= edIn. From owner-freebsd-stable@freebsd.org Thu Jul 7 00:12:29 2016 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4B63B758D1; Thu, 7 Jul 2016 00:12:29 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 857D5126D; Thu, 7 Jul 2016 00:12:29 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u670CLT1011655 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 7 Jul 2016 03:12:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u670CLT1011655 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u670CIZE011654; Thu, 7 Jul 2016 03:12:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 7 Jul 2016 03:12:18 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: David Cross <dcrosstech@gmail.com> Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Reproducable panic in FFS with softupdates and no journaling (10.3-RELEASE-pLATEST) Message-ID: <20160707001218.GI38613@kib.kiev.ua> References: <CAM9edeOek_zqRPt-0vDMNMK9CH31yAeVPAirWVvcuUWy5xsm4A@mail.gmail.com> <CAM9edeN1Npc=cNth2gAk1XFLvar-jZqzxWX50pLQVxDusMrOVg@mail.gmail.com> <20160706151822.GC38613@kib.kiev.ua> <CAM9edeMDdjO6C2BRXBxDV-trUG5A0NEua+K0H_wERq7H4AR72g@mail.gmail.com> <CAM9edePfMxm26yYC=o10CGhRSDUHXTTNosFc_T89v4Pxt0JM0g@mail.gmail.com> <20160706173758.GF38613@kib.kiev.ua> <CAM9edeOb0yUqaXbTMGBJVFqgJ++yaDr4tGV1TQ_UPOYmv4p2fw@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <CAM9edeOb0yUqaXbTMGBJVFqgJ++yaDr4tGV1TQ_UPOYmv4p2fw@mail.gmail.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 07 Jul 2016 00:12:30 -0000 On Wed, Jul 06, 2016 at 02:21:20PM -0400, David Cross wrote: > (kgdb) up 5 > #5 0xffffffff804aafa1 in brelse (bp=0xfffffe00f77457d0) at buf.h:428 > 428 (*bioops.io_deallocate)(bp); > Current language: auto; currently minimal > (kgdb) p/x *(struct buf *)0xfffffe00f77457d0 > $1 = {b_bufobj = 0xfffff80002e88480, b_bcount = 0x4000, b_caller1 = 0x0, > b_data = 0xfffffe00f857b000, b_error = 0x0, b_iocmd = 0x0, b_ioflags = > 0x0, > b_iooffset = 0x0, b_resid = 0x0, b_iodone = 0x0, b_blkno = 0x115d6400, > b_offset = 0x0, b_bobufs = {tqe_next = 0x0, tqe_prev = > 0xfffff80002e884d0}, > b_vflags = 0x0, b_freelist = {tqe_next = 0xfffffe00f7745a28, > tqe_prev = 0xffffffff80c2afc0}, b_qindex = 0x0, b_flags = 0x20402800, > b_xflags = 0x2, b_lock = {lock_object = {lo_name = 0xffffffff8075030b, > lo_flags = 0x6730000, lo_data = 0x0, lo_witness = > 0xfffffe0000602f00}, > lk_lock = 0xfffff800022e8000, lk_exslpfail = 0x0, lk_timo = 0x0, > lk_pri = 0x60}, b_bufsize = 0x4000, b_runningbufspace = 0x0, > b_kvabase = 0xfffffe00f857b000, b_kvaalloc = 0x0, b_kvasize = 0x4000, > b_lblkno = 0x0, b_vp = 0xfffff80002e883b0, b_dirtyoff = 0x0, > b_dirtyend = 0x0, b_rcred = 0x0, b_wcred = 0x0, b_saveaddr = 0x0, b_pager > = { > pg_reqpage = 0x0}, b_cluster = {cluster_head = {tqh_first = 0x0, > tqh_last = 0x0}, cluster_entry = {tqe_next = 0x0, tqe_prev = 0x0}}, > b_pages = {0xfffff800b99b30b0, 0xfffff800b99b3118, 0xfffff800b99b3180, > 0xfffff800b99b31e8, 0x0 <repeats 28 times>}, b_npages = 0x4, b_dep = { > lh_first = 0xfffff800023d8c00}, b_fsprivate1 = 0x0, b_fsprivate2 = 0x0, > b_fsprivate3 = 0x0, b_pin_count = 0x0} > > > This is the freshly allocated buf that causes the panic; is this what is > needed? I "know" which vnode will cause the panic on vnlru cleanup, but I > don't know how to walk the memory list without a 'hook'.. as in, i can > setup the kernel in a state that I know will panic when the vnode is > cleaned up, I can force a panic 'early' (kill -9 1), and then I could get > that vnode.. if I could get the vnode list to walk. Was the state printed after the panic occured ? What is strange is that buffer was not even tried for i/o, AFAIS. Apart from empty b_error/b_iocmd, the b_lblkno is zero, which means that the buffer was never allocated on the disk. The b_blkno looks strangely high. Can you print *(bp->b_vp) ? If it is UFS vnode, do p *(struct inode)(<vnode>->v_data). I am esp. interested in the vnode size. Can you reproduce the problem on HEAD ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1009064032.2811332.1467839324186.JavaMail.app>