From owner-freebsd-current@freebsd.org Mon Apr 1 15:16:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24B44156656D for ; Mon, 1 Apr 2019 15:16:48 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-yw1-f67.google.com (mail-yw1-f67.google.com [209.85.161.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A59473487 for ; Mon, 1 Apr 2019 15:16:46 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-yw1-f67.google.com with SMTP id x129so3390854ywc.1 for ; Mon, 01 Apr 2019 08:16:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gw3C3igBRrNqq1SoZXr5t5Xug7wFSD43831ZUuqh6Eg=; b=P54PPEZV+MtTSqvGuQ+ckoUIWAEsjB2Tix+nyV+6RSwDMzO7D4oXyN7D57XQbOQM3i NyTqISFrqikvR6kzX+gHi6M9W5fIaR0jkfzMb/D+xnULvhRX7SJo8YMoPMBBSCI89sRC 1ivF8Wf5jISQwG4nsHGcony1Mkj8nDvRXbjZxUZixcq+kN+T9iNBX5DN1OMJ57ROk4UC 43SzsHdhCHEqxax+9TcY+NKm/9jE0LzvfLbH2XagT1I0ecIaj7+RPgXtQLyQDHRNUlUp DFusLSDrR/NT9kJWZGBJfKobxKys8K3qSCZFdizZA9EYK5FpYVC2FdjcF6qr7YFe3nwI 1SkA== X-Gm-Message-State: APjAAAXdlZdGW4LG+/Nm+GmhP52m1pWioIgy0hGACN9UMnMC3T2AB1Hc HVGDVYQ6Y35+bGA0WZXt29n2XL3SVf12gwIvSiXHmvp1 X-Google-Smtp-Source: APXvYqwbmFUgCoO7HI8WhhaE38VH/wLc5NvMf0preYn6UW6g7TST96d1W5xfCMnHHlgfhqBvUfv0adgiCvbyEv5msYQ= X-Received: by 2002:a81:3a57:: with SMTP id h84mr52075079ywa.284.1554131799909; Mon, 01 Apr 2019 08:16:39 -0700 (PDT) MIME-Version: 1.0 From: Li-Wen Hsu Date: Mon, 1 Apr 2019 23:16:28 +0800 Message-ID: Subject: FreeBSD CI Weekly Report 2019-03-31 To: freebsd-testing@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 7A59473487 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of lwhsufreebsd@gmail.com designates 209.85.161.67 as permitted sender) smtp.mailfrom=lwhsufreebsd@gmail.com X-Spamd-Result: default: False [-4.15 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FORGED_RECIPIENTS(0.00)[freebsd-testing@freebsd.org,freebsd-current@freebsd.org]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[67.161.85.209.rep.mailspike.net : 127.0.0.18]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.92)[-0.925,0]; DMARC_NA(0.00)[freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[67.161.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.88), asn: 15169(-2.15), country: US(-0.06)]; FORGED_SENDER(0.30)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Mailman-Approved-At: Mon, 01 Apr 2019 15:56:09 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Apr 2019 15:16:48 -0000 (bcc -current and -stable for more audience) FreeBSD CI Weekly Report 2019-03-31 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-03-25 to 2019-03-31. During this period, we have: * 2095 builds (98.7% passed, 1.3% failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 363 test runs (52.6% passed, 46.8% unstable, 0.6% exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 8 doc buils (100% passed) (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/s/BymrvPI_4 and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Fixed Tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * lib.libarchive.functional_test.test_fuzz_zip Fixed in https://svnweb.freebsd.org/changeset/base/345497 * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * lib.libc.regex.exhaust_test.regcomp_too_big * lib.libregex.exhaust_test.regcomp_too_big Fixed in https://svnweb.freebsd.org/changeset/base/345516 ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * lib.libc.sys.sendfile_test.fd_positive_shm_v4 * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 * (New) lib.libc.gen.floatunditf_test.floatunditf * (New) lib.libc.stdio.printfloat_test.hexadecimal_rounding * (New) lib.msun.ctrig_test.test_small_inputs * (New) lib.msun.precision_test.t_precision https://bugs.freebsd.org/236936 * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * lib.libc.regex.exhaust_test.regcomp_too_big * lib.libregex.exhaust_test.regcomp_too_big * sys.kern.coredump_phnum_test.coredump_phnum WIP: https://reviews.freebsd.org/D18495 * https://ci.freebsd.org/job/FreeBSD-stable-11-amd64-test/ * usr.bin.procstat.procstat_test.kernel_stacks * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * sys.netmap.ctrl-api-test.main * sys.opencrypto.runtests.main * usr.bin.procstat.procstat_test.kernel_stacks * local.kyua.* (31 cases) * local.lutok.* (3 cases) * lib.libc.sys.sendfile_test.fd_positive_shm_v4 * lib.libc.sys.sendfile_test.hdtr_negative_bad_pointers_v4 ## Failing Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * common.ip.t_dtrace_contrib.tst_ipv4localsctp_ksh * common.ip.t_dtrace_contrib.tst_localsctpstate_ksh * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * usr.bin.procstat.procstat_test.command_line_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 ## Closed Issues * Flakey test case: lib.libarchive.functional_test.test_fuzz_zip https://bugs.freebsd.org/236300 ## Oepn Issues * https://bugs.freebsd.org/236936 4 test cases failing on i386 after r345562 ### Cause build fails * [233735: Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory](https://bugs.freebsd.org/233735) * [233769: Possible build race: ld: error: unable to find library -lgcc_s](https://bugs.freebsd.org/233769) ### Others [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-current@freebsd.org Mon Apr 1 21:11:54 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F386D156F2F8; Mon, 1 Apr 2019 21:11:53 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D8018A080; Mon, 1 Apr 2019 21:11:52 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm1-x331.google.com with SMTP id n25so989816wmk.4; Mon, 01 Apr 2019 14:11:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition:user-agent; bh=eHUr+4T3iQ2WSL+LelN9wyBJ2HetQUpnpYMdr1OqsuM=; b=iQBd9ozni4Rv1fUCTl5mYpXeE0zqKrYXMKAMUCjuAY+uFVMxPRyCcsNJr67nMjcn7q +9XGBdAL52/eRcf96QlsLQl/li36YmQLHo7/uPdTjxlrUZahbWxxikGNYVVkiRssKoNO q3WumQ5NHF4/wn0SnSYG5fgklbLv8PjijZ+SW7utTw59NJeKUn/1XqdcOBr7Nl1frL3W vAdmgUTlTlf5NnX6DnkZyXVA2Zta6jsMYwSGDsjA26OcomaqJcKWbIdF+hXdP19yWtqf XezFqKQK6O1wLxyjMgcOaBVn30zo9rorMxf3cRDZY1V56pWOopYcqLO6xm/q62rVQdQL Rnkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mail-followup-to:mime-version:content-disposition:user-agent; bh=eHUr+4T3iQ2WSL+LelN9wyBJ2HetQUpnpYMdr1OqsuM=; b=sXBcBpBujBhfnQdwZufYtRo23nhAAwdMB3jdoREg+0rOxohP+55UcVkD/+Gy3ZxVbw OkM9amfVbVu5ljwcmCAJfDJXpy6BmR3/b1FK7//B4uU3KARzWNIl7Y7/G+FVF6zFa6U2 3sIbQZRWju2ENEiOi9280qkYJXVKXuaClWZ4idMV8uCMcyHSuUSdLeMctBFj8cCVuwA5 vwTU0U010q10sXoHlSmk9YQD4SkljExYyOPQyyEMrzjARGaQUGA0sSZb3cg42YW9PPfJ aWcNy+jQjeTQUAm6waN8cAMROh3i0b7Tr0b0oIRs6u+045aLvH+26w+tb5lpXG5MTN2U hDgA== X-Gm-Message-State: APjAAAWLychoB6Qu0ldxOqj/sJfdYngk7nlZ+X0Mc5gEB5lGxB4YzarF JxL+546ehvf3RADFT9M0x0mGzffB X-Google-Smtp-Source: APXvYqwf1pclv0BkKDkO22uIPWMrr2sPC/Ne1imYZQPdZlNh3kr7NLCw3I3JjMZq0k7r614NjFs9XQ== X-Received: by 2002:a1c:6a0d:: with SMTP id f13mr1081218wmc.76.1554153110839; Mon, 01 Apr 2019 14:11:50 -0700 (PDT) Received: from v2 (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id y125sm18686697wmc.39.2019.04.01.14.11.49 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 01 Apr 2019 14:11:49 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Mon, 1 Apr 2019 18:49:52 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Call for 2019Q1 quarterly status reports Message-ID: <20190401174952.GA8844@v2> Mail-Followup-To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline User-Agent: Mutt/1.11.3 (2019-02-01) X-Rspamd-Queue-Id: 6D8018A080 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=iQBd9ozn; spf=pass (mx1.freebsd.org: domain of etnapierala@gmail.com designates 2a00:1450:4864:20::331 as permitted sender) smtp.mailfrom=etnapierala@gmail.com X-Spamd-Result: default: False [-7.55 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[trasz@freebsd.org,etnapierala@gmail.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[trasz@freebsd.org,etnapierala@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_SHORT(-0.99)[-0.990,0]; IP_SCORE(-2.75)[ip: (-9.15), ipnet: 2a00:1450::/32(-2.36), asn: 15169(-2.15), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[1.3.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MID_RHS_NOT_FQDN(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Apr 2019 21:11:54 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 30, 2019, for work done since the last round of Quarterly Reports: January, 2019 =E2=80=93 March, 2019. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about work that is underway and completed. Submission of reports is not restricted to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarterly@FreeBSD.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-s= ample.md The old XML generator and templates are no longer used. We look forward to seeing your 2019Q1 reports! Thanks, Edward (on behalf of quarterly@) --J/dobhs11T7y2rNN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGmBAEBCgCQFiEEbvjBe1hu6u1NeinjJCKD+Vwk/7oFAlyiT0BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZF RjhDMTdCNTg2RUVBRUQ0RDdBMjlFMzI0MjI4M0Y5NUMyNEZGQkESHHRyYXN6QGZy ZWVic2Qub3JnAAoJECQig/lcJP+6Jx0H/2YmGr1upqgTjc+Uur8uXFovS4V571Zf ddZnWVJ9kJX2matASDp/OwCFEuWSk9dGAUTkzuAGme/wK1ke3PM9tcH3hY+HLphc xhsxUs6wLgwCe28TX4JFKAkZMlJ8sc2i//AXo7u1YolABvgNwEk51ThDPKlnE7pw FbyOQMLGSTdJbrgz78pD42alCMNSmN/Zz5txD6pIwFBWrqbAF4BHw5kvHplQOk38 FQqH/MW6kIbdiPs/KNUbVllPyaBe/nXAKudm0AjCLzzWbrMheWpjlELMkw9sBe46 7Qfw9wdVSMrwzcRMLq8GUXrajDZvhjI7SC04mjbhiyXoZV1xttiCwOk= =E9Un -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-current@freebsd.org Wed Apr 3 07:05:38 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A4481560ADB; Wed, 3 Apr 2019 07:05:38 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail1.yamagi.org (mail1.yamagi.org [IPv6:2001:19f0:5001:17bd::2]) (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 6791296856; Wed, 3 Apr 2019 07:05:37 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from [212.48.125.108] (helo=aka) by mail1.yamagi.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1hBZxm-000AKq-Pe; Wed, 03 Apr 2019 09:05:36 +0200 Date: Wed, 3 Apr 2019 09:05:22 +0200 From: Yamagi Burmeister To: rozhuk.im@gmail.com Cc: dariusmihaim@gmail.com, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Boot hang on ryzen based notebook Message-Id: <20190403090522.548ffbdaad84c2c001a6926d@yamagi.org> In-Reply-To: <20190330211736.05b39193@rimwks> References: <20190330164628.138a2bad@rimwks> <20190330204138.18fe8443@rimwks> <20190330211736.05b39193@rimwks> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA256"; boundary="Signature=_Wed__3_Apr_2019_09_05_22_+0200_GXlVhFLCDLN3VP/8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2019 07:05:38 -0000 --Signature=_Wed__3_Apr_2019_09_05_22_+0200_GXlVhFLCDLN3VP/8 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 30 Mar 2019 21:17:36 +0300 Rozhuk Ivan wrote: > > You wrote "apic.0.disabled", not "acpi.0.disabled". Are you sure you > > wrote the correct command? You do not want to disable the APIC > > (interrupt controller), but the ACPI (control and power interface). >=20 > hint.acpi.0.disabled=3D"1" - 11.13.1. > Then set: > panic: running without device atpic requires a local APIC Most modern hardware won't boot without ACPI. But I can get my Lenovo E485 to boot with Linux and FreeBSD if I disable IOMMU aupport in the BIOS / UEFI. --=20 Homepage: https://www.yamagi.org Github: https://github.com/yamagi GPG: 0x1D502515 --Signature=_Wed__3_Apr_2019_09_05_22_+0200_GXlVhFLCDLN3VP/8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOXu/lxyufwz0gC5x6xRy5x1QJRUFAlykWzIACgkQ6xRy5x1Q JRWccQ//Qn5SL++7sKEiTzwKVQPbIJURjxmEMPvXrsHBVDVTR5MeSS8zakZ1bDR/ nWjsR9EC1nx0CJtmNB92xalaH8I44yoTApZlntc6gzJP4fA1gzLrnMP+GUCYbFBF EhXS+f04ti0Vl+VZ5jtP26X0VOrqE10TUwqlaj/yEOlMPq24hPpXggT1iFFHL8SW cxQdWPpPxeU+VfhYhkxYulBXtOPx72EYToaOcvSB41dHQO4/oSn/w2fM1lhWeeVo fcP2s8aK0aeoQSUzaI6gFltBTyU8qVh3zXRap8Gvt9BRhQJn9xuQdayhJlAnqfzi VbA6SF0fXTghV9g0zkBmzov/6OazoXC7w4BOEXqekOlDRCMwWT243iLIayJ6KnTo 2HLTOpU2Kz9XgGSGwGu+shbt6GlK/b28rxnb0thWzISDkaYC4ght67urq1sqO94y DHBu5fxUSKPggPL6AKjroNMFu+6nRFlF0/GjWeo40QSz5dYxmc1qRW7pytljyJcQ 2Ykm/E5lnBj7bFJ1JmBw2xT67bH2GdrvvPF32e+nLlH4UZHFwojoQ45f0RZp0W+7 1RscZAdVOfIKrBlah4YlCFIvlVdZYt5Yx4FESEU4nuTD675bqQan59DoTUUQhJRT d5PoMKp6f8/uFQlVU+EXDCphQO1hv5bk3fPCpzzOfLE50ZnC4Iw= =8EnE -----END PGP SIGNATURE----- --Signature=_Wed__3_Apr_2019_09_05_22_+0200_GXlVhFLCDLN3VP/8-- From owner-freebsd-current@freebsd.org Wed Apr 3 09:11:57 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 651D31565734; Wed, 3 Apr 2019 09:11:57 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D15DF6E25A; Wed, 3 Apr 2019 09:11:56 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-ed1-x52c.google.com with SMTP id d26so14184030ede.10; Wed, 03 Apr 2019 02:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=IIoUkuK0FRxcICaoZO0Y3iJkVSOLmp72E9abMx6heq4=; b=VQNO4f3RRd2LlrGPYvHccPS4FqmRhwFtPN9rXhyXpV8zC31mS+KSZuiRD2lbDhS7Mr +DtqBDRJB0CagMAvSyr5dl/DUMlSdKKeePmKTrmtUy5CjYsKdX0jdHOTzA4bNxevRMjT dKQM0Pzh3+wphArASSSPa5O7PpJxb+7gWADLE1jzKJ1OLHf/d9P6gnqvdnwZEz77CU3Y rgqA06A1uAuTmxKw4s22LSVWye0+9fJytf5lM9i4heTNRZH7/QVP/qFoe2EKJS9mx+Yq Xsqd/RA9zzvWr6xMHxYzX2CEHOdBxK2mRauoM9ujnCJXOmTd3m4HexwPVl0yS/zAzOzN 0sfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=IIoUkuK0FRxcICaoZO0Y3iJkVSOLmp72E9abMx6heq4=; b=qNBzFWPK9nrIh3e+KqW7x5wi/iy2nlwdzzUpW2zsw3q2SwFvsb8ObOdUHUZLbiy/T0 fpcsfUzarvV4IjD8Ws6UbDDLg5Lu3fS5ebxR8poBLP7oVkixh5h10bS7lQJ7BiUKRGRP TQOVQxm6ANMA47KYHydCHBCR0Seey+pcv/mH1JoX347wq1GygtmS2Vhqa6e5rbO28T4b 5onbyxEKu59MCaDaaMTz2qfnbAFOf8cy+bhyL9H2wTPUUnqI3Xse5TTSl3rJzwI2fD5q +cAZY2wjemW/1vGqu0+WbopWPN2h478/w2//gujrodgNiACg5EedMqe4AHQBe5L6r4zN s2fg== X-Gm-Message-State: APjAAAWSVFzkbHlNchh3+0nSq8wXhTgLmxqea5Wk8EtWA/YXryr5oU+v CPtzhgNP/SqTZu6wh1XlDh0= X-Google-Smtp-Source: APXvYqx9dgnX0aO/u5Vlwt5nFy3xESE1I+pT5XQ4QhTcck/NVe9nQPJm4c2Aq1mZHRA+lXzALQkbGQ== X-Received: by 2002:a50:b79d:: with SMTP id h29mr47876554ede.233.1554282715552; Wed, 03 Apr 2019 02:11:55 -0700 (PDT) Received: from rimwks ([2001:470:1f15:3d8:692:26ff:fec0:61d6]) by smtp.gmail.com with ESMTPSA id f58sm4734916edd.42.2019.04.03.02.11.53 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 03 Apr 2019 02:11:54 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Wed, 3 Apr 2019 12:11:52 +0300 To: Yamagi Burmeister Cc: dariusmihaim@gmail.com, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Boot hang on ryzen based notebook Message-ID: <20190403121152.7f7f915c@rimwks> In-Reply-To: <20190403090522.548ffbdaad84c2c001a6926d@yamagi.org> References: <20190330164628.138a2bad@rimwks> <20190330204138.18fe8443@rimwks> <20190330211736.05b39193@rimwks> <20190403090522.548ffbdaad84c2c001a6926d@yamagi.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: D15DF6E25A X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.979,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2019 09:11:57 -0000 On Wed, 3 Apr 2019 09:05:22 +0200 Yamagi Burmeister wrote: > > > You wrote "apic.0.disabled", not "acpi.0.disabled". Are you sure > > > you wrote the correct command? You do not want to disable the APIC > > > (interrupt controller), but the ACPI (control and power > > > interface). > > > > hint.acpi.0.disabled="1" - 11.13.1. > > Then set: > > panic: running without device atpic requires a local APIC > > Most modern hardware won't boot without ACPI. But I can get my Lenovo > E485 to boot with Linux and FreeBSD if I disable IOMMU aupport in the > BIOS / UEFI. > With hw.pci.mcfg=0 - boot ok. From owner-freebsd-current@freebsd.org Fri Apr 5 12:19:17 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 301471575760 for ; Fri, 5 Apr 2019 12:19:17 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A60F58EE91; Fri, 5 Apr 2019 12:19:16 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1554466753; bh=kFpjojdF0G4UmXu/QO33K/fiinoo5Bt5twmXjNL c34w=; b=qdrpGdw6f1rrc35B4l57uiJI25Calp1CIKx7DpymOQgNlQJrhmGrCD3 rjzHFDsdpLeOM2XI0A/Pa+L4j2lHGAQqmi+peIfE8ZfaAjVWO4HpSo0/xM+e1Un9 86agRfBDFIqJ1RjDxr4na71l+AOZ8gWinh+ZBPIpqH+gq1cuXKlY= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 3AEB41E34; Fri, 5 Apr 2019 08:19:13 -0400 (EDT) To: freebsd-current From: Michael Butler Openpgp: preference=signencrypt Cc: phil@freebsd.org Subject: SVN r345859: libxo broke netstat? Message-ID: Date: Fri, 5 Apr 2019 08:19:12 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 12:19:17 -0000 Something changed in libxo that causes 'netstat -i' to segfault as below: imb@toshi:/usr/src/usr.bin/netstat> lldb /usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat (lldb) target create "/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat" Current executable set to '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64). (lldb) run -i Process 65948 launching Process 65948 launched: '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64) Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Process 65948 stopped * thread #1, name = 'netstat', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x00000008002987ad libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0: -> 0x8002987ad <+669>: movsbl (%r12), %eax 0x8002987b2 <+674>: movslq %eax, %rbx 0x8002987b5 <+677>: movq 0xac04(%rip), %r13 0x8002987bc <+684>: testl %eax, %eax (lldb) bt * thread #1, name = 'netstat', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x00000008002987ad libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 frame #1: 0x0000000800294e09 libxo.so.0`___lldb_unnamed_symbol24$$libxo.so.0 + 1401 frame #2: 0x0000000800293b91 libxo.so.0`___lldb_unnamed_symbol22$$libxo.so.0 + 609 frame #3: 0x0000000800293df0 libxo.so.0`xo_emit + 256 frame #4: 0x0000000000212dc5 netstat`intpr + 1669 frame #5: 0x0000000000217ecf netstat`main + 2431 frame #6: 0x000000000021210f netstat`__fini_array_end + 271 From owner-freebsd-current@freebsd.org Fri Apr 5 16:39:23 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D9761551151 for ; Fri, 5 Apr 2019 16:39:23 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CB796A615; Fri, 5 Apr 2019 16:39:22 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg1-x535.google.com with SMTP id v12so3365852pgq.1; Fri, 05 Apr 2019 09:39:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PmbcKxoE9Pv/W4fDKWNXxoX/mpNaysNL/xD2RFkbNbY=; b=OqiOHrwrjT6zQ3zoLDWdNvxtq0MRbCEHHjh5YEh0c6MqsupuF3u2Kl/XNjrkw0SnEa /JELNcinGVYsbyOI00ESn36MuVmhPNBn8OvRfIhksiUGhSByNmAt5yHK/o0rLgCLyh64 EfjzGZXqM4MDNJK9nxjbh4U4eZLbo/VCbn6MFKPEtdHtXL4vg5Ecy68M+a9MqERCOknz 0fM7p2aOIW8ZVyOJz9MZn5ileYZchJcgnd/8LV+zR9PiR1vnWrxKrY5A8gL91Iqn3tmz B1cVMAWIELdRqV+CkG5+iEQxThjV6mVDPqDzMLMvp/TwuNJ5BIGxaT+vOwXYYrkTbCRI SE7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PmbcKxoE9Pv/W4fDKWNXxoX/mpNaysNL/xD2RFkbNbY=; b=m2EJKcEK1+WJI5i4N8r5lXUzYnN0cz0Rmww9RMwvu4z/OlCMzxKSHytcSvmmV+W8Ft vgri0WwrMU4QEXYhVRVtyU/CRF3bizXwriMATAPBthiKtvbk4DMnnaVgYbZmJb7SM7U/ iZPBskxVJSXRw6E8hruraldnnDahAM7cctEGZXM40v8rlLUaSY47jR3I0+M0J4Hlj1dq i3ucSIs9K4QLBqHu91AEfch3LOrVo7/Jiy1ENbn6A3slhblhcJOZomQiABhJibn91lUB eWe9mxgTyOxPK+my/XqNc/BwB3eSG5DuGgvfxmNdU86BVhKtV2Gi0QwifwvtG0L2ZJC1 V07Q== X-Gm-Message-State: APjAAAVruEzlyLRIYbCckKrsEfdnLMJROoio5nhQ7arz5cxpnk3uaMh9 259t43DgRF0hNZ9qz6OKJZVki4xBV8M= X-Google-Smtp-Source: APXvYqzEY60aQZ6COK9xS1z2gq8OdVnSvB8yg+2R6f8eaa+liSlTZsSXaH2T2Zn3AFLl2xws2qKuEw== X-Received: by 2002:a63:6581:: with SMTP id z123mr12639012pgb.243.1554482361139; Fri, 05 Apr 2019 09:39:21 -0700 (PDT) Received: from [192.168.20.7] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id o5sm76643745pfa.135.2019.04.05.09.39.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Apr 2019 09:39:20 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: SVN r345859: libxo broke netstat? From: Enji Cooper In-Reply-To: Date: Fri, 5 Apr 2019 09:39:19 -0700 Cc: freebsd-current , phil@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8A6173F2-B6A5-48E6-9EC0-063698C0C511@gmail.com> References: To: Michael Butler X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 7CB796A615 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.964,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 16:39:23 -0000 > On Apr 5, 2019, at 5:19 AM, Michael Butler = wrote: >=20 > Something changed in libxo that causes 'netstat -i' to segfault as = below: >=20 > imb@toshi:/usr/src/usr.bin/netstat> lldb > /usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat > (lldb) target create = "/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat" > Current executable set to > '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64). > (lldb) run -i > Process 65948 launching > Process 65948 launched: > '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64) > Name Mtu Network Address Ipkts Ierrs Idrop > Opkts Oerrs Coll > Process 65948 stopped > * thread #1, name =3D 'netstat', stop reason =3D signal SIGSEGV: = invalid > address (fault address: 0x0) > frame #0: 0x00000008002987ad > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0: > -> 0x8002987ad <+669>: movsbl (%r12), %eax > 0x8002987b2 <+674>: movslq %eax, %rbx > 0x8002987b5 <+677>: movq 0xac04(%rip), %r13 > 0x8002987bc <+684>: testl %eax, %eax > (lldb) bt > * thread #1, name =3D 'netstat', stop reason =3D signal SIGSEGV: = invalid > address (fault address: 0x0) > * frame #0: 0x00000008002987ad > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 > frame #1: 0x0000000800294e09 > libxo.so.0`___lldb_unnamed_symbol24$$libxo.so.0 + 1401 > frame #2: 0x0000000800293b91 > libxo.so.0`___lldb_unnamed_symbol22$$libxo.so.0 + 609 > frame #3: 0x0000000800293df0 libxo.so.0`xo_emit + 256 > frame #4: 0x0000000000212dc5 netstat`intpr + 1669 > frame #5: 0x0000000000217ecf netstat`main + 2431 > frame #6: 0x000000000021210f netstat`__fini_array_end + 271 Michael, Could you please file a PR for this? Thank you! -Enji From owner-freebsd-current@freebsd.org Fri Apr 5 19:03:58 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA23C155823D for ; Fri, 5 Apr 2019 19:03:58 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 799A66F5F3; Fri, 5 Apr 2019 19:03:57 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id CU7vhqlFmsAGkCU7whdfqb; Fri, 05 Apr 2019 13:03:50 -0600 X-Authority-Analysis: v=2.3 cv=WeVylHpX c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=oexKYjalfGEA:10 a=pGLkceISAAAA:8 a=zxA2vyXaAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=RiKPiEmj_PkCBvM_GNYA:9 a=qxRNq1ZIBcZtRpE9:21 a=DspgWPCihwn702_f:21 a=CjuIK1q_8ugA:10 a=nK2txNHJmq7TfjpuLlwI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id 562D72E6B; Fri, 5 Apr 2019 12:03:46 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x35J3R9a004661; Fri, 5 Apr 2019 12:03:27 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x35J3RHM004658; Fri, 5 Apr 2019 12:03:27 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201904051903.x35J3RHM004658@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Enji Cooper cc: Michael Butler , freebsd-current , phil@freebsd.org Subject: Re: SVN r345859: libxo broke netstat? In-Reply-To: Message from Enji Cooper of "Fri, 05 Apr 2019 09:39:19 -0700." <8A6173F2-B6A5-48E6-9EC0-063698C0C511@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Apr 2019 12:03:27 -0700 X-CMAE-Envelope: MS4wfKCg6yRYIGWkdYYMU8LHBsrSzVwNHmuChKxIbr7Aqy/5y8yOqv9EpgNTnxiAZ8txILY9lrIA3ok/lco7Tn+FpcAAKdFUfbXqunV997/iTz/YzUI0FSea Mcunr4NGM9CF4HpSv0jMaIoL4w3V4Gk91V2rGepZH2uu1zRnAqx/Rvje2RdmV1H1E1k1ny83+boGJ7Kn0JOMHtlMVQOnC15T6Yesz2oOWwxPBxfYjSpjk4Py SaITR1kE8DjuMY6TjHTm8ZA+5xCYIOpBZFRsbSoN1WA+2eBkmTd6CpXOg0gNm/kn X-Rspamd-Queue-Id: 799A66F5F3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.07 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.96)[-0.958,0]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; RCVD_IN_DNSWL_LOW(-0.10)[12.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; SUBJECT_ENDS_QUESTION(1.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.40)[ip: (-6.46), ipnet: 64.59.128.0/20(-3.07), asn: 6327(-2.38), country: CA(-0.09)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 19:03:59 -0000 In message <8A6173F2-B6A5-48E6-9EC0-063698C0C511@gmail.com>, Enji Cooper writes : > > > On Apr 5, 2019, at 5:19 AM, Michael Butler wro > te: > > > > Something changed in libxo that causes 'netstat -i' to segfault as below: > > > > imb@toshi:/usr/src/usr.bin/netstat> lldb > > /usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat > > (lldb) target create "/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat" > > Current executable set to > > '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64). > > (lldb) run -i > > Process 65948 launching > > Process 65948 launched: > > '/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat' (x86_64) > > Name Mtu Network Address Ipkts Ierrs Idrop > > Opkts Oerrs Coll > > Process 65948 stopped > > * thread #1, name = 'netstat', stop reason = signal SIGSEGV: invalid > > address (fault address: 0x0) > > frame #0: 0x00000008002987ad > > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 > > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0: > > -> 0x8002987ad <+669>: movsbl (%r12), %eax > > 0x8002987b2 <+674>: movslq %eax, %rbx > > 0x8002987b5 <+677>: movq 0xac04(%rip), %r13 > > 0x8002987bc <+684>: testl %eax, %eax > > (lldb) bt > > * thread #1, name = 'netstat', stop reason = signal SIGSEGV: invalid > > address (fault address: 0x0) > > * frame #0: 0x00000008002987ad > > libxo.so.0`___lldb_unnamed_symbol30$$libxo.so.0 + 669 > > frame #1: 0x0000000800294e09 > > libxo.so.0`___lldb_unnamed_symbol24$$libxo.so.0 + 1401 > > frame #2: 0x0000000800293b91 > > libxo.so.0`___lldb_unnamed_symbol22$$libxo.so.0 + 609 > > frame #3: 0x0000000800293df0 libxo.so.0`xo_emit + 256 > > frame #4: 0x0000000000212dc5 netstat`intpr + 1669 > > frame #5: 0x0000000000217ecf netstat`main + 2431 > > frame #6: 0x000000000021210f netstat`__fini_array_end + 271 > > Michael, > Could you please file a PR for this? > Thank you! Add arp(8) broken by the libxo import. It's broken at line 603 of libxo.c as well. A NULL pointer deref. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Fri Apr 5 19:34:22 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D46BC155BB0B for ; Fri, 5 Apr 2019 19:34:21 +0000 (UTC) (envelope-from phil@juniper.net) Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E012571284; Fri, 5 Apr 2019 19:34:20 +0000 (UTC) (envelope-from phil@juniper.net) Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x35JUmuB017565; Fri, 5 Apr 2019 12:34:08 -0700 Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2056.outbound.protection.outlook.com [104.47.38.56]) by mx0b-00273201.pphosted.com with ESMTP id 2rp9ukrcdn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 05 Apr 2019 12:34:07 -0700 Received: from BN6PR05CA0020.namprd05.prod.outlook.com (2603:10b6:405:39::33) by DM5PR05MB3577.namprd05.prod.outlook.com (2603:10b6:4:45::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.8; Fri, 5 Apr 2019 19:34:04 +0000 Received: from CO1NAM05FT059.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::207) by BN6PR05CA0020.outlook.office365.com (2603:10b6:405:39::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.8 via Frontend Transport; Fri, 5 Apr 2019 19:34:04 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by CO1NAM05FT059.mail.protection.outlook.com (10.152.96.177) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1771.6 via Frontend Transport; Fri, 5 Apr 2019 19:34:03 +0000 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 5 Apr 2019 12:34:03 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Fri, 5 Apr 2019 12:34:03 -0700 Received: from idle.juniper.net (idleski.juniper.net [172.25.5.10]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x35JY1fo032513; Fri, 5 Apr 2019 12:34:02 -0700 (envelope-from phil@juniper.net) Received: from [172.25.5.11] (localhost [127.0.0.1]) by idle.juniper.net (8.15.2/8.15.2) with ESMTP id x35JYn58082829; Fri, 5 Apr 2019 15:34:49 -0400 (EDT) (envelope-from phil@juniper.net) From: Phil Shafer To: Cy Schubert CC: Enji Cooper , Michael Butler , freebsd-current , Subject: Re: SVN r345859: libxo broke netstat? Date: Fri, 5 Apr 2019 15:34:01 -0400 X-Mailer: MailMate (1.12.4r5608) Message-ID: In-Reply-To: <201904051903.x35J3RHM004658@slippy.cwsent.com> References: <201904051903.x35J3RHM004658@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(979002)(39860400002)(376002)(396003)(346002)(136003)(2980300002)(189003)(199004)(53936002)(68736007)(76506005)(229853002)(76176011)(54906003)(51416003)(16586007)(558084003)(316002)(81166006)(8936002)(86362001)(97736004)(81156014)(6916009)(6246003)(50226002)(2906002)(305945005)(8676002)(478600001)(48376002)(47776003)(82746002)(83716004)(106466001)(5660300002)(50466002)(356004)(6666004)(11346002)(7126003)(2616005)(476003)(336012)(486006)(186003)(53546011)(26005)(77096007)(126002)(4326008)(36756003)(33656002)(446003)(69596002)(426003)(105596002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3577; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: b04492af-5ade-4bb7-60f2-08d6b9fda970 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(4710095)(4711036)(2017052603328); SRVR:DM5PR05MB3577; X-MS-TrafficTypeDiagnostic: DM5PR05MB3577: X-Microsoft-Antispam-PRVS: X-Forefront-PRVS: 0998671D02 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: E3z42DegPb1gzubnR4ByFqvdptgVQMgTPgkm1y336+/Yt3ER4iwJ5y16gAVtm5aTLTQ7YRbnxqbbwjqpg8vtGzxogty1X+v3X5Ce5Sjlnrj9b67XoEqVULmoD2G1ZMaJ+5oUo7KiV7tBn0rPrfbJ6YoTzWxmJlioSuiiyvaUtoXh6opptO3NZps9Dyn//GoWI4OsPj+qe3jSBkJu9/rIv/N5iyn+XrqA79OTuMLG49U8av5KZYnxJ1mjRFmS2+XqdRkv+Gr+zecCc5GkNJaZ/B9/KY7h/HVA1tpxGPePv2QXpL+yn/Gv/dchiL1yobqL5q+IcGOv52NCrr/6G8earD+Xu6wj+7HDoU6AHVjzzt4mX5EaLs1Nmb/42hrIW5wNwN0GJ1YfBsNzcEBdDQIbClSOFeJeoutJc+8dVSTUXKw= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Apr 2019 19:34:03.8291 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: b04492af-5ade-4bb7-60f2-08d6b9fda970 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3577 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-05_15:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=618 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904050129 X-Rspamd-Queue-Id: E012571284 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.958,0]; R_DKIM_ALLOW(-0.20)[juniper.net:s=PPS1017]; RCVD_COUNT_SEVEN(0.00)[10]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:67.231.152.164]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mxb-00273201.gslb.pphosted.com]; DKIM_TRACE(0.00)[juniper.net:+]; DMARC_POLICY_ALLOW(-0.50)[juniper.net,reject]; NEURAL_HAM_SHORT(-0.49)[-0.494,0]; IP_SCORE(-0.13)[ip: (-0.38), ipnet: 67.231.152.0/24(-0.14), asn: 22843(-0.08), country: US(-0.06)]; RCVD_IN_DNSWL_LOW(-0.10)[164.152.231.67.list.dnswl.org : 127.0.3.1]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:22843, ipnet:67.231.152.0/24, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-Mailman-Approved-At: Fri, 05 Apr 2019 20:01:54 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 19:34:22 -0000 On 5 Apr 2019, at 15:03, Cy Schubert wrote: > Add arp(8) broken by the libxo import. It's broken at line 603 of > libxo.c as well. A NULL pointer deref. Apologies. I have a fix in hand. Will commit shortly. Thanks, Phil From owner-freebsd-current@freebsd.org Sat Apr 6 05:47:20 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFEF2156D7F1 for ; Sat, 6 Apr 2019 05:47:20 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F13828EE5D for ; Sat, 6 Apr 2019 05:47:19 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from fomalhaut.potoki.eu ([IPv6:2001:470:71:d47:288b:35ad:1929:c8f7]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPSA id x365l6na029878 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 6 Apr 2019 07:47:15 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1554529635; bh=fe5Uc83vMGvSKjv5FknMPeANTE8+VDUM+iP8XHUdOR4=; h=To:References:From:Subject:Date:In-Reply-To; b=pTW9mHYzX/vRoN+f4kRneD5+Q5481b4u9vrVo5TfZ6W5nZS5u6PaFab3Dte8+oAXf KImQqTn4ZvBe2ZembxppHDkx979IlrOPoqZ2zjDGot9dyyBTM4muw55muxfq6qs+GI GrwA8yU0yVNUrUHEGMZpZPikEvFS/jJW0P7yr8mOS6RvHrqj26caz0Qbcg/jRYaM/O eGlgSr+6yWU7rxN5KdZ1N3vTIp96/8dHDpj9AmAPLq5LG+gTfKT8FTbJTHa2Prd76T kOU9Ix7cVXx8Vqe6qUl1LLvUWDxPIRVL2zRIANGJ9pjlaUlppqtD5HkUJ7zLiXtOcf kwKtBufhqwSzw== X-Authentication-Warning: plan-b.pwste.edu.pl: Host [IPv6:2001:470:71:d47:288b:35ad:1929:c8f7] claimed to be fomalhaut.potoki.eu To: freebsd-current@freebsd.org References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> From: Marek Zarychta Openpgp: preference=signencrypt Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; prefer-encrypt=mutual; keydata= mQENBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAG0N01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD6JATcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgbkBDQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABiQEf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V65AQ0EV+OTdwEIAMxnGg7OO/ZAnSwiIiABA9lil1Lfa5BWTH3c l1rz4slz7Gw99G9J3bX3FiPA0vU89dgBZ2k0/UVk5cI5EsMAvwJN4bPwRsfBELQqjCKkVZr4 vUeGyvgQ2jnoK1fcEFOnCRdwFy4EJ6Y/fsZCTj4IfQpkM1W7C3KuSGPcjPDA9XCLDjjp8bbA Q9VgQ68MntAnYxMqK0S3CrHp5Pruvb0x4MfFLNwaKtWK+UnJGPT4umj8PMP6XLsFC3g+SGoP aWoYRDI297ZGx4IBWEaJq181oEC5iUQ6WREti9fNQ3TsAB3Q2CjNlkx1geSczIFJSyOHmyJZ RqAocw1sIuPopvhWtR0AEQEAAYkCRAQYAQgADwUCV+OTdwIbAgUJCWYBgAEpCRAdlby8gWmm gsBdIAQZAQgABgUCV+OTdwAKCRB1n+z//VKNLOETCAC3ggwAAQij4hkIxQFapnRuIVb5vq7D AwJ9+Ld5/zYHOj2Tfu+BPSNGzI2edqboz2w1t55UHEYzYDp2axxIfPrZrXsBV4DsjtGwzVV/ jZ9or5qTaYFDEStRkzL4mRpTyYhl/T7GgWpwOJWOih+cU7RWzjSOxiYMi4QSYlkpDUCcZew0 C3HfcxeFqpeL46zgysHC2ptjINXQ+xR2/F6dbed+l7OsvJAfkBqJoQ/48m+8ly1lbViKck7q gWw143ljaKn2qGIjZdb95zcI/CP4L45SXq8NOweACdx2NfUphLrIMbNCqLkMUJcrnruKfbnp C8OMjFJIqlu+PsW593NcZyOugEAH/0cBsDxlSauSVK4kp8ald26pcBI6igNnIMgjaxMiZBjn eoxBiKAOAO93sPnPr9/64CMMwv1T+0vU2lj8SMKOdHVrB9sW/ICGji5skE85xPEAtUkdAQN+ +c2clotujcaj9lBZKJdncKmSxY0SshEa66H+s76u+2Q3jGK6vOrdxakWYCvh2P0/l52Nd/t2 eazLFgwtk5rbo7O0MSC1GNXUsG07vtZ+zxJXFRx7PQ3ZIn0Y4HqwvXUvqgZ9EHiKy8F+ondz 9IS8/Fs81N5ieujHhSWqbaibapnpeDHvT/FWf8iXfJqWq+F7C8lGShSkmsS5AOhB4TNNH5/m ZzECJa1ql64= Subject: Re: HEAD'S UP: fusefs sysctls going away Message-ID: <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> Date: Sat, 6 Apr 2019 07:47:01 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pg7kAYhy6sEi9tXoLrPQVD6McF5JNszXq" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 05:47:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pg7kAYhy6sEi9tXoLrPQVD6McF5JNszXq Content-Type: multipart/mixed; boundary="z6wT2axPnmTARZ5tyOretUAHfHV9v9O3W"; protected-headers="v1" From: Marek Zarychta To: freebsd-current@freebsd.org Message-ID: <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> Subject: Re: HEAD'S UP: fusefs sysctls going away References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> In-Reply-To: --z6wT2axPnmTARZ5tyOretUAHfHV9v9O3W Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US W dniu 21.03.2019 o=C2=A017:03, Alan Somers pisze: > On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb wrote: >> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote: >>> On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb wrote: >>>> Hey Alan, >>>> >>>> Thank you very much for your work in maintaining fusefs. I only use >>>> fusefs in very limited circumstances, so take what I'm about to say >>>> with a grain of salt. >>>> >>>> On Thu, Mar 21, 2019 at 09:43:07AM -0600, Alan Somers wrote: >>>>> fusefs has several sysctl knobs that seem to be workarounds for bug= s >>>>> in particular fuse daemons. However, there is no indication as to >>>>> which those daemons are, neither in the code nor in SVN. All of th= e >>>>> workarounds are at least 6.5 years old, so the original bugs may ha= ve >>>>> been fixed already. Since the original bugs aren't documented, I >>>>> consider these workarounds to be unmaintainable, and I'm planning t= o >>>>> delete them unless anybody objects. Please pipe up if you still us= e >>>>> them! >>>>> >>>>> vfs.fusefs.mmap_enable: If non-zero, and data_cache_mode is also >>>>> non-zero, enable mmap(2) of FUSE files >>>> I'm curious if the security impacts of removing the toggle to disabl= e >>>> mmap support for fusefs. Is there a per-fusefs replacement for >>>> mmap_enable? From a security perspective, it would be nice to keep t= he >>>> ability to disable mapping of files mounted on a fusefs. >>> As a matter of fact, there are three other ways to disable mmap: >>> 1) Set vfs.fusefs.data_cache_mode=3D0. This completely disables cach= ing >>> file data, which precludes mmap. >>> 2) Use the undocumented -o no_datacache mount option, which does the >>> same thing on a per-mount basis. >>> 3) Use the undocumented -o no_mmap mount option, which disables mmap >>> on a per-mount basis. >> Awesome! I wasn't aware of these. Thanks! >> >>> Are you aware of any general security problems with using mmap? >>> Anything that would apply to fusefs but not other filesystems? >> Primarily because I trust the filesystems natively implemented in my >> OS more than I trust some (potentially random) fusefs module. >> >> For example, if I'm in a shared hosting environment, implemented with >> jails, and I let the customer mount a fusefs module in the jail (which= >> is now possible, if I remember right), then I must trust that the >> module's mmap integration is properly implemented. I'm not sure I >> personally am okay with that level of trust. > Ah, well you needn't worry about that. mmap is handled entirely > within the kernel. The userland fusefs module only sees writes and > reads. From userland's perspective, the only real difference is that > mmap()ed writes don't identify the pid of the originating process, > whereas direct writes do (except when vfs.fusefs.data_cache_mode=3D=3D2= ). > >> However, the point is moot now that you documented the three ways to >> disable mmap (two of which work on a per-mount basis). After recent changes in fusefs code I am getting such panics regularly on amd64: Fatal trap 12: page fault while in kernel mode cpuid =3D 3; apic id =3D 03 fault virtual address=C2=A0=C2=A0=C2=A0 =3D 0x248 fault code=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =3D supervisor read data=C2= =A0 , page not present instruction pointer=C2=A0=C2=A0=C2=A0 =3D 0x20:0xffffffff82d6250c stack pointer=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =3D 0x28:0xfffffe005dc2c630 frame pointer=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =3D 0x28:0xfffffe005dc2c7b0 code segment=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =3D base 0x0, limit 0xf= ffff, type 0x1b =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =3D DPL 0, pres = 1, long 1, def32 0, gran 1 processor eflags=C2=A0=C2=A0=C2=A0 =3D interrupt enabled, resume, IOPL =3D= 0 current process=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =3D 2016 (mount_fuse= fs) trap number=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =3D 12 panic: page fault cpuid =3D 3 time =3D 1554528396 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe005dc2c2e0 vpanic() at vpanic+0x19d/frame 0xfffffe005dc2c330 panic() at panic+0x43/frame 0xfffffe005dc2c390 trap_fatal() at trap_fatal+0x394/frame 0xfffffe005dc2c3f0 trap_pfault() at trap_pfault+0x49/frame 0xfffffe005dc2c450 trap() at trap+0x29f/frame 0xfffffe005dc2c560 calltrap() at calltrap+0x8/frame 0xfffffe005dc2c560 --- trap 0xc, rip =3D 0xffffffff82d6250c, rsp =3D 0xfffffe005dc2c630, rbp= =3D 0xfffffe005dc2c7b0 --- fuse_vfsop_mount() at fuse_vfsop_mount+0x5dc/frame 0xfffffe005dc2c7b0 vfs_domount() at vfs_domount+0xace/frame 0xfffffe005dc2c9e0 vfs_donmount() at vfs_donmount+0x934/frame 0xfffffe005dc2ca80 sys_nmount() at sys_nmount+0x69/frame 0xfffffe005dc2cac0 amd64_syscall() at amd64_syscall+0x36e/frame 0xfffffe005dc2cbf0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe005dc2cb= f0 --- syscall (378, FreeBSD ELF64, sys_nmount), rip =3D 0x8002d510a, rsp =3D= 0x7fffffffe128, rbp =3D 0x7fffffffe730 --- KDB: enter: panic Last time I have checked it happened on FreeBSD 13.0-CURRENT #21 r345948: Fri Apr=C2=A0 5 17:12:53 CEST 2019. As a workaround loading fusefs.ko and fuse.ko modules can be disabled. --=20 Marek Zarychta --z6wT2axPnmTARZ5tyOretUAHfHV9v9O3W-- --pg7kAYhy6sEi9tXoLrPQVD6McF5JNszXq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlyoPVkACgkQdZ/s//1S jSxaaQf7BMqw5+7qQ/mdg/aKEVvV9PlhMQd0n4ShhvpH6Xs3Pl8qj0m7zkCTnDsZ AGn5bv23QzmSiivGNMQFTdY5GfOXngKMxnLY/qhQ597JEciPxAYdidTK7wgq13Sg rlLPbFiB5sSlii7C4r/FtPku9ckcz/qQbXOyAAID4oYX7fW56QBK4x+UdxXE0yYb DQEkza+uCdR+oLrZbTweJXOMcI0BvW/oxOriZdEKfIcC6/ZEPr+X/xSSH+yq9bTH Fmwtcsyk4EAB+IRsUG+z1AIV1uQfFspOohZv+kkJNSkegg+2u7JoDaqLem4/csPf 8QF4b+TkJAn0xk/7rvJN+I6mE5889A== =q8wI -----END PGP SIGNATURE----- --pg7kAYhy6sEi9tXoLrPQVD6McF5JNszXq-- From owner-freebsd-current@freebsd.org Sat Apr 6 13:48:01 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A536155D705 for ; Sat, 6 Apr 2019 13:48:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BD3C809E3 for ; Sat, 6 Apr 2019 13:48:00 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f45.google.com with SMTP id g7so6320744lfh.10 for ; Sat, 06 Apr 2019 06:48:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VsD8LAlTC0TLJsLYXkKE5/PBVDGXpGuSVMRg2l1oC40=; b=Vwdf3p1Cm9dyr40wTCAut1XsEFo6KRxnHJYluFI94agDfQ2WSAZrsDa4P6YYaT75B9 /CesFEU1d9+gj0jjVi/y4e2/bIcM0ZvUVfFg3EL1oTYe5f6Q2bNamFIMODEcxOS2t8aL HdP2uSpZCppwnq84Tbz/+hovlTNyOFga5HrgiRDBZi81eiIJ8iGlHzoLrjeoe+z2AhDH SVH5rlB9d8u/v8kipY6gnPjv4+S22/vjuU9olUgnt2M5RWNeyL7qtzGkMcJW+PM2O23+ ToEQddV3SbvqTmMeIA5c/iAquJ9ZX+p/px50fFOw9oybnBI58ooAFJze6gyq4uO48bau AUmw== X-Gm-Message-State: APjAAAW0z9nguW9D4nmZfyCRY0U/NnznJ0VZY+s7g7kB2wYFlWLaLBso RpZ+8X0EUdL4/dMrMoPUiSOM2qq5Q00wTLvfoXw= X-Google-Smtp-Source: APXvYqxxAkalA+MyPfzEoLGJJTl5/NkWBqqbDIg2hq+ipKONrJp9rYH+ltt4bTVTqNpDthYWEagUvx/NatlWHpYNlGs= X-Received: by 2002:a19:4f44:: with SMTP id a4mr9830119lfk.72.1554557977339; Sat, 06 Apr 2019 06:39:37 -0700 (PDT) MIME-Version: 1.0 References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> In-Reply-To: <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> From: Alan Somers Date: Sat, 6 Apr 2019 07:39:25 -0600 Message-ID: Subject: Re: HEAD'S UP: fusefs sysctls going away To: Marek Zarychta Cc: FreeBSD CURRENT X-Rspamd-Queue-Id: 5BD3C809E3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.90)[-0.899,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 13:48:01 -0000 On Fri, Apr 5, 2019 at 11:48 PM Marek Zarychta < zarychtam@plan-b.pwste.edu.pl> wrote: > > W dniu 21.03.2019 o 17:03, Alan Somers pisze: > > On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb > wrote: > >> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote: > >>> On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb > wrote: > >>>> Hey Alan, > >>>> > >>>> Thank you very much for your work in maintaining fusefs. I only use > >>>> fusefs in very limited circumstances, so take what I'm about to say > >>>> with a grain of salt. > >>>> > >>>> On Thu, Mar 21, 2019 at 09:43:07AM -0600, Alan Somers wrote: > >>>>> fusefs has several sysctl knobs that seem to be workarounds for bugs > >>>>> in particular fuse daemons. However, there is no indication as to > >>>>> which those daemons are, neither in the code nor in SVN. All of the > >>>>> workarounds are at least 6.5 years old, so the original bugs may have > >>>>> been fixed already. Since the original bugs aren't documented, I > >>>>> consider these workarounds to be unmaintainable, and I'm planning to > >>>>> delete them unless anybody objects. Please pipe up if you still use > >>>>> them! > >>>>> > >>>>> vfs.fusefs.mmap_enable: If non-zero, and data_cache_mode is also > >>>>> non-zero, enable mmap(2) of FUSE files > >>>> I'm curious if the security impacts of removing the toggle to disable > >>>> mmap support for fusefs. Is there a per-fusefs replacement for > >>>> mmap_enable? From a security perspective, it would be nice to keep the > >>>> ability to disable mapping of files mounted on a fusefs. > >>> As a matter of fact, there are three other ways to disable mmap: > >>> 1) Set vfs.fusefs.data_cache_mode=0. This completely disables caching > >>> file data, which precludes mmap. > >>> 2) Use the undocumented -o no_datacache mount option, which does the > >>> same thing on a per-mount basis. > >>> 3) Use the undocumented -o no_mmap mount option, which disables mmap > >>> on a per-mount basis. > >> Awesome! I wasn't aware of these. Thanks! > >> > >>> Are you aware of any general security problems with using mmap? > >>> Anything that would apply to fusefs but not other filesystems? > >> Primarily because I trust the filesystems natively implemented in my > >> OS more than I trust some (potentially random) fusefs module. > >> > >> For example, if I'm in a shared hosting environment, implemented with > >> jails, and I let the customer mount a fusefs module in the jail (which > >> is now possible, if I remember right), then I must trust that the > >> module's mmap integration is properly implemented. I'm not sure I > >> personally am okay with that level of trust. > > Ah, well you needn't worry about that. mmap is handled entirely > > within the kernel. The userland fusefs module only sees writes and > > reads. From userland's perspective, the only real difference is that > > mmap()ed writes don't identify the pid of the originating process, > > whereas direct writes do (except when vfs.fusefs.data_cache_mode==2). > > > >> However, the point is moot now that you documented the three ways to > >> disable mmap (two of which work on a per-mount basis). > > After recent changes in fusefs code I am getting such panics regularly > on amd64: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; apic id = 03 > fault virtual address = 0x248 > fault code = supervisor read data , page not present > instruction pointer = 0x20:0xffffffff82d6250c > stack pointer = 0x28:0xfffffe005dc2c630 > frame pointer = 0x28:0xfffffe005dc2c7b0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 2016 (mount_fusefs) > trap number = 12 > panic: page fault > cpuid = 3 > time = 1554528396 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe005dc2c2e0 > vpanic() at vpanic+0x19d/frame 0xfffffe005dc2c330 > panic() at panic+0x43/frame 0xfffffe005dc2c390 > trap_fatal() at trap_fatal+0x394/frame 0xfffffe005dc2c3f0 > trap_pfault() at trap_pfault+0x49/frame 0xfffffe005dc2c450 > trap() at trap+0x29f/frame 0xfffffe005dc2c560 > calltrap() at calltrap+0x8/frame 0xfffffe005dc2c560 > --- trap 0xc, rip = 0xffffffff82d6250c, rsp = 0xfffffe005dc2c630, rbp = > 0xfffffe005dc2c7b0 --- > fuse_vfsop_mount() at fuse_vfsop_mount+0x5dc/frame 0xfffffe005dc2c7b0 > vfs_domount() at vfs_domount+0xace/frame 0xfffffe005dc2c9e0 > vfs_donmount() at vfs_donmount+0x934/frame 0xfffffe005dc2ca80 > sys_nmount() at sys_nmount+0x69/frame 0xfffffe005dc2cac0 > amd64_syscall() at amd64_syscall+0x36e/frame 0xfffffe005dc2cbf0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe005dc2cbf0 > --- syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x8002d510a, rsp = > 0x7fffffffe128, rbp = 0x7fffffffe730 --- > KDB: enter: panic > > Last time I have checked it happened on FreeBSD 13.0-CURRENT #21 > r345948: Fri Apr 5 17:12:53 CEST 2019. > > As a workaround loading fusefs.ko and fuse.ko modules can be disabled. > > -- > Marek Zarychta > Thanks for the bug report. This is probably fixed by r345419 (which hasn't been merged to head yet). If so, then it indicates that your fuse daemon is doing something wrong. What fuse file system are you trying to use, and what command are you using to start it? -Alan From owner-freebsd-current@freebsd.org Sat Apr 6 14:52:52 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53742155FFCB for ; Sat, 6 Apr 2019 14:52:52 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 844A884EE5; Sat, 6 Apr 2019 14:52:51 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from fomalhaut.potoki.eu ([IPv6:2001:470:71:d47:89e0:9791:aa76:705b]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPSA id x36EqjpY026748 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 6 Apr 2019 16:52:46 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1554562366; bh=Tb+5GZ8qOAjnVOeTv3bbK5XHoAHc2+p4LseoHjcBxlM=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=YDn/VmVBEZk1ISEqab7rgq+RVbtU2YxyFGz7re8srvBMy8boLaHFHtimzOS9beIkt 6pXeupr5G+r3rtKGJ5K8+KdwXK4Fe2hPwcAG+m40C4BFuajPibFdD4pMgRKI2omLmS 14JDY465AX3VuFlCc7o3JJxM7a9juP+OhiXF6xB/dvL4u6P1r9p4yr7UTVnzN/m4bk ici6zIeVZqoONeO4xKIlzuCLYV8g+d4EtduYUHQDxHMT13QSGWllagROzKFPF9izIG OKLcA9HvwNCc05Zgu2khQqobDILTOfz8PQ1hsq4NdMj8to4HtCe7WNa5x4fO8U7Dvb kgJXLlGRGqY/Q== X-Authentication-Warning: plan-b.pwste.edu.pl: Host [IPv6:2001:470:71:d47:89e0:9791:aa76:705b] claimed to be fomalhaut.potoki.eu To: Alan Somers Cc: FreeBSD CURRENT References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> From: Marek Zarychta Openpgp: preference=signencrypt Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; prefer-encrypt=mutual; keydata= mQENBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAG0N01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD6JATcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgbkBDQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABiQEf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V65AQ0EV+OTdwEIAMxnGg7OO/ZAnSwiIiABA9lil1Lfa5BWTH3c l1rz4slz7Gw99G9J3bX3FiPA0vU89dgBZ2k0/UVk5cI5EsMAvwJN4bPwRsfBELQqjCKkVZr4 vUeGyvgQ2jnoK1fcEFOnCRdwFy4EJ6Y/fsZCTj4IfQpkM1W7C3KuSGPcjPDA9XCLDjjp8bbA Q9VgQ68MntAnYxMqK0S3CrHp5Pruvb0x4MfFLNwaKtWK+UnJGPT4umj8PMP6XLsFC3g+SGoP aWoYRDI297ZGx4IBWEaJq181oEC5iUQ6WREti9fNQ3TsAB3Q2CjNlkx1geSczIFJSyOHmyJZ RqAocw1sIuPopvhWtR0AEQEAAYkCRAQYAQgADwUCV+OTdwIbAgUJCWYBgAEpCRAdlby8gWmm gsBdIAQZAQgABgUCV+OTdwAKCRB1n+z//VKNLOETCAC3ggwAAQij4hkIxQFapnRuIVb5vq7D AwJ9+Ld5/zYHOj2Tfu+BPSNGzI2edqboz2w1t55UHEYzYDp2axxIfPrZrXsBV4DsjtGwzVV/ jZ9or5qTaYFDEStRkzL4mRpTyYhl/T7GgWpwOJWOih+cU7RWzjSOxiYMi4QSYlkpDUCcZew0 C3HfcxeFqpeL46zgysHC2ptjINXQ+xR2/F6dbed+l7OsvJAfkBqJoQ/48m+8ly1lbViKck7q gWw143ljaKn2qGIjZdb95zcI/CP4L45SXq8NOweACdx2NfUphLrIMbNCqLkMUJcrnruKfbnp C8OMjFJIqlu+PsW593NcZyOugEAH/0cBsDxlSauSVK4kp8ald26pcBI6igNnIMgjaxMiZBjn eoxBiKAOAO93sPnPr9/64CMMwv1T+0vU2lj8SMKOdHVrB9sW/ICGji5skE85xPEAtUkdAQN+ +c2clotujcaj9lBZKJdncKmSxY0SshEa66H+s76u+2Q3jGK6vOrdxakWYCvh2P0/l52Nd/t2 eazLFgwtk5rbo7O0MSC1GNXUsG07vtZ+zxJXFRx7PQ3ZIn0Y4HqwvXUvqgZ9EHiKy8F+ondz 9IS8/Fs81N5ieujHhSWqbaibapnpeDHvT/FWf8iXfJqWq+F7C8lGShSkmsS5AOhB4TNNH5/m ZzECJa1ql64= Subject: Re: HEAD'S UP: fusefs sysctls going away Message-ID: <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> Date: Sat, 6 Apr 2019 16:52:40 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ohzWwbTIzmDnagtZd2tEVBqDygfyRq9uL" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 14:52:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ohzWwbTIzmDnagtZd2tEVBqDygfyRq9uL Content-Type: multipart/mixed; boundary="ZwS85fZQjjVJ0QEDerVC5Ccd6RH7rgOf7"; protected-headers="v1" From: Marek Zarychta To: Alan Somers Cc: FreeBSD CURRENT Message-ID: <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> Subject: Re: HEAD'S UP: fusefs sysctls going away References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> In-Reply-To: --ZwS85fZQjjVJ0QEDerVC5Ccd6RH7rgOf7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US W dniu 06.04.2019 o=C2=A015:39, Alan Somers pisze: > On Fri, Apr 5, 2019 at 11:48 PM Marek Zarychta < > zarychtam@plan-b.pwste.edu.pl> wrote: > >> W dniu 21.03.2019 o 17:03, Alan Somers pisze: >>> On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb >> wrote: >>>> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote: >>>>> On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb >> wrote: >>>>>> Hey Alan, >>>>>> >>>>>> Thank you very much for your work in maintaining fusefs. I only us= e >>>>>> fusefs in very limited circumstances, so take what I'm about to sa= y >>>>>> with a grain of salt. >>>>>> >>>>>> On Thu, Mar 21, 2019 at 09:43:07AM -0600, Alan Somers wrote: >>>>>>> fusefs has several sysctl knobs that seem to be workarounds for b= ugs >>>>>>> in particular fuse daemons. However, there is no indication as t= o >>>>>>> which those daemons are, neither in the code nor in SVN. All of = the >>>>>>> workarounds are at least 6.5 years old, so the original bugs may = have >>>>>>> been fixed already. Since the original bugs aren't documented, I= >>>>>>> consider these workarounds to be unmaintainable, and I'm planning= to >>>>>>> delete them unless anybody objects. Please pipe up if you still = use >>>>>>> them! >>>>>>> >>>>>>> vfs.fusefs.mmap_enable: If non-zero, and data_cache_mode is also >>>>>>> non-zero, enable mmap(2) of FUSE files >>>>>> I'm curious if the security impacts of removing the toggle to disa= ble >>>>>> mmap support for fusefs. Is there a per-fusefs replacement for >>>>>> mmap_enable? From a security perspective, it would be nice to keep= the >>>>>> ability to disable mapping of files mounted on a fusefs. >>>>> As a matter of fact, there are three other ways to disable mmap: >>>>> 1) Set vfs.fusefs.data_cache_mode=3D0. This completely disables ca= ching >>>>> file data, which precludes mmap. >>>>> 2) Use the undocumented -o no_datacache mount option, which does th= e >>>>> same thing on a per-mount basis. >>>>> 3) Use the undocumented -o no_mmap mount option, which disables mma= p >>>>> on a per-mount basis. >>>> Awesome! I wasn't aware of these. Thanks! >>>> >>>>> Are you aware of any general security problems with using mmap? >>>>> Anything that would apply to fusefs but not other filesystems? >>>> Primarily because I trust the filesystems natively implemented in my= >>>> OS more than I trust some (potentially random) fusefs module. >>>> >>>> For example, if I'm in a shared hosting environment, implemented wit= h >>>> jails, and I let the customer mount a fusefs module in the jail (whi= ch >>>> is now possible, if I remember right), then I must trust that the >>>> module's mmap integration is properly implemented. I'm not sure I >>>> personally am okay with that level of trust. >>> Ah, well you needn't worry about that. mmap is handled entirely >>> within the kernel. The userland fusefs module only sees writes and >>> reads. From userland's perspective, the only real difference is that= >>> mmap()ed writes don't identify the pid of the originating process, >>> whereas direct writes do (except when vfs.fusefs.data_cache_mode=3D=3D= 2). >>> >>>> However, the point is moot now that you documented the three ways to= >>>> disable mmap (two of which work on a per-mount basis). >> After recent changes in fusefs code I am getting such panics regularly= >> on amd64: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 3; apic id =3D 03 >> fault virtual address =3D 0x248 >> fault code =3D supervisor read data , page not present >> instruction pointer =3D 0x20:0xffffffff82d6250c >> stack pointer =3D 0x28:0xfffffe005dc2c630 >> frame pointer =3D 0x28:0xfffffe005dc2c7b0 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >> current process =3D 2016 (mount_fusefs) >> trap number =3D 12 >> panic: page fault >> cpuid =3D 3 >> time =3D 1554528396 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> 0xfffffe005dc2c2e0 >> vpanic() at vpanic+0x19d/frame 0xfffffe005dc2c330 >> panic() at panic+0x43/frame 0xfffffe005dc2c390 >> trap_fatal() at trap_fatal+0x394/frame 0xfffffe005dc2c3f0 >> trap_pfault() at trap_pfault+0x49/frame 0xfffffe005dc2c450 >> trap() at trap+0x29f/frame 0xfffffe005dc2c560 >> calltrap() at calltrap+0x8/frame 0xfffffe005dc2c560 >> --- trap 0xc, rip =3D 0xffffffff82d6250c, rsp =3D 0xfffffe005dc2c630, = rbp =3D >> 0xfffffe005dc2c7b0 --- >> fuse_vfsop_mount() at fuse_vfsop_mount+0x5dc/frame 0xfffffe005dc2c7b0 >> vfs_domount() at vfs_domount+0xace/frame 0xfffffe005dc2c9e0 >> vfs_donmount() at vfs_donmount+0x934/frame 0xfffffe005dc2ca80 >> sys_nmount() at sys_nmount+0x69/frame 0xfffffe005dc2cac0 >> amd64_syscall() at amd64_syscall+0x36e/frame 0xfffffe005dc2cbf0 >> fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe005dc= 2cbf0 >> --- syscall (378, FreeBSD ELF64, sys_nmount), rip =3D 0x8002d510a, rsp= =3D >> 0x7fffffffe128, rbp =3D 0x7fffffffe730 --- >> KDB: enter: panic >> >> Last time I have checked it happened on FreeBSD 13.0-CURRENT #21 >> r345948: Fri Apr 5 17:12:53 CEST 2019. >> >> As a workaround loading fusefs.ko and fuse.ko modules can be disabled.= >> >> -- >> Marek Zarychta > Thanks for the bug report. This is probably fixed by r345419 (which ha= sn't > been merged to head yet). If so, then it indicates that your fuse daem= on > is doing something wrong. What fuse file system are you trying to use,= and > what command are you using to start it? > -Alan XFCE4 desktop environment seems to be the culprit of the whole anxiety. It has installed fusefs-libs-2.9.9 as a dependency. I get these panics during the XFCE session startup. Furthermore, I haven't any fusefs packages installed beside mentioned fusefs-libs. --=20 Marek Zarychta --ZwS85fZQjjVJ0QEDerVC5Ccd6RH7rgOf7-- --ohzWwbTIzmDnagtZd2tEVBqDygfyRq9uL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlyovTwACgkQdZ/s//1S jSzwnAgAtdtQBhDSGGVcBFpvR9KPpZqfKwccQzQhUgsfaR0+eFyt3Y3x3iKvEXVF xPIwDoErJF3JskXuKqMJtsGp6/G5ziY5ouqE7RGGVVZByiGUGeW93lQFJsAHV97h c1KBrutXbXfGW9IgAAWp2X2FiM0lrwwnGFKvUYc13urjtMPVtR3j2hiG6MUyOdEi 7LhOJwwg3agxIVyK3RZHfv34n28x0p4wP20qS3Q1iAqP6knzsFDxnKCb29nv6nF4 C0owhUAR+crcqleP2cnAt98e4eTNIF+qbar73Hjvh2oOQIjbf6moJN/pzW7jn4I4 340kdt5CEwHyVvL2JK9vhW00XXelEw== =QyuE -----END PGP SIGNATURE----- --ohzWwbTIzmDnagtZd2tEVBqDygfyRq9uL-- From owner-freebsd-current@freebsd.org Sat Apr 6 15:29:08 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10412156206F for ; Sat, 6 Apr 2019 15:29:08 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 655B685EC4 for ; Sat, 6 Apr 2019 15:29:07 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f173.google.com with SMTP id q66so7670250ljq.7 for ; Sat, 06 Apr 2019 08:29:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8T1kHVjz7G6sNXk0droLCBRXkERQx/Ttps8dx/F2caQ=; b=Jn7Ru+1512m7xZyCrWa7w37k0nesTHktXU+WqgTWqbQH2b/IP23VsvKD8A4UxvKvTN 9wpWmPehyWy9XYKH3G/YhpiXFRzNgvirya6KpT4aEYYl/xVS36BJ9WojixRM3ksUhmZs Pxymqy3bKv5u7Hfldg58QnNaXORkMJlPs2kN4SkuwFoBExq/DBAM6XEMSeEjYUgHsxFU ptUTJzM3nb2bQ0DfbRhd1bDcgQiAACaHDqqxORadnv0XvhXiTsTAsikpAz1LsD3KgoSP GUN0XQPzzjiKLPMgpGBA0SiYP7ehkmdLVtgpUBEKl5/tL0GfHvCu7+IbvdotFHXKa7FR +xFA== X-Gm-Message-State: APjAAAUds5WIx18g93fheUrZwd9dfDmRRTvlz/nI/kavoB/ja3+uANDS 0a58xjESfRuSmH4Fv70C0thLtCZIYpXbB7BcKPI= X-Google-Smtp-Source: APXvYqxjGH8R9tPSajz5NNfCE5XblVx+OC9O8qSQ/ii1yy0SrFC8ThveUp5rcA/ddo1As4xNwMknxWR+6tfMnc0+hyE= X-Received: by 2002:a2e:94c7:: with SMTP id r7mr10270577ljh.91.1554564545490; Sat, 06 Apr 2019 08:29:05 -0700 (PDT) MIME-Version: 1.0 References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> In-Reply-To: <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> From: Alan Somers Date: Sat, 6 Apr 2019 09:28:53 -0600 Message-ID: Subject: Re: HEAD'S UP: fusefs sysctls going away To: Marek Zarychta Cc: FreeBSD CURRENT X-Rspamd-Queue-Id: 655B685EC4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 15:29:08 -0000 On Sat, Apr 6, 2019 at 8:52 AM Marek Zarychta wrote: > > W dniu 06.04.2019 o 15:39, Alan Somers pisze: > > On Fri, Apr 5, 2019 at 11:48 PM Marek Zarychta < > > zarychtam@plan-b.pwste.edu.pl> wrote: > > > >> W dniu 21.03.2019 o 17:03, Alan Somers pisze: > >>> On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb < > shawn.webb@hardenedbsd.org> > >> wrote: > >>>> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote: > >>>>> On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb < > shawn.webb@hardenedbsd.org> > >> wrote: > >>>>>> Hey Alan, > >>>>>> > >>>>>> Thank you very much for your work in maintaining fusefs. I only use > >>>>>> fusefs in very limited circumstances, so take what I'm about to say > >>>>>> with a grain of salt. > >>>>>> > >>>>>> On Thu, Mar 21, 2019 at 09:43:07AM -0600, Alan Somers wrote: > >>>>>>> fusefs has several sysctl knobs that seem to be workarounds for > bugs > >>>>>>> in particular fuse daemons. However, there is no indication as to > >>>>>>> which those daemons are, neither in the code nor in SVN. All of > the > >>>>>>> workarounds are at least 6.5 years old, so the original bugs may > have > >>>>>>> been fixed already. Since the original bugs aren't documented, I > >>>>>>> consider these workarounds to be unmaintainable, and I'm planning > to > >>>>>>> delete them unless anybody objects. Please pipe up if you still > use > >>>>>>> them! > >>>>>>> > >>>>>>> vfs.fusefs.mmap_enable: If non-zero, and data_cache_mode is also > >>>>>>> non-zero, enable mmap(2) of FUSE files > >>>>>> I'm curious if the security impacts of removing the toggle to > disable > >>>>>> mmap support for fusefs. Is there a per-fusefs replacement for > >>>>>> mmap_enable? From a security perspective, it would be nice to keep > the > >>>>>> ability to disable mapping of files mounted on a fusefs. > >>>>> As a matter of fact, there are three other ways to disable mmap: > >>>>> 1) Set vfs.fusefs.data_cache_mode=0. This completely disables > caching > >>>>> file data, which precludes mmap. > >>>>> 2) Use the undocumented -o no_datacache mount option, which does the > >>>>> same thing on a per-mount basis. > >>>>> 3) Use the undocumented -o no_mmap mount option, which disables mmap > >>>>> on a per-mount basis. > >>>> Awesome! I wasn't aware of these. Thanks! > >>>> > >>>>> Are you aware of any general security problems with using mmap? > >>>>> Anything that would apply to fusefs but not other filesystems? > >>>> Primarily because I trust the filesystems natively implemented in my > >>>> OS more than I trust some (potentially random) fusefs module. > >>>> > >>>> For example, if I'm in a shared hosting environment, implemented with > >>>> jails, and I let the customer mount a fusefs module in the jail (which > >>>> is now possible, if I remember right), then I must trust that the > >>>> module's mmap integration is properly implemented. I'm not sure I > >>>> personally am okay with that level of trust. > >>> Ah, well you needn't worry about that. mmap is handled entirely > >>> within the kernel. The userland fusefs module only sees writes and > >>> reads. From userland's perspective, the only real difference is that > >>> mmap()ed writes don't identify the pid of the originating process, > >>> whereas direct writes do (except when vfs.fusefs.data_cache_mode==2). > >>> > >>>> However, the point is moot now that you documented the three ways to > >>>> disable mmap (two of which work on a per-mount basis). > >> After recent changes in fusefs code I am getting such panics regularly > >> on amd64: > >> > >> > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 3; apic id = 03 > >> fault virtual address = 0x248 > >> fault code = supervisor read data , page not present > >> instruction pointer = 0x20:0xffffffff82d6250c > >> stack pointer = 0x28:0xfffffe005dc2c630 > >> frame pointer = 0x28:0xfffffe005dc2c7b0 > >> code segment = base 0x0, limit 0xfffff, type 0x1b > >> = DPL 0, pres 1, long 1, def32 0, gran 1 > >> processor eflags = interrupt enabled, resume, IOPL = 0 > >> current process = 2016 (mount_fusefs) > >> trap number = 12 > >> panic: page fault > >> cpuid = 3 > >> time = 1554528396 > >> KDB: stack backtrace: > >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > >> 0xfffffe005dc2c2e0 > >> vpanic() at vpanic+0x19d/frame 0xfffffe005dc2c330 > >> panic() at panic+0x43/frame 0xfffffe005dc2c390 > >> trap_fatal() at trap_fatal+0x394/frame 0xfffffe005dc2c3f0 > >> trap_pfault() at trap_pfault+0x49/frame 0xfffffe005dc2c450 > >> trap() at trap+0x29f/frame 0xfffffe005dc2c560 > >> calltrap() at calltrap+0x8/frame 0xfffffe005dc2c560 > >> --- trap 0xc, rip = 0xffffffff82d6250c, rsp = 0xfffffe005dc2c630, rbp = > >> 0xfffffe005dc2c7b0 --- > >> fuse_vfsop_mount() at fuse_vfsop_mount+0x5dc/frame 0xfffffe005dc2c7b0 > >> vfs_domount() at vfs_domount+0xace/frame 0xfffffe005dc2c9e0 > >> vfs_donmount() at vfs_donmount+0x934/frame 0xfffffe005dc2ca80 > >> sys_nmount() at sys_nmount+0x69/frame 0xfffffe005dc2cac0 > >> amd64_syscall() at amd64_syscall+0x36e/frame 0xfffffe005dc2cbf0 > >> fast_syscall_common() at fast_syscall_common+0x101/frame > 0xfffffe005dc2cbf0 > >> --- syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x8002d510a, rsp = > >> 0x7fffffffe128, rbp = 0x7fffffffe730 --- > >> KDB: enter: panic > >> > >> Last time I have checked it happened on FreeBSD 13.0-CURRENT #21 > >> r345948: Fri Apr 5 17:12:53 CEST 2019. > >> > >> As a workaround loading fusefs.ko and fuse.ko modules can be disabled. > >> > >> -- > >> Marek Zarychta > > Thanks for the bug report. This is probably fixed by r345419 (which > hasn't > > been merged to head yet). If so, then it indicates that your fuse daemon > > is doing something wrong. What fuse file system are you trying to use, > and > > what command are you using to start it? > > -Alan > > XFCE4 desktop environment seems to be the culprit of the whole anxiety. > It has installed fusefs-libs-2.9.9 as a dependency. I get these panics > during the XFCE session startup. Furthermore, I haven't any fusefs > packages installed beside mentioned fusefs-libs. > > -- > > Marek Zarychta Then the culprit is probably /usr/local/libexec/gvfsd-fuse. But on my XFCE4 system, that command never runs. I don't know why not. Try this patch: https://reviews.freebsd.org/D19836 -Alan From owner-freebsd-current@freebsd.org Sat Apr 6 17:50:34 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A50C1566029 for ; Sat, 6 Apr 2019 17:50:34 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F315D8A7F3; Sat, 6 Apr 2019 17:50:32 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from fomalhaut.potoki.eu ([IPv6:2001:470:71:d47:2df3:7afa:8cde:613c]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPSA id x36HoRw0057664 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 6 Apr 2019 19:50:28 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1554573028; bh=10BdrfN/Xz29R1UIus8ZyQ2aA/5fFcwYLnnxPtyvfPo=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=K6z/wBPML9cmg8x44lmsB3ARwwXaHae/gDkM+GeYU/3J6V80bhPhkWhDsjV3yn8A5 muQvTLUInpAFe7wAXjWZw2ooP4R3KErhp23J1q15AcKJza/6Y7gMBzIsEji/9FIIkn Px1ibLlft75E5DzdLFRcfGF6C5OM/Wrv+muiLxRIUoykdz4NtxeWy1dLVBwweEZ4ca fdDAmlmdlNO++iv0JS9jv5Rst5pZ5EJ9vE09trazeHCveJJ2B2dh0YFdK4QApR4M20 kW04LTT0mNM/QNFeNKxQxUwb7+3joZsAyCCgdeoXRFyIru3oRbjo1TIabzcvcoHpZ5 HcGbuXSD2X43A== X-Authentication-Warning: plan-b.pwste.edu.pl: Host [IPv6:2001:470:71:d47:2df3:7afa:8cde:613c] claimed to be fomalhaut.potoki.eu To: Alan Somers Cc: FreeBSD CURRENT References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> From: Marek Zarychta Openpgp: preference=signencrypt Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; prefer-encrypt=mutual; keydata= mQENBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAG0N01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD6JATcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgbkBDQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABiQEf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V65AQ0EV+OTdwEIAMxnGg7OO/ZAnSwiIiABA9lil1Lfa5BWTH3c l1rz4slz7Gw99G9J3bX3FiPA0vU89dgBZ2k0/UVk5cI5EsMAvwJN4bPwRsfBELQqjCKkVZr4 vUeGyvgQ2jnoK1fcEFOnCRdwFy4EJ6Y/fsZCTj4IfQpkM1W7C3KuSGPcjPDA9XCLDjjp8bbA Q9VgQ68MntAnYxMqK0S3CrHp5Pruvb0x4MfFLNwaKtWK+UnJGPT4umj8PMP6XLsFC3g+SGoP aWoYRDI297ZGx4IBWEaJq181oEC5iUQ6WREti9fNQ3TsAB3Q2CjNlkx1geSczIFJSyOHmyJZ RqAocw1sIuPopvhWtR0AEQEAAYkCRAQYAQgADwUCV+OTdwIbAgUJCWYBgAEpCRAdlby8gWmm gsBdIAQZAQgABgUCV+OTdwAKCRB1n+z//VKNLOETCAC3ggwAAQij4hkIxQFapnRuIVb5vq7D AwJ9+Ld5/zYHOj2Tfu+BPSNGzI2edqboz2w1t55UHEYzYDp2axxIfPrZrXsBV4DsjtGwzVV/ jZ9or5qTaYFDEStRkzL4mRpTyYhl/T7GgWpwOJWOih+cU7RWzjSOxiYMi4QSYlkpDUCcZew0 C3HfcxeFqpeL46zgysHC2ptjINXQ+xR2/F6dbed+l7OsvJAfkBqJoQ/48m+8ly1lbViKck7q gWw143ljaKn2qGIjZdb95zcI/CP4L45SXq8NOweACdx2NfUphLrIMbNCqLkMUJcrnruKfbnp C8OMjFJIqlu+PsW593NcZyOugEAH/0cBsDxlSauSVK4kp8ald26pcBI6igNnIMgjaxMiZBjn eoxBiKAOAO93sPnPr9/64CMMwv1T+0vU2lj8SMKOdHVrB9sW/ICGji5skE85xPEAtUkdAQN+ +c2clotujcaj9lBZKJdncKmSxY0SshEa66H+s76u+2Q3jGK6vOrdxakWYCvh2P0/l52Nd/t2 eazLFgwtk5rbo7O0MSC1GNXUsG07vtZ+zxJXFRx7PQ3ZIn0Y4HqwvXUvqgZ9EHiKy8F+ondz 9IS8/Fs81N5ieujHhSWqbaibapnpeDHvT/FWf8iXfJqWq+F7C8lGShSkmsS5AOhB4TNNH5/m ZzECJa1ql64= Subject: Re: HEAD'S UP: fusefs sysctls going away Message-ID: <22f4bc9d-3068-132c-5ebe-6093cb5ddd04@plan-b.pwste.edu.pl> Date: Sat, 6 Apr 2019 19:50:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="83NNTOYl3OcxJaiJl5yCkagRLXDiUb2BF" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 17:50:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --83NNTOYl3OcxJaiJl5yCkagRLXDiUb2BF Content-Type: multipart/mixed; boundary="wG372Ew6CiD3a87ds51762UchbgqB39cE"; protected-headers="v1" From: Marek Zarychta To: Alan Somers Cc: FreeBSD CURRENT Message-ID: <22f4bc9d-3068-132c-5ebe-6093cb5ddd04@plan-b.pwste.edu.pl> Subject: Re: HEAD'S UP: fusefs sysctls going away References: <20190321154817.2lgwjzl4o2urlmdw@mutt-hbsd> <20190321155922.rdsnvyztssgmms2x@mutt-hbsd> <49723980-27d7-1b2f-e583-5b6c10666ad3@plan-b.pwste.edu.pl> <2ce4c843-745b-76b9-cda9-4c83ab005110@plan-b.pwste.edu.pl> In-Reply-To: --wG372Ew6CiD3a87ds51762UchbgqB39cE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US W dniu 06.04.2019 o=C2=A017:28, Alan Somers pisze: > On Sat, Apr 6, 2019 at 8:52 AM Marek Zarychta > wrote: > >>>> After recent changes in fusefs code I am getting such panics regular= ly >>>> on amd64: >>>> >>>> >>>> Fatal trap 12: page fault while in kernel mode >>>> cpuid =3D 3; apic id =3D 03 >>>> fault virtual address =3D 0x248 >>>> fault code =3D supervisor read data , page not present >>>> instruction pointer =3D 0x20:0xffffffff82d6250c >>>> stack pointer =3D 0x28:0xfffffe005dc2c630 >>>> frame pointer =3D 0x28:0xfffffe005dc2c7b0 >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b >>>> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >>>> current process =3D 2016 (mount_fusefs) >>>> trap number =3D 12 >>>> panic: page fault >>>> cpuid =3D 3 >>>> time =3D 1554528396 >>>> KDB: stack backtrace: >>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >>>> 0xfffffe005dc2c2e0 >>>> vpanic() at vpanic+0x19d/frame 0xfffffe005dc2c330 >>>> panic() at panic+0x43/frame 0xfffffe005dc2c390 >>>> trap_fatal() at trap_fatal+0x394/frame 0xfffffe005dc2c3f0 >>>> trap_pfault() at trap_pfault+0x49/frame 0xfffffe005dc2c450 >>>> trap() at trap+0x29f/frame 0xfffffe005dc2c560 >>>> calltrap() at calltrap+0x8/frame 0xfffffe005dc2c560 >>>> --- trap 0xc, rip =3D 0xffffffff82d6250c, rsp =3D 0xfffffe005dc2c630= , rbp =3D >>>> 0xfffffe005dc2c7b0 --- >>>> fuse_vfsop_mount() at fuse_vfsop_mount+0x5dc/frame 0xfffffe005dc2c7b= 0 >>>> vfs_domount() at vfs_domount+0xace/frame 0xfffffe005dc2c9e0 >>>> vfs_donmount() at vfs_donmount+0x934/frame 0xfffffe005dc2ca80 >>>> sys_nmount() at sys_nmount+0x69/frame 0xfffffe005dc2cac0 >>>> amd64_syscall() at amd64_syscall+0x36e/frame 0xfffffe005dc2cbf0 >>>> fast_syscall_common() at fast_syscall_common+0x101/frame >>>> 0xfffffe005dc2cbf0 >>>> --- syscall (378, FreeBSD ELF64, sys_nmount), rip =3D 0x8002d510a, r= sp =3D >>>> 0x7fffffffe128, rbp =3D 0x7fffffffe730 --- >>>> KDB: enter: panic >>>> >>>> Last time I have checked it happened on FreeBSD 13.0-CURRENT #21 >>>> r345948: Fri Apr 5 17:12:53 CEST 2019. >>>> >>>> As a workaround loading fusefs.ko and fuse.ko modules can be disable= d. >>>> >>>> -- >>>> Marek Zarychta >>> Thanks for the bug report. This is probably fixed by r345419 (which >>> hasn't been merged to head yet). If so, then it indicates that your = fuse daemon >>> is doing something wrong. What fuse file system are you trying to us= e, and >>> what command are you using to start it? >>> -Alan >> XFCE4 desktop environment seems to be the culprit of the whole anxiety= =2E >> It has installed fusefs-libs-2.9.9 as a dependency. I get these panics= >> during the XFCE session startup. Furthermore, I haven't any fusefs >> packages installed beside mentioned fusefs-libs. >> >> -- >> Marek Zarychta > > Then the culprit is probably /usr/local/libexec/gvfsd-fuse. But on my > XFCE4 system, that command never runs. I don't know why not. Try this= > patch: > https://reviews.freebsd.org/D19836 > > -Alan Thank you for the fast-tracked patch. It resolves the issue. I have XFCE4=C2=A0 coexisting with Gnome and some extra,=C2=A0 non-native= disk partitions on this workstation, this is probably the cause that /usr/local/libexec/gvfsd-fuse comes into play. --=20 Marek Zarychta --wG372Ew6CiD3a87ds51762UchbgqB39cE-- --83NNTOYl3OcxJaiJl5yCkagRLXDiUb2BF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlyo5uEACgkQdZ/s//1S jSykWgf/WvMa/4e2tGT7kctw/yNL1bzMrC6IWxfsBtpJTK/do1GI7hQk6SL+gQSv R7/jSxlFxl1VTWPlLpi43/I6pVL9oao6zExXpy2O32LrxgO3x47VOPsCJ2S7azIS tqU0yyydJ5kOweB+moqQ/3Baq+BHk2n+YC3jfrbmL2r9QRne8qJMW7AapHIz/PAL J1gV2QphzVSVA2odYedkn3pf58zdfc37qYTXJOhV7mx8qv+P0wkY70uaKA0w0xUJ MI/4Vbwp/GAiz4kPQ1ymjiGoaowtcOsHbbSniipkB0npqvrJ0VbCcqNyYWmAlHXX vvXTKjYsgmifK109XRz7q7uzajx+kw== =qhDC -----END PGP SIGNATURE----- --83NNTOYl3OcxJaiJl5yCkagRLXDiUb2BF--