Date: Thu, 19 Oct 2017 16:46:31 +0200 From: "Kristof Provost" <kristof@sigsegv.be> To: "Dmitry Vyukov" <dvyukov@google.com> Cc: freebsd-hackers@freebsd.org, rwatson@freebsd.org, "Kostya Serebryany" <kcc@google.com>, syzkaller <syzkaller@googlegroups.com> Subject: Re: syzkaller for freebsd Message-ID: <95CF3989-2830-41E4-A29A-B32EBC818CE0@sigsegv.be> In-Reply-To: <CACT4Y%2Bak76pMDefZ9sz_pOSRiH1XPQ7Jvo%2BV6XwX394krqLg-A@mail.gmail.com> References: <CACT4Y%2Bak76pMDefZ9sz_pOSRiH1XPQ7Jvo%2BV6XwX394krqLg-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Neat! On 19 Oct 2017, at 14:05, Dmitry Vyukov via freebsd-hackers wrote: > panic: ffs_write: type 0xfffff80003eee760 8 (0,0) > https://pastebin.com/raw/Xm80kYSz > This one even comes with a C reproducer (which is surprising, because > syzkaller currently only generates/builds reproducers for Linux, still > it somehow run on FreeBSD and triggered the crash): > https://pastebin.com/raw/EZe8thej > FreeBSD can run (some/many) Linux binaries, so perhaps that’s what you’re seeing here. > Fatal trap 12: page fault in vnet_pf_uninit > https://pastebin.com/raw/0AiJJz7D > I’m pretty sure this one isn’t really a direct result of fuzzing. Unloading pf on 11.1 is unreliable. Doing `kldunload -f pf` will likely result in the same panic. I believe this to be fixed in CURRENT. Regards, Kristof From owner-freebsd-hackers@freebsd.org Thu Oct 19 15:08:51 2017 Return-Path: <owner-freebsd-hackers@freebsd.org> Delivered-To: freebsd-hackers@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 5A25CE3E12B for <freebsd-hackers@mailman.ysv.freebsd.org>; Thu, 19 Oct 2017 15:08:51 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED5416D464 for <freebsd-hackers@freebsd.org>; Thu, 19 Oct 2017 15:08:50 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 61d13e65-b4df-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 61d13e65-b4df-11e7-a893-25625093991c; Thu, 19 Oct 2017 15:08:38 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9JF8XQC008662; Thu, 19 Oct 2017 09:08:33 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1508425713.1383.6.camel@freebsd.org> Subject: Re: We do serial differently. From: Ian Lepore <ian@freebsd.org> To: Zaphod Beeblebrox <zbeeble@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Date: Thu, 19 Oct 2017 09:08:33 -0600 In-Reply-To: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9+dUtp66+SSjVuyhpxA@mail.gmail.com> References: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9+dUtp66+SSjVuyhpxA@mail.gmail.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD <freebsd-hackers.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>; List-Post: <mailto:freebsd-hackers@freebsd.org> List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 19 Oct 2017 15:08:51 -0000 On Thu, 2017-10-19 at 00:25 -0400, Zaphod Beeblebrox wrote: > How does FreeBSD do serial differently than Linux or MacOS or Windows? > > Now... this isn't _exactly_ serial, but the serial that is emulated by the > arduino driver in ports. > > The issue is that running the arduino IDE works (and it boots with the > loaded code), but then running 'pronterface' fails to connect --- looking > all-the-while like one-way communication. > > I see someone else basically having the same problem and claiming that > hacking a trace (that affects the DTR response) on the arduino fixes it for > FreeBSD (see https://plus.google.com/+MiroslavPrymek/posts/6TDdbuoNhzH )... > > Given this information, can I stty my way out of this problem? Can I make > a small modification to pronterface? Use the "callout" device, /dev/cuaXX, rather than /dev/ttyXX (which is the "callin" device). The callin device waits for a call to come in, and that's implemented by blocking in open() until the modem/other-end asserts DTR (or DSR, I can never remember which end is which). So if it's hanging with /dev/ttyU0 use /dev/cuaU0. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95CF3989-2830-41E4-A29A-B32EBC818CE0>