From owner-freebsd-current@freebsd.org Sun Feb 4 02:38:30 2018 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 58C81EE0152 for ; Sun, 4 Feb 2018 02:38:30 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E9F6F87FFF for ; Sun, 4 Feb 2018 02:38:29 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AD9C1EE0151; Sun, 4 Feb 2018 02:38:29 +0000 (UTC) Delivered-To: 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 9B6FEEE0150 for ; Sun, 4 Feb 2018 02:38:29 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4EBF487FFE for ; Sun, 4 Feb 2018 02:38:29 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id AABD220D97 for ; Sat, 3 Feb 2018 21:38:22 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Sat, 03 Feb 2018 21:38:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=dbNNIxB9hRTtcnsRlt/kNI8ST0CCZ nTW3Iffvz8ICn8=; b=AGRCGSl1k4Qvc30VMyknhpSW2vE3uXIGQFOq7L8dSDu8Q 8uPqFTk9huttO37PUfW5FkD5l8BaG0+/OkffEk6rmyNnDMbjEXFcgPg9DYEnCPqT BXcg0zokkRuljStePsz7OmW4oywlDQwaIrmutxY/Ws+Iz5fIGCvcT9v7NmynCHVq Uqdt9tsA8vHemXzbLaTuFLzq8dvxyQvoHhKv0Zqox0cp4/0G6QODDynwo1RpvF5A hpwCtlN0HtGq+TyrDc4B5UB2oMtbuHbWO+dN6TMASx2h0Pq0Hbi/mjAU/oOZd9E5 5oqAASoO3uoAfcV7q7e/6DVVyDwQrVoIc3A37hTEA== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 88FB09E47F; Sat, 3 Feb 2018 21:38:22 -0500 (EST) Message-Id: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> From: Josh Paetzel To: current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-fde26eb3 Date: Sat, 03 Feb 2018 20:38:22 -0600 Subject: HEAD amd64 seems unhappy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 02:38:30 -0000 --- all_subdir_lib/libngatm --- /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal se [-Werror,-Wtautological-type-limit-compare] if (portno == 0 || portno > 0xffffffff) ~~~~~~ ^ ~~~~~~~~~~ 1 error generated. *** [cc_port.o] Error code 1 This code hasn't changed in ages so I can only assume it's clang or such. -- Thanks, Josh Paetzel From owner-freebsd-current@freebsd.org Sun Feb 4 11:58:23 2018 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 C48BBECD5B2 for ; Sun, 4 Feb 2018 11:58:23 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 38D707C2C1 for ; Sun, 4 Feb 2018 11:58:22 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w14BwCOm045653; Sun, 4 Feb 2018 20:58:12 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sun, 4 Feb 2018 20:58:12 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: freebsd@grem.de Subject: Re: Lenovo T470s Questions Message-Id: <20180204205812.cac6af308ce1d0de8e711cca@dec.sakura.ne.jp> In-Reply-To: <20180202123847.3cc856ad@bsd64.grem.de> References: <20180202202332.791eef96ccdf40e8a0a2c17d@dec.sakura.ne.jp> <20180202123847.3cc856ad@bsd64.grem.de> Organization: Junchoon corps X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 11:58:24 -0000 Hi, Michael. Noticed your previous post after sending mine. :-) Fallback code for older ThinkPads looks reasonable and gives no new (not known) regression. As I don't have new (0x200) ThinkPads (T420 is my latest), I cannot review and test for new protocol and functionality. Sorry. Just FYI, `acpidump -d -t DSDT | fgrep MHKV` on my T420 claims "Method (MHKV, 0, NotSerialized)" only. So it would go fallback way. Preferrably, user(s) of latest (i.e, T480) models pops in and report this worked or not. [Is there one more protocol like 0x300?] Thanks for your work! On Fri, 2 Feb 2018 12:38:47 +0100 Michael Gmelin wrote: > > > On Fri, 2 Feb 2018 20:23:32 +0900 > Tomoaki AOKI wrote: > > > Not 100% sure but possibly some (one?) EisaId are (is) missing in > > ibm_ids definition of sys/dev/acpi_support/acpi_ibm.c. > > Currently it contains "IBM0068" and "LEN0068". > > > > Run `acpidump -d -t | fgrep EisaId` as root on your T470s and look for > > EisaId something other than... > > > > IBM0068 > > LEN0068 > > IBM3780 > > PNP???? > > > > If there's something new, insert them (it) to > > static char *ibm_ids[] = {"IBM0068", "LEN0068", NULL}; > > line of sys/dev/acpi_support/acpi_ibm.c, between "LEN0068" and "NULL". > > > > If there's none, it's over my hand. :-( > > There could be some incompatibility, like struct member change etc. > > Hi Tomoaki, > > Could you please take a look at this? > > https://reviews.freebsd.org/D14103 > > Thanks, > Michael > > > > > > > See my web page [1] of part "Note for limitations of ACPI in ThinkPad > > T420" and The FreeBSD Forums' thread noted there [2] for more info. > > Although old, but part of them can be useful. > > > > [1] http://www.dec.sakura.ne.jp/~junchoon/machine/freebsd-e.html > > [2] https://forums.freebsd.org/threads/26759/ > > > > > > On Thu, 1 Feb 2018 21:13:05 -0500 > > Bridger Dyson-Smith wrote: > > > > > Hi list and Michael - > > > > > > I received a T470s at work and decided to jump into the CURRENT end > > > of the FreeBSD pool. I have a weird acpi_ibm issue and I'm not sure > > > where to start trying to diagnose the issue. > > > > > > # uname -a > > > FreeBSD spanner 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328126: Thu > > > Jan 18 15:25:44 UTC 2018 root@releng3.nyi.freebsd.org:/ > > > usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > > > > I've loaded acpi_ibm via /boot/loader.conf: > > > acpi_ibm_load="YES" > > > > > > and the module shows as being loaded: > > > # kldstat | grep acpi_ibm > > > 8 1 0xffffffff8278e000 7570 acpi_ibm.ko > > > > > > However, I don't have any of the sysctl knobs available; e.g. > > > # sysctl -a | grep acpi_ibm > > > # > > > > > > or > > > # sysctl dev.acpi_ibm.0.fan_speed > > > sysctl: unknown oid 'dev.acpi_ibm.0.fan_speed' > > > > > > I've (tried) to look through the commit messages on svn-src-head, > > > but I'm not seeing anything specifically related to acpi work, or I > > > just don't know what I'm looking at (a definite possibility). > > > > > > Would someone be able to provide a bit of debugging direction here? > > > Reviewing `dmesg -a` doesn't tell me anything specific about > > > acpi_ibm. > > > > > > Thanks in advance for your time and trouble. > > > Bridger > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > > > "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > -- > Michael Gmelin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Sun Feb 4 09:50:31 2018 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 3DEC5EF2414 for ; Sun, 4 Feb 2018 09:50:31 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9475A761F4 for ; Sun, 4 Feb 2018 09:50:30 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pg0-x234.google.com with SMTP id m136so16186228pga.12 for ; Sun, 04 Feb 2018 01:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qL6dEFLWUdSLK3T1AQUhdpG8W3BRyNcgK8UuUfA2L7Q=; b=OnZF7gneZgLQK8H+b7gNLYhIRysjSDzeQGVl1puyD6nnvYyN60V97SotkX0+r29AqE D78vJj9jkcpxX0NmyEAz1Jyogk8QeHdnSWrYdFqb5ZPu0omo2hevL3pL9tL4A/DeBFtS z3O0dCe4xnVxElxooeyN2OqF/MmPYJHA8hgEmk/XzK4ssWN47pP3UETusa0fY+Z4jtrQ L1w58k35/Pzd+4EglfAbEyj662I+dCuYGH9HFnYHgoDTXPJGVGjfv/7ln9o+VYQannI5 tI8YgIj6xJlwkldPJ3eJsqQdyvzWU8mn8Q7UZzm3RfeoDNJcmqGZslxSd8iJWFAHRH+a QIbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qL6dEFLWUdSLK3T1AQUhdpG8W3BRyNcgK8UuUfA2L7Q=; b=KqAsYfSqgSh3mu9PQjlm8fIRnNpwoZNkWu1omj592KnWwAgR1qWKn+oGsJEniCSLzY NysQ6HROtd2SkvMdT6N7lGuLqorJJvCZrKfSDwaxURFHlBVxEoiKqSLXa9R8vXKYSnyD MlwEOZcS570JSWt6chBpJ94ZMoWLzgnIOkTObhWuvSxlP69Af2fmP3F1rc/U1zpT70bO W6aCRifBmhhHW+xq2+3PzQbCT6Jriakni7s1JcQI1mosS3Ie9J0uC7vvcOn7d3hZT8un 3wv3YtylLDpP2ebwCD3+aMRDN3eiJsS7F0GzzimrQoIaPflblSe8nF9BQpdYdCHiI4Kl qHsg== X-Gm-Message-State: AKwxyteO9usFiqD4E+i456Sv1Tu4tLTVeGOtB+mLJZSJZFeA7t3YOYPf 26cpCO5Yh+AiFyxNsdyAMdv1Bx5TgI/JVxjtHfrUYw== X-Google-Smtp-Source: AH8x225bsxdV1VcpDiAnx0tOrwFUPPtv6mY3i3T0RiLIFfs98CeKe7zMYePxg6ChvojkkEO8XBR2P9G9KTEWvMdne28= X-Received: by 10.101.98.5 with SMTP id d5mr3906781pgv.108.1517737829536; Sun, 04 Feb 2018 01:50:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.138.144 with HTTP; Sun, 4 Feb 2018 01:50:28 -0800 (PST) In-Reply-To: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> From: Maurizio Vairani Date: Sun, 4 Feb 2018 10:50:28 +0100 Message-ID: Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. To: John Nielsen Cc: freebsd-current , Daisuke Aoyama Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 09:50:31 -0000 2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] > > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani > wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 > UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64. > amd64/sys/GENERIC > amd64 > > After compiling the kernel module as discussed in this thread : > https://lists.freebsd.org/pipermail/freebsd-current/ > 2018-January/068272.html > > I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the iSCSI > boot driver version 0.2.13, starts I receive a panic: > https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4 > > Any idea? > > > Bummer! > > Aoyama-san- > > Are you still maintaining isboot? Can you help debug this issue on FreeBSD > 12-CURRENT? > > Once we get it working I will update the port with whatever is needed and > send you the patches in case you'd like to cut a new release. > > Thank you! > I have solved the issue changing the function isboot_ifup() in the source file isboot.c. static int isboot_ifup(struct ifnet *ifp) { struct socket *so; struct ifreq ifr; struct thread *td; int error; td = curthread; error = socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); if (error) { printf("%s: socreate, error=%d\n", __func__, error); return (error); } /* boot NIC */ memset(&ifr, 0, sizeof(ifr)); strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); /* set IFF_UP */ error = ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); if (error) { printf("%s: ifioctl SIOCGIFFLAGS, error=%d\n", __func__, error); return (error); } ifr.ifr_flags |= IFF_UP; error = ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); if (error) { printf("%s, ifioctl SIOCSIFFLAGS, error=%d\n", __func__, error); return (error); } soclose(so); return (0); } I have added a socket in the ifioctl() call as in the /usr/src/sys/nfs/bootp_subr.c source. Please let me know if you prefer a patch. -- Regards, Maurizio From owner-freebsd-current@freebsd.org Sun Feb 4 11:04:02 2018 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 4324AECAA8E for ; Sun, 4 Feb 2018 11:04:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B207F7A47B for ; Sun, 4 Feb 2018 11:04:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.182.56]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfmZs-1eL93q0Yia-00N9Bm; Sun, 04 Feb 2018 12:03:58 +0100 Date: Sun, 4 Feb 2018 12:03:23 +0100 From: "O. Hartmann" To: "Ronald Klop" Cc: Jan =?ISO-8859-1?Q?Kokem=FCller?= , "O. Hartmann" , "FreeBSD Current" Subject: Re: pkg OSVERSION problem Message-ID: <20180204120350.17460aae@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20180127083725.081d5b08@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/lmsyClToDTC=NvA6e5dsvV9"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ms2eSAGxdgVDARL340DhbpeEwvA9XUdtldEr39QzfLqwtcWZtWW XSF7psSyn3UezH6ePmI9l40qV9B6QKH+SV/P0CSoflSoksjgS9IOqjRDmQxdE3w3mAWPJ4k neQ5Fju8H7PfxOcVJsjj2SbKdjK9HzXZBJt9wCWKznCorbxBaPTVhbvR13Mq/2aB900Zhp3 WucS6hgeRmhItjp5YlSPQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:N+DmqOvBvhk=:GECyH+UAcuzzWWvVZ6rdHo IX/JRkH/79/jcfKql1rLXwkfzbao778lZYI7/f3piS2sHY6rZ69HJJGRJpf9NLPIhOQpc1d3r VwCU4PxyQiJveZS/JdQIcK99ViWsNShLrB3QYzyoY3W2/MexDwBCbuVbD1nN1+Po66sYpahPr d4iLZ2v3R9wbN0/6cBTVaHpt2kriAgX0WiPviud2mRsV9dIt3cocxf88TSgnBxUyajklo+cMR XTcfLhvNJprrghtDgtyuewxwO8V3TPLAJDUMHKoLa8itex4iMxf1PGAbTjVjnmZWikpDxiIfz 3Vr9utOTUNBGNHljwTQfPZsdP3Di/m2ufl6EzxXrtUNTNHQoakK9gZkSk4vZJnWi0GUn8PdQB sbAiIi47LCo0jqtNJo2yQdYI1RLz9Qwfoo7Q4fJEqGafQKtkuN7gFfnAJnfiF2xwuq5ZolB0c gU0K78qcvPFEqRN395OnOXyGSI+8rWYY3YRvR6K8Ctyxj2yoNtc54ZadDgyZK8O+Tf46s3KdF JVemope7MmTxM/nruHp+o3shd8/J3bhwUlFqQC2OE3oEl2uG4q2KxQCqArDj1nYdaEKIhhohI 9XfPe4trHiCVshZOz1txLdpH0Sjmg7A4yEZHiF/q/ZAHKQJ9wAW9tPuLBGkC+8RRC6u3AMYxw A9tPKfJ6zudbYpcBHHDTTxudSrs+cPksFp4RZWMt8DOfzQZG52Sem/+0FaibIiJPddERvovOt eV0EvNn8KaIzVU29SeqMDQyp384C7HQ1UzwZHzHokpa0hfWb0uw7ZIX7/pANJ3jYzhuhnniZs 9gfjoaOH94Y8jd7PbiI5yYhrakjbQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 11:04:02 -0000 --Sig_/lmsyClToDTC=NvA6e5dsvV9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sat, 27 Jan 2018 10:23:28 +0100 "Ronald Klop" schrieb: > On Sat, 27 Jan 2018 08:36:58 +0100, O. Hartmann = =20 > wrote: >=20 > > Am Thu, 25 Jan 2018 21:38:27 +0100 > > Jan Kokem=C3=BCller schrieb: > > =20 > >> On 25.01.2018 21:19, Ronald Klop wrote: =20 > >> > I know there should be multiple updates of packages. > >> > Even with -o OSVERSION it does not give any new pkgs anymore. > >> > What will help this? =20 > >> > >> I've just had the same issue and solved it by forcefully updating the > >> package database: > >> > >> # pkg -o OSVERSION=3D1200056 update -f > >> # pkg -o OSVERSION=3D1200056 upgrade > >> > >> > >> -Jan > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to =20 > >> "freebsd-current-unsubscribe@freebsd.org" =20 > > > > Thanks, > > > > I'll give it a try. > > > > regards, > > > > Oliver > > =20 >=20 > Thanks also. It kicked pkg upgrade into upgrading again, but in the end I= =20 > missed libdl.so (clang 6?) which was fixed by updating my system to =20 > 1200056 anyway. Otherwise Firefox wouldn't start. > So although the OSVERSION check is annoying it does warn for actual =20 > problems. >=20 > Regards, > Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I tried and it worked as expected! Thanks a lot. Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/lmsyClToDTC=NvA6e5dsvV9 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWnbolgAKCRDS528fyFhY lOPhAf94JscvN5eiaGDKOIevaZUZLFhmEecydr5bjNrNAU7nbFNKa72CqamN0zei R/lJY+sCEQYV5/IXwkSYZa2yHDKdAf9p53BYMVEb98ZPaI0PDntRf1rmPye4xiAg 1eQ1AW9NFkKJoo8L+oRWwy6q4NAYHv0IPYtc7Rq8sodsUv6+TjDv =n9HI -----END PGP SIGNATURE----- --Sig_/lmsyClToDTC=NvA6e5dsvV9-- From owner-freebsd-current@freebsd.org Sun Feb 4 11:36:39 2018 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 7C219ECC1A7 for ; Sun, 4 Feb 2018 11:36:39 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E05397B5F8; Sun, 4 Feb 2018 11:36:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.182.56]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M8NBi-1eukxx0q02-00vzCS; Sun, 04 Feb 2018 12:31:27 +0100 Date: Sun, 4 Feb 2018 12:30:58 +0100 From: "O. Hartmann" To: "O. Hartmann" Cc: Dimitry Andric , FreeBSD CURRENT Subject: Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11 Message-ID: <20180204123125.58659ccd@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180204122921.28b569e5@thor.intern.walstatt.dynvpn.de> References: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de> <0B0D5F42-8A40-4E00-812C-EFB6556E9444@FreeBSD.org> <0D62F4DB-72A3-4A38-8448-5BE722D75B62@FreeBSD.org> <20180203114352.21de5800@thor.intern.walstatt.dynvpn.de> <60031F9F-5B92-4023-B7AE-484E860F7CD5@FreeBSD.org> <20180204122921.28b569e5@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Ke4AdWPCyDLat5hx/4QK5Ig"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:CXqUWNR1uv0RG7s+TXj61SxuGSvjtiy2Lb6J1/TQEb2fwmsTw6e 11P+irwPO+Obw7Iuhlu0Bn2LEfUF2fSS4u4WX5y4THw0cdG3GSdgfc9b58L9Da4TPJuMgye /8i59/8rqhmHI+7aOd471QwQQJEl7xTZNfrbmvOonFGwfFiYT4SY6QoQJy9L9sQVUoAmfMO JM5m9CINmqUECUygEMnsg== X-UI-Out-Filterresults: notjunk:1;V01:K0:2RzA668MKIg=:Fxy8nq872uZxi1Yayi0VD4 3qUI36jThaYd5u58nPmg1+Y1GVJq0Grts+LC45Ony9DFvGTd4ZJjTh5lCHseOS4WviddhTaPx Iy537p14JIFHJUpy0tONV2kPEDAjQaNv657ue9+cbkBXxl53pC33O3shEY/5wQRyz60PZF5Ox 0LDvF/RZeLskCcdUFT11G186mmEW/D3dDgZ4Notl89gFzjTYOVAZpgthW43J6QCkagcQhU6J4 30B8Pp5ZN3uB2f5liwjoE5G5i1PUhf2CdHmjjk/Woxf8uvsi3IiKTzXK0Kfmu9gMRK8yjmigB fDnzvSIKvIOQL1DbyGKOoG0S30KeX/Cb8F5X6SzS1wSaqgYs1V3NAyG44lh/ToxNkdkeq7Bn6 11PVJvO93p4ywhyj80iOpxR3BtCUoU42Tfdp7C0epmRGjaNi3PFZgmJ4lHRm3SulvBOWAngg4 VavdLJ6CaDhOLgR4JOsK3V7aSvBO7cvFPqcF7a6RKv9Yt1uLDut8QLOrGjp7l6pjxZ9ALPJgc e5jTLr+D25Rnt+z8xLRVR6Ltd2nBwtPG8ZCUj6IA4aqz+KD4XHFKUpe+6Nl11cjrSjDxAfDPT 287PM40KoE5wFBtfvisQYntwQtbJX8BLTuSBXwJCo2i0T08ptDWIZDTyiXVjNzGIuXOqieoNQ 87f1+fWU+pON/D1tTbeqFIfdIPtXL1juV1RnQb1fxiO0XQUh/tcyJSLS3+rC3OgekHGLS8rcy G04tErNtJ5E4NwmJVTUJkvnOShhJKlx2ugAQSpLL8/PR0T0pAMiZZbUC2dhasKKTevXKhi3mL 77J/Kfd2h/Txt5GPpnqbHCvWZXmqQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 11:36:39 -0000 --Sig_/Ke4AdWPCyDLat5hx/4QK5Ig Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 4 Feb 2018 12:28:54 +0100 "O. Hartmann" schrieb: > Am Sat, 3 Feb 2018 14:04:17 +0100 > Dimitry Andric schrieb: >=20 > > On 3 Feb 2018, at 11:43, O. Hartmann wrote: =20 > > >=20 > > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > > Dimitry Andric schrieb: =20 > > >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: = =20 > > >>> On 29 Jan 2018, at 19:39, O. Hartmann wrot= e: =20 > > >>>>=20 > > >>>> Last weekend I updated a CURRENT server to recent CURRENT, > r3284= 00 and > > >>>> performed updates of the ports tree. Since Sunday, I receive segme= natation > > >>>> faults (SIG 11) when accessing the server, especially with setup o= f nextcloud, > > >>>> refdb, phpldapadmin and any other access with LDAP backend (all ht= tps). =20 > > ... =20 > > > Starting program: /usr/local/sbin/httpd -X > > > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 34376777= 728] (2)No such > > > file or directory: AH00075: Failed to enable the 'httpready' Accept F= ilter [Sat Feb > > > 03 11:41:27.704359 2018] [core:warn] [pid 59320:tid 34376777728] (2)N= o such file or > > > directory: AH00075: Failed to enable the 'dataready' Accept Filter [N= ew LWP 101096 > > > of process 59320] [New LWP 101105 of process 59320] [New LWP 101109 o= f process > > > 59320] [New LWP 101103 of process 59320] > > > [New LWP 101102 of process 59320] > > > [New LWP 101110 of process 59320] > > > [New LWP 101107 of process 59320] > > > [New LWP 101098 of process 59320] > > > [New LWP 101099 of process 59320] > > > [New LWP 101108 of process 59320] > > > [New LWP 101112 of process 59320] > > > [New LWP 101101 of process 59320] > > > [New LWP 101104 of process 59320] > > > [New LWP 101097 of process 59320] > > > [New LWP 101106 of process 59320] > > > [New LWP 101111 of process 59320] > > > [New LWP 101100 of process 59320] > > > [LWP 101096 of process 59320 exited] > > >=20 > > > Thread 11 received signal SIGSEGV, Segmentation fault. > > > [Switching to LWP 101108 of process 59320] > > > 0x0000000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opca= che.so =20 > >=20 > > Run the "backtrace" command there, please. If it doesn't give any > > function names, try setting WITH_DEBUG=3D1 in the environment, then > > rebuilding the mod_php56 port (and optionally also the php56 and > > apache24 ports themselves), to add debug info. > >=20 > > -Dimitry > > =20 > www/mod_php56: env WITH_DEBUG=3D1 make reinstall (prior to that, I had to= "pkg delete" the > port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as= recommended > and performing command sequence to enter gdb, run -X, the Apache 2.4 now = crashes > immediately and not when the URL is called by the browser triggering the = fault. This is > what I get then: >=20 > bt > #0 0x000000080208b382 in ?? () from /usr/local/lib/php/20131226-zts/opca= che.so > #1 0x0000000802088e1a in ?? () from /usr/local/lib/php/20131226-zts/opca= che.so > #2 0x0000000802085f12 in ?? () from /usr/local/lib/php/20131226-zts/opca= che.so > #3 0x0000000802085cf3 in zend_accel_script_optimize () > from /usr/local/lib/php/20131226-zts/opcache.so #4 0x000000080207a393 in= ?? () > from /usr/local/lib/php/20131226-zts/opcache.so #5 0x00000008020799d6 in > persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.s= o #6 > 0x000000080195d33c in zend_execute_scripts () > from /usr/local/libexec/apache24/libphp5.so #7 0x00000008018f47a3 in > php_execute_script () from /usr/local/libexec/apache24/libphp5.so #8 > 0x00000008019f1015 in ?? () from /usr/local/libexec/apache24/libphp5.so #9 > 0x00000000002563d7 in ap_invoke_handler () #10 0x000000000029005d in > ap_process_async_request () #11 0x000000000028ca2d in ap_process_http_con= nection () #12 > 0x000000000026e3b7 in ap_run_process_connection () #13 0x000000080152827f= in ?? () > from /usr/local/libexec/apache24/mod_mpm_event.so #14 0x0000000801527e11 = in ?? () > from /usr/local/libexec/apache24/mod_mpm_event.so #15 0x00000008005d2476 = in ?? () > from /lib/libthr.so.3 #16 0x0000000000000000 in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffde1ef000 >=20 >=20 I forgot to mention, that I already have rebuilt www/apache24 via portmaste= r -df and I also have rebuild all php ports/modules installed including php56 itself (b= ut without debugging, it takes a while on that box). --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/Ke4AdWPCyDLat5hx/4QK5Ig Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWnbvDQAKCRDS528fyFhY lI/0Af4jY5ZJw5W603g7++v5YdBgcBjGAhiViwgC1N5CooeL0ZM8c60/q7iozyWP ADAtn4juPgNotdwvPJBQiuglQKswAf0ZtSoLXqpR3W2q/lnQr4XMFvltRrbbr2p4 e5u51HLxBOkqkesb+qxKgYcejyr8mbVoQPIVKOvT91YREIoW2HZN =/K6u -----END PGP SIGNATURE----- --Sig_/Ke4AdWPCyDLat5hx/4QK5Ig-- From owner-freebsd-current@freebsd.org Sun Feb 4 11:29:38 2018 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 6D705ECB78E for ; Sun, 4 Feb 2018 11:29:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2A387B070; Sun, 4 Feb 2018 11:29:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.182.56]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4WNA-1ewOUH3L6i-00yhyZ; Sun, 04 Feb 2018 12:29:29 +0100 Date: Sun, 4 Feb 2018 12:28:54 +0100 From: "O. Hartmann" To: Dimitry Andric Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11 Message-ID: <20180204122921.28b569e5@thor.intern.walstatt.dynvpn.de> In-Reply-To: <60031F9F-5B92-4023-B7AE-484E860F7CD5@FreeBSD.org> References: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de> <0B0D5F42-8A40-4E00-812C-EFB6556E9444@FreeBSD.org> <0D62F4DB-72A3-4A38-8448-5BE722D75B62@FreeBSD.org> <20180203114352.21de5800@thor.intern.walstatt.dynvpn.de> <60031F9F-5B92-4023-B7AE-484E860F7CD5@FreeBSD.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/S0Kf9=GEQH3nRLRd3T1cC1i"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:QDD6uqzS3pO93uGVg0GqEwNZl5M/ksCqiTT4WJEw6PMIC9MjA3J keXjrrOFK4T/UT615ORnJV7bAdq9ShZr8XeZV4PBSfVVPgHocS+wY7URIcLNPVJW0rY/Mcp Jw6tWo+VXhlkAdgqOgFbDfZZ8GjszWBIkB8EqRXDpgjVddzCZZcWEF0TVLhIHr3mAy3vjaD bjUVevU0e55iaEcywcdug== X-UI-Out-Filterresults: notjunk:1;V01:K0:hgaBNPpm7PI=:Q5hw1LeHrDpGwV1ymwGVHT BO6jcL/Y2Yr1+6EtqS6gToYDtrj6rmLLaGZ22cuBtjI3KPJjucYjioFlA8oYXst9QRuIj3iuF H2xCS4l72erv5P4R65thwAJVE9KSlNUwCWsIv65qUFuhkbfVPtxFfQG11FvHtpCeIsz/hPRHF JzRIvCUYpy1BoMN3NCG8qpEvnIdV677cLW7O/zpgGM1KArxmcwLcRvaLe0d+bSJok8qZfzWrJ YVYBL3Cicbd+gooRZfKIdS/f3g9B6pXrmtcK9Ah8QpPlg7zxNYrpZC1Psn/tS28B+gvrqItqZ PZu/uVDY9WrQ+rVd1HHRv0l3EisUIFvhWsVWdvGvO/cnjVx24jUKs3ga0Q7qX5UuuInfT7P+l qKE840HDeXHdJVdKJCPvYHLpr/jDb65aQicoWCjLa7Ts9BnP5TLRzKyMqgP4GggbSvEO80VnF GNhfZolZ6yVRMZd2gj+W4BuSwq+96fzLgjFXlvHRD3GiDDhxDM0puHlnEv4zH0IdCCdcSEDjH JjQyVffjY0BqThB3kTg4+idQ79KfDNkplpQcagf0gkwxMeBo+Qf9MM4zOfHkd7H0eOe4wGEek xAOCG0FwL0HTt7M/PFQ1PG0mW0oamDrNoBDsM98/Js2F8Kdh5fZ1iNsZkZq0seKcy6MbeFAJ9 uzaI05kti4RqpYGdIjIE1GLp9llHuXAFRY2am6RXoGvLCVQtgNF8uSau2XLAh1zXvMgkitlDN 2c7TTX2zofOAFQ4FeA/b61aYaZErWO1Nl7W4H7+PKH/9oOua1M39aksVeGfmSB7ie2WtDQYea lDAVX8We21IY+kXF1EwD1W4okx0fg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 11:29:38 -0000 --Sig_/S0Kf9=GEQH3nRLRd3T1cC1i Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sat, 3 Feb 2018 14:04:17 +0100 Dimitry Andric schrieb: > On 3 Feb 2018, at 11:43, O. Hartmann wrote: > >=20 > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > Dimitry Andric schrieb: =20 > >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: =20 > >>> On 29 Jan 2018, at 19:39, O. Hartmann wrote:= =20 > >>>>=20 > >>>> Last weekend I updated a CURRENT server to recent CURRENT, > r328400= and performed > >>>> updates of the ports tree. Since Sunday, I receive segmenatation fau= lts (SIG 11) > >>>> when accessing the server, especially with setup of nextcloud, refdb= , phpldapadmin > >>>> and any other access with LDAP backend (all https). =20 > ... > > Starting program: /usr/local/sbin/httpd -X > > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437677772= 8] (2)No such > > file or directory: AH00075: Failed to enable the 'httpready' Accept Fil= ter [Sat Feb 03 > > 11:41:27.704359 2018] [core:warn] [pid 59320:tid 34376777728] (2)No suc= h file or > > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New= LWP 101096 of > > process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of pro= cess 59320] > > [New LWP 101103 of process 59320] > > [New LWP 101102 of process 59320] > > [New LWP 101110 of process 59320] > > [New LWP 101107 of process 59320] > > [New LWP 101098 of process 59320] > > [New LWP 101099 of process 59320] > > [New LWP 101108 of process 59320] > > [New LWP 101112 of process 59320] > > [New LWP 101101 of process 59320] > > [New LWP 101104 of process 59320] > > [New LWP 101097 of process 59320] > > [New LWP 101106 of process 59320] > > [New LWP 101111 of process 59320] > > [New LWP 101100 of process 59320] > > [LWP 101096 of process 59320 exited] > >=20 > > Thread 11 received signal SIGSEGV, Segmentation fault. > > [Switching to LWP 101108 of process 59320] > > 0x0000000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcach= e.so =20 >=20 > Run the "backtrace" command there, please. If it doesn't give any > function names, try setting WITH_DEBUG=3D1 in the environment, then > rebuilding the mod_php56 port (and optionally also the php56 and > apache24 ports themselves), to add debug info. >=20 > -Dimitry >=20 www/mod_php56: env WITH_DEBUG=3D1 make reinstall (prior to that, I had to "= pkg delete" the port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as r= ecommended and performing command sequence to enter gdb, run -X, the Apache 2.4 now crashe= s immediately and not when the URL is called by the browser triggering the fault. This is= what I get then: bt #0 0x000000080208b382 in ?? () from /usr/local/lib/php/20131226-zts/opcach= e.so #1 0x0000000802088e1a in ?? () from /usr/local/lib/php/20131226-zts/opcach= e.so #2 0x0000000802085f12 in ?? () from /usr/local/lib/php/20131226-zts/opcach= e.so #3 0x0000000802085cf3 in zend_accel_script_optimize () from /usr/local/lib/php/20131226-zts/opcache.so #4 0x000000080207a393 in ?= ? () from /usr/local/lib/php/20131226-zts/opcache.so #5 0x00000008020799d6 in persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.so = #6 0x000000080195d33c in zend_execute_scripts () from /usr/local/libexec/apach= e24/libphp5.so #7 0x00000008018f47a3 in php_execute_script () from /usr/local/libexec/apache24/libphp5.so #8 0x00000008019f1015 in ?? () from /usr/local/libexec/apache24/libphp5.so #9 0x00000000002563d7 in ap_in= voke_handler () #10 0x000000000029005d in ap_process_async_request () #11 0x000000000028= ca2d in ap_process_http_connection () #12 0x000000000026e3b7 in ap_run_process_conn= ection () #13 0x000000080152827f in ?? () from /usr/local/libexec/apache24/mod_mpm_ev= ent.so #14 0x0000000801527e11 in ?? () from /usr/local/libexec/apache24/mod_mpm_ev= ent.so #15 0x00000008005d2476 in ?? () from /lib/libthr.so.3 #16 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffde1ef000 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/S0Kf9=GEQH3nRLRd3T1cC1i Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWnbukQAKCRDS528fyFhY lJ2TAf9B8STasKLdF3wSp3RzvrAAACftaF1NMbg7w4RfxyTUuDDKmigp42y1X/QF xRrC011bhLamnD/FS0WZtMqWTL4tAf4oyCMXxXE3pjKgTp4Zy+jzYB4dmlinU/D5 fWksN0TluH3YBbNOhPWhRS9glgo0fiJfxx04o73/Nn+sWMjN3hoU =UvJd -----END PGP SIGNATURE----- --Sig_/S0Kf9=GEQH3nRLRd3T1cC1i-- From owner-freebsd-current@freebsd.org Sun Feb 4 10:24:42 2018 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 E7BC4EC9270 for ; Sun, 4 Feb 2018 10:24:41 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7FBB278CD6 for ; Sun, 4 Feb 2018 10:24:41 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 36FE9EC926F; Sun, 4 Feb 2018 10:24:41 +0000 (UTC) Delivered-To: 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 25964EC926E for ; Sun, 4 Feb 2018 10:24:41 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADABB78CD4; Sun, 4 Feb 2018 10:24:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A0EF81929B; Sun, 4 Feb 2018 11:24:38 +0100 (CET) From: Dimitry Andric Message-Id: <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_DF557A53-CC05-44FB-9366-F2492FC3A1E9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: HEAD amd64 seems unhappy Date: Sun, 4 Feb 2018 11:24:38 +0100 In-Reply-To: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> Cc: current@freebsd.org To: Josh Paetzel References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 10:24:42 -0000 --Apple-Mail=_DF557A53-CC05-44FB-9366-F2492FC3A1E9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 4 Feb 2018, at 03:38, Josh Paetzel wrote: >=20 > --- all_subdir_lib/libngatm --- > /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result = of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal > se [-Werror,-Wtautological-type-limit-compare] > if (portno =3D=3D 0 || portno > 0xffffffff) > ~~~~~~ ^ ~~~~~~~~~~ > 1 error generated. > *** [cc_port.o] Error code 1 >=20 > This code hasn't changed in ages so I can only assume it's clang or = such. This is because of r328816, which requires you to update your toolchain to at least r328381. E.g. please run either "make buildworld" or "make kernel-toolchain" before building your kernel. -Dimitry --Apple-Mail=_DF557A53-CC05-44FB-9366-F2492FC3A1E9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWnbfZgAKCRCwXqMKLiCW o6R6AKDsGO9a094ebMq7ncySvTpKhGPhhQCgjIzee046HDBqAWqEEbEwu1gTCM4= =7ygF -----END PGP SIGNATURE----- --Apple-Mail=_DF557A53-CC05-44FB-9366-F2492FC3A1E9-- From owner-freebsd-current@freebsd.org Sun Feb 4 13:46:13 2018 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 AEE89ED73D2 for ; Sun, 4 Feb 2018 13:46:13 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34A28804C2 for ; Sun, 4 Feb 2018 13:46:13 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f45.google.com with SMTP id g72so38063632lfg.5 for ; Sun, 04 Feb 2018 05:46:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NQavAe8km00cCBsesec+4giIsb43QM3FcdWSmcnlMiY=; b=YABsWze33agJg6dlGZNB6xQR53XLm4GRCF/DKzY/SGC04xA4/7HdjOMogMeJbv6RZd jU3Z4+mMLUio3Y1fcerFn/Pje2R3ITbhWcU72b/UfWLeCi/N5AHRz+2IuhjPzR7cGgFe Gy28wlUQVR45nM32FVDSeZy0f/Ck6sQi/oBblo2cbAu6W+L0uZ9KyC6DzeDbVSXs/4CS 9P5OG1SLuH4cqgyLQe47LApvfjg1mjYEIU/KDNBpjO86GInwVoX+9wUlTtXY86X6dvJa iZDy27gwHwbvIc37Qs9a39cEUCsJ1EEXe0870gRAnjQ8qox7p9pEWHh6V55ujBvg1HqP w4aw== X-Gm-Message-State: AKwxytejrUFmDxkc++IeGra5RYBgarOy9qFb45ylteVkAni8U63xKYks FcJ4o1iTQV6r8EIvwroz4ZPoNcuh X-Google-Smtp-Source: AH8x2268ekGPCApUunGw2jb9L5V+NbYnVrAx2xhtbAG560ZuTGdnO/SElbQ11AUL5nVSDja9qlsGCg== X-Received: by 10.46.99.202 with SMTP id s71mr13900861lje.143.1517751620055; Sun, 04 Feb 2018 05:40:20 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id i18sm1354371ljd.27.2018.02.04.05.40.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Feb 2018 05:40:19 -0800 (PST) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. To: Maurizio Vairani Cc: freebsd-current References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> From: Andriy Gapon Message-ID: <8349653f-fe9a-a896-48f5-325738d7bd8e@FreeBSD.org> Date: Sun, 4 Feb 2018 15:40:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 13:46:13 -0000 On 04/02/2018 11:50, Maurizio Vairani wrote: > I have added a socket in the ifioctl() call as in the > /usr/src/sys/nfs/bootp_subr.c source. > Please let me know if you prefer a patch. A patch here https://reviews.freebsd.org/ would be the best. -- Andriy Gapon From owner-freebsd-current@freebsd.org Sun Feb 4 13:15:50 2018 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 81913ED35BC for ; Sun, 4 Feb 2018 13:15:50 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0AAF27EE65 for ; Sun, 4 Feb 2018 13:15:50 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id B6151ED35B8; Sun, 4 Feb 2018 13:15:49 +0000 (UTC) Delivered-To: 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 A4170ED35B7 for ; Sun, 4 Feb 2018 13:15:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 E6EAE7EE60; Sun, 4 Feb 2018 13:15:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w14DFkGr002491; Sun, 4 Feb 2018 13:15:46 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w14DFkrE002490; Sun, 4 Feb 2018 05:15:46 -0800 (PST) (envelope-from david) Date: Sun, 4 Feb 2018 05:15:46 -0800 From: David Wolfskill To: Josh Paetzel Cc: current@freebsd.org Subject: Re: HEAD amd64 seems unhappy Message-ID: <20180204131546.GG1178@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Josh Paetzel , current@freebsd.org References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4ndw/alBWmZEhfcZ" Content-Disposition: inline In-Reply-To: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 13:15:50 -0000 --4ndw/alBWmZEhfcZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 03, 2018 at 08:38:22PM -0600, Josh Paetzel wrote: > --- all_subdir_lib/libngatm --- > /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of = comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal > se [-Werror,-Wtautological-type-limit-compare] > if (portno =3D=3D 0 || portno > 0xffffffff) > ~~~~~~ ^ ~~~~~~~~~~ > 1 error generated. > *** [cc_port.o] Error code 1 >=20 > This code hasn't changed in ages so I can only assume it's clang or such. > .... My update of head/amd64 from r328830 to r328838 was rather quick and quite painless this morning (00:05:15 elapsed time... on my laptop; build machine was < 00:05:00, as I didn't need to re-authenticate to sudo for the shutdown). So: I didn't see the issue. Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --4ndw/alBWmZEhfcZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlp3B4JfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7heQhQf+P0yORKz4P5Vftu5kC0JIzT81dkHpra6lymE8ZLH8VCfcgtrV4ash1+qu xY5Q7vVcLXQXoKxEJDCBbaGf4YpQIdjFxlhM/4N8DN7jENXvOQh4YkTZuavl4tNH S61nofwOd/ivxpnb545goSgS8madOzql3QKFCZnuRjJK7go4xhzEga2Cf9lZI5iO pu17anCv4O/eUupO4bP5PWSc9PaalJAIdLCZcASD+PNjwmtphC4TIHCa4iTm0Nzd 1B0I/cdsnUMgH4ovOtwF6DttLX4f8h+CtQp7aP5KV1rLGZ7TTVLvj1I0m1tYxwg6 v8TY7YYsTaQiZAekPYk5OH6x+cVjPQ== =I+TF -----END PGP SIGNATURE----- --4ndw/alBWmZEhfcZ-- From owner-freebsd-current@freebsd.org Sun Feb 4 12:36:40 2018 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 4C2D6ECEF57 for ; Sun, 4 Feb 2018 12:36:40 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A70CE7D817 for ; Sun, 4 Feb 2018 12:36:39 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.182.56]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MFcg9-1eUEe81elx-00Ea6j; Sun, 04 Feb 2018 13:36:37 +0100 Date: Sun, 4 Feb 2018 13:36:09 +0100 From: "O. Hartmann" To: Vladimir Zakharov Cc: "O. Hartmann" , freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180204133636.763674ee@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180203111733.7d64a066@thor.intern.walstatt.dynvpn.de> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <20180202063755.02aa231a@freyja.zeit4.iv.bundesimmobilien.de> <20180203081053.rxyog5iewqrjezp6@vzakharov> <20180203111733.7d64a066@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/XFIWuW58k/lP6zfr3+jc1St"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:RKognzXaiQiiT4AKq2/LBMG6LOekHlOlWsB742JnxbckUryM1gf Fw0NQDcskwvytvuWESGmAmWC7Z7weA/Obmq+xE15YGjSqnxj1piF+7xtEXilEq9YZUhpbbD aJH8+OdrTVBi2GghufWlQpG2kTrTk8ikJnndgDvqfORn4G32NOF6iC5WChMIlzfQ+S8rvsq OoT0bCoiyXG6wLYYSp5Og== X-UI-Out-Filterresults: notjunk:1;V01:K0:8tL3fSCq+jI=:Jn8IGbalaiuqsYnKfmkzkd 2RtNsbGw1721U50Ce5Wuf36Rn+zCHw+YQyhp2UpA+oc8OloADsOz1xeIW43yXDaCNIiXunWQ1 Q2nkYY0WJk47/Nwutg4fWZnNg49vFdmJ0r6nYFkJO0Vg4HObuWsR3hustbPWvJbYJgv12k7PL UNCalX4SihCHxVXBAcd+rngcku92/rimztO1cBEH5aK27kwO9Rr0aOvgr8vJGiMsaGizQjSmW UsGbqwFnegiQGy/T7TON8H9+spxm1BHNni/974UiYWphqIr4/EjOmqPTPehn1u0429ezsQN7N hF7cpJ2JB3AOBQoz+cdsI2pqt9g0thPU6nmv23/lB8fzdMrOpSWqeQsnPBFbkCP0TuSpTYZWj Yte/8zf0qhNb4j69xYKKC3wXh+2owzguLrNrcNTpQBGaSigvjZzPDRlv3ty+oJuhpcZarhkch P1ZegQmy1o52wbVgg2vCHwZmvqUBLiETq/qoC2Or35HR2o2EzKfrHj7mm7948KZaSpFZ4EJxn bJlasB35y/o9Xxrux3JO2GdyoX06egGazVkkpHO3nE9XK01f0UNi0Jin0wI1qpQnyyt3K2LIf VlwC69qoI+PG4MYAzuGwg7CUD7OeYq/0ZZckBJqjyoBHlAhSosEgo6ouv8GGMRGh5f15Dr4+v pBHIdk6tmsPb55wfUvZZ8O67NljQg6XYc+7/3RepWhzKUe+AaxBpyRIyinjVBrD6/wBXVRUDy 49rp1hsbBWkcSKjGFjIjxNx2m1mzhUoA65lHXllXTzgIJZPqktF0du0J0r/KFn1UhthLh9hyj YyX2X1Sl+MHgdfG5nQCfqJw9nS97Q== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 12:36:40 -0000 --Sig_/XFIWuW58k/lP6zfr3+jc1St Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sat, 3 Feb 2018 11:17:06 +0100 "O. Hartmann" schrieb: > Am Sat, 3 Feb 2018 11:10:53 +0300 > Vladimir Zakharov schrieb: >=20 > > Hello, Oliver! > >=20 > > On Fri, Feb 02, 2018, O. Hartmann wrote: =20 > > > On Thu, 1 Feb 2018 12:10:30 +0300 > > > Vladimir Zakharov wrote: > > > =20 > > > > Hello! > > > >=20 > > > > For some time (about a week) building and installing kernel fails w= ith > > > > the error "Variable OBJTOP is recursive." when going to build/insta= ll > > > > module from ports. > > > >=20 > > > > Last successful build was at r328426. Next build at r328527 failed = and > > > > still broken at r328649. > > > >=20 > > > > Without PORTS_MODULES building and installing kernel succeeds. Anot= her > > > > workaround: ignore error and build/install module directly from por= ts. > > > > =20 > > >=20 > > > I have had the very same issue! > > >=20 > > > You need to perform a "installworld" first (just comment out the PORT= S_MODULES=3D > > > parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel = (maybe not > > > a full buildworld, but I do not know the state of your source tree) a= nd perform > > > a regular installation of the world. It could be something easier by= direkctly > > > install-only the mk-portions, but recently, some changes to world (LL= VM) made > > > it worth anyway to buildworld. > > >=20 > > > As recommended by others earlier on this list according to this subje= ct, this > > > procedure makes the problem go away. =20 > >=20 > > Thanks for your answer. Unfortunately, this didn't help. > > =20 >=20 > You are correct! I made a mistake and had the portions still commented ou= t. I'm very > sorry. >=20 > This remains a bug! >=20 This problem has been introduced with svn commit: r328489 - head/sys/conf The the appropriate list for reference. oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/XFIWuW58k/lP6zfr3+jc1St Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWnb+VAAKCRDS528fyFhY lKF8Af9vp6J+8VrgGYbjOGqT7piENETH1XiS0qjd80bnbxOrbPDWVeUzzA4fbU3T ZM9WLWRe2G5U+WGCYYLFgWUEdDRoAf0UfATXJ5Kqw3nTrXfmyMTvwz/CdsO+LmcE FXAyK+sz87D1Z4DinDbkdbqvQZxGdw9CAfqWYEh+JP+V75LlfpaK =I86M -----END PGP SIGNATURE----- --Sig_/XFIWuW58k/lP6zfr3+jc1St-- From owner-freebsd-current@freebsd.org Sun Feb 4 10:48:13 2018 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 A78F4ECA23A for ; Sun, 4 Feb 2018 10:48:13 +0000 (UTC) (envelope-from taav@protonmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 428A0797B8 for ; Sun, 4 Feb 2018 10:48:13 +0000 (UTC) (envelope-from taav@protonmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id F3B36ECA22E; Sun, 4 Feb 2018 10:48:12 +0000 (UTC) Delivered-To: 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 E2548ECA22D for ; Sun, 4 Feb 2018 10:48:12 +0000 (UTC) (envelope-from taav@protonmail.com) Received: from mail3.protonmail.ch (mail3.protonmail.ch [185.70.40.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EEA6797B7 for ; Sun, 4 Feb 2018 10:48:11 +0000 (UTC) (envelope-from taav@protonmail.com) Date: Sun, 04 Feb 2018 05:47:58 -0500 To: "current@freebsd.org" From: Taavi Reply-To: Taavi Subject: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes Message-ID: <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5FMckEUyrF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=@protonmail.com> Feedback-ID: DE6O6gJFyPb0hA7-V94Wt75T4HquYkFeRTcwrdLs1TBZ4KxqXiHBLQzVbD_COG_zInavwSAKPkGJOuM7R7l3xQ==:Ext:ProtonMail MIME-Version: 1.0 X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-Mailman-Approved-At: Sun, 04 Feb 2018 18:00:59 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 10:48:13 -0000 c2VlIHN1YmplY3QKCnRoYW5rIHlvdQp0CgpTZW50IHdpdGggW1Byb3Rvbk1haWxdKGh0dHBzOi8v cHJvdG9ubWFpbC5jb20pIFNlY3VyZSBFbWFpbC4= From owner-freebsd-current@freebsd.org Sun Feb 4 18:19:39 2018 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 7D698EE69AB for ; Sun, 4 Feb 2018 18:19:39 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 156936B951 for ; Sun, 4 Feb 2018 18:19:39 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id C8100EE69A0; Sun, 4 Feb 2018 18:19:38 +0000 (UTC) Delivered-To: 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 B4CB2EE699F for ; Sun, 4 Feb 2018 18:19:38 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (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 47E2F6B950 for ; Sun, 4 Feb 2018 18:19:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id iOsyes7HiJZWxiOt0eZ6v1; Sun, 04 Feb 2018 11:19:30 -0700 X-Authority-Analysis: v=2.3 cv=D6Jp1MZj c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=Op4juWPpsa0A:10 a=sfOm8-O8AAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=UipU2NSKCdVe5ZQeNEcA:9 a=CjuIK1q_8ugA:10 a=TvTJqdcANYtsRzA46cdi:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 868BCC2; Sun, 4 Feb 2018 10:19:28 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w14IJSpB003915; Sun, 4 Feb 2018 10:19:28 -0800 (PST) (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 w14IJSFi003912; Sun, 4 Feb 2018 10:19:28 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201802041819.w14IJSFi003912@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 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Taavi cc: "current@freebsd.org" Subject: Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes In-Reply-To: Message from Taavi of "Sun, 04 Feb 2018 05:47:58 -0500." <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5FMckEUyrF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Feb 2018 10:19:28 -0800 X-CMAE-Envelope: MS4wfHQqGcCSX0yFWJ9LdQiyWTPUEyfaXHh9GHbgnefSOa9pilKwfz333ntK2lSLCacaKDHZOB2LahCByiisXVytdVGsqOcK7kufT5zKdnhnjvobBTvsrji4 jOFxCRjvwmQRLIvxXtnQ+2HVRSNZ6uKuOXowHmLIgPZytmWHELFhrxhTuOGJre1ymZ/jSK4oavM7o6hOStNT0rEPNdD9tYFCH0U= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 18:19:39 -0000 In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5 FMckEUy rF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=@protonmail.com>, Taavi writes: > see subject Try rebuilding and reinstalling virtualbox-ose-kmod. -- 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 Sun Feb 4 19:36:30 2018 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 4D4A9EEBC2D for ; Sun, 4 Feb 2018 19:36:30 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D1E916EBFB for ; Sun, 4 Feb 2018 19:36:29 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: by mailman.ysv.freebsd.org (Postfix) id 8E3E5EEBC20; Sun, 4 Feb 2018 19:36:29 +0000 (UTC) Delivered-To: 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 7C278EEBC1C for ; Sun, 4 Feb 2018 19:36:29 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from mail.srv.hagen.coffee (brews.the.best.midnight.coffee [176.9.40.102]) by mx1.freebsd.org (Postfix) with ESMTP id 184386EBF8 for ; Sun, 4 Feb 2018 19:36:28 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from localhost (HSI-KBW-37-49-77-182.hsi14.kabel-badenwuerttemberg.de [37.49.77.182]) by mail.srv.hagen.coffee (Postfix) with ESMTPSA id 8F68A18E10 for ; Sun, 4 Feb 2018 20:34:17 +0100 (CET) Date: Sun, 4 Feb 2018 20:36:15 +0100 From: Stefan Hagen To: current@freebsd.org Subject: Re: HEAD amd64 seems unhappy Message-ID: <20180204193614.GA70927@ptrace.hagen.corp> References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> Precedence: first-class Priority: normal X-Editor: VIM - Vi IMproved 8.0 X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-Mailer: Mutt 1.9.2 (2017-12-15) X-GPG: 0x883FCC91 OpenPGP: url=https://pgp.ptrace.org; id=883FCC91 User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2018 19:36:30 -0000 > Dimitry Andric wrote: >On 4 Feb 2018, at 03:38, Josh Paetzel wrote: >> >> --- all_subdir_lib/libngatm --- >> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal >> se [-Werror,-Wtautological-type-limit-compare] >> if (portno == 0 || portno > 0xffffffff) >> ~~~~~~ ^ ~~~~~~~~~~ >> 1 error generated. >> *** [cc_port.o] Error code 1 >> >> This code hasn't changed in ages so I can only assume it's clang or such. > >This is because of r328816, which requires you to update your toolchain >to at least r328381. E.g. please run either "make buildworld" or "make >kernel-toolchain" before building your kernel. I get the same error. It actually comes up at "make buildworld". Running "make kernel-toolchain" before did not help. I'm on r328860. Best Regards, Stefan From owner-freebsd-current@freebsd.org Sun Feb 4 19:59:27 2018 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 4EC4CEED48E for ; Sun, 4 Feb 2018 19:59:27 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E14C96FA35 for ; Sun, 4 Feb 2018 19:59:26 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A5AF5EED48D; Sun, 4 Feb 2018 19:59:26 +0000 (UTC) Delivered-To: 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 93295EED48C for ; Sun, 4 Feb 2018 19:59:26 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B0586FA32; Sun, 4 Feb 2018 19:59:26 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [IPv6:2003:cd:6bf1:8000:d4f2:3e86:bbdf:e6fb] (p200300CD6BF18000D4F23E86BBDFE6FB.dip0.t-ipconnect.de [IPv6:2003:cd:6bf1:8000:d4f2:3e86:bbdf:e6fb]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id A10D7721E281A; Sun, 4 Feb 2018 20:59:17 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: HEAD amd64 seems unhappy From: Michael Tuexen In-Reply-To: <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> Date: Sun, 4 Feb 2018 20:59:14 +0100 Cc: Josh Paetzel , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <03D56DEA-D965-46F8-9F61-10DCCCBC3B28@freebsd.org> References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 19:59:27 -0000 > On 4. Feb 2018, at 11:24, Dimitry Andric wrote: >=20 > On 4 Feb 2018, at 03:38, Josh Paetzel wrote: >>=20 >> --- all_subdir_lib/libngatm --- >> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result = of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal >> se [-Werror,-Wtautological-type-limit-compare] >> if (portno =3D=3D 0 || portno > 0xffffffff) >> ~~~~~~ ^ ~~~~~~~~~~ >> 1 error generated. >> *** [cc_port.o] Error code 1 >>=20 >> This code hasn't changed in ages so I can only assume it's clang or = such. >=20 > This is because of r328816, which requires you to update your = toolchain > to at least r328381. E.g. please run either "make buildworld" or = "make > kernel-toolchain" before building your kernel. I get this error when doing a buildworld... Using r328861. Best regards Michael >=20 > -Dimitry >=20 From owner-freebsd-current@freebsd.org Sun Feb 4 20:40:30 2018 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 788BAEF001D for ; Sun, 4 Feb 2018 20:40:30 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 08FAE71324 for ; Sun, 4 Feb 2018 20:40:30 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AECEBEF001C; Sun, 4 Feb 2018 20:40:29 +0000 (UTC) Delivered-To: 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 95CF8EF001B for ; Sun, 4 Feb 2018 20:40:29 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FBC37131D; Sun, 4 Feb 2018 20:40:28 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 5AA5B192DF; Sun, 4 Feb 2018 21:40:20 +0100 (CET) From: Dimitry Andric Message-Id: <76A6BFDB-7A96-4EF4-B218-0163CDD3F9BC@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_993E813C-283B-49C3-B869-1AD80F8B4A71"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: HEAD amd64 seems unhappy Date: Sun, 4 Feb 2018 21:40:19 +0100 In-Reply-To: <03D56DEA-D965-46F8-9F61-10DCCCBC3B28@freebsd.org> Cc: Josh Paetzel , current@freebsd.org To: Michael Tuexen References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> <03D56DEA-D965-46F8-9F61-10DCCCBC3B28@freebsd.org> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 20:40:30 -0000 --Apple-Mail=_993E813C-283B-49C3-B869-1AD80F8B4A71 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 4 Feb 2018, at 20:59, Michael Tuexen wrote: >=20 >> On 4. Feb 2018, at 11:24, Dimitry Andric wrote: >> On 4 Feb 2018, at 03:38, Josh Paetzel wrote: >>>=20 >>> --- all_subdir_lib/libngatm --- >>> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: = result of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always = fal >>> se [-Werror,-Wtautological-type-limit-compare] >>> if (portno =3D=3D 0 || portno > 0xffffffff) >>> ~~~~~~ ^ ~~~~~~~~~~ >>> 1 error generated. >>> *** [cc_port.o] Error code 1 >>>=20 >>> This code hasn't changed in ages so I can only assume it's clang or = such. >>=20 >> This is because of r328816, which requires you to update your = toolchain >> to at least r328381. E.g. please run either "make buildworld" or = "make >> kernel-toolchain" before building your kernel. > I get this error when doing a buildworld... Using r328861. This should now be fixed by r328863. The MK_SYSTEM_COMPILER logic did not build a cross-tools toolchain, so you were still getting warnings from the (old) compiler in your base system. -Dimitry --Apple-Mail=_993E813C-283B-49C3-B869-1AD80F8B4A71 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWndvswAKCRCwXqMKLiCW o0yeAJ4qMMrd+sdPopg4Oj2SPmg0MErjDwCdGAtn867/ys3pZg6Lu+ChzIaGOCo= =39uA -----END PGP SIGNATURE----- --Apple-Mail=_993E813C-283B-49C3-B869-1AD80F8B4A71-- From owner-freebsd-current@freebsd.org Sun Feb 4 21:54:47 2018 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 61837ED0230 for ; Sun, 4 Feb 2018 21:54:47 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F2E9C74271 for ; Sun, 4 Feb 2018 21:54:46 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B3592ED022A; Sun, 4 Feb 2018 21:54:46 +0000 (UTC) Delivered-To: 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 A1105ED0229 for ; Sun, 4 Feb 2018 21:54:46 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C8817426C; Sun, 4 Feb 2018 21:54:46 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [IPv6:2003:cd:6bf1:8000:d4f2:3e86:bbdf:e6fb] (p200300CD6BF18000D4F23E86BBDFE6FB.dip0.t-ipconnect.de [IPv6:2003:cd:6bf1:8000:d4f2:3e86:bbdf:e6fb]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 77B3D721E281A; Sun, 4 Feb 2018 22:54:44 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: HEAD amd64 seems unhappy From: Michael Tuexen In-Reply-To: <76A6BFDB-7A96-4EF4-B218-0163CDD3F9BC@FreeBSD.org> Date: Sun, 4 Feb 2018 22:54:41 +0100 Cc: Josh Paetzel , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <11E28CCA-1F02-431E-ABA6-C478537C797B@freebsd.org> References: <1517711902.3429873.1258647112.4DA64BE7@webmail.messagingengine.com> <1941B8EC-88AA-4B11-AE0E-BED6B0428475@FreeBSD.org> <03D56DEA-D965-46F8-9F61-10DCCCBC3B28@freebsd.org> <76A6BFDB-7A96-4EF4-B218-0163CDD3F9BC@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 04 Feb 2018 21:54:47 -0000 > On 4. Feb 2018, at 21:40, Dimitry Andric wrote: >=20 > On 4 Feb 2018, at 20:59, Michael Tuexen wrote: >>=20 >>> On 4. Feb 2018, at 11:24, Dimitry Andric wrote: >>> On 4 Feb 2018, at 03:38, Josh Paetzel wrote: >>>>=20 >>>> --- all_subdir_lib/libngatm --- >>>> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: = result of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always = fal >>>> se [-Werror,-Wtautological-type-limit-compare] >>>> if (portno =3D=3D 0 || portno > 0xffffffff) >>>> ~~~~~~ ^ ~~~~~~~~~~ >>>> 1 error generated. >>>> *** [cc_port.o] Error code 1 >>>>=20 >>>> This code hasn't changed in ages so I can only assume it's clang or = such. >>>=20 >>> This is because of r328816, which requires you to update your = toolchain >>> to at least r328381. E.g. please run either "make buildworld" or = "make >>> kernel-toolchain" before building your kernel. >> I get this error when doing a buildworld... Using r328861. >=20 > This should now be fixed by r328863. The MK_SYSTEM_COMPILER logic did > not build a cross-tools toolchain, so you were still getting warnings > from the (old) compiler in your base system. I can confirm that it works now. Thanks for the quick fix! Best regards Michael >=20 > -Dimitry >=20 From owner-freebsd-current@freebsd.org Mon Feb 5 08:05:56 2018 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 B5A18ED7B13 for ; Mon, 5 Feb 2018 08:05:56 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F30F87B70 for ; Mon, 5 Feb 2018 08:05:56 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id f136so40397862lff.8 for ; Mon, 05 Feb 2018 00:05:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=bZtoB1oRDGyBy64qwaxgdyRVJMuHyLcIsoCJbJ2fizA=; b=bFma/Pq9LN6SGqHJWKN16dI1Ydy+ehkchr76KZVQVvWnO3NkJFtl8QdbppbWJII1C5 GllXPkQD3kGgvHb7X+Lt7s7iekbW399RlhaBtOsMFm/aZSiWVqDL2johQs+j+pNlI022 HIgdHpcx4PKRP3cYgatXYmn8x/zkqHioEzSaZNSV1MhCFH7PAHcNeBpqJJzD6bUDUvnG Vbkjue9pHNzdGUqidTOwZ7nv2+A1gNZMWoLIsXqjPSyrA6YKJD135nBocb4OwPCBXiIM rfiAaaYqqfbiB703R7DfzytRA2CB6AW6ubT05IN1PBUqZCiOFdRnLZAYdI1igClNVd6u qWMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=bZtoB1oRDGyBy64qwaxgdyRVJMuHyLcIsoCJbJ2fizA=; b=h9EmraYOo12tRxe3/4xlMV29eHKFZ8R8XKdnEttpxTsFLyxwkm37xQz6rCb7nwzfze l39l3w3/88/evrmW5AZzvfItz51MFLUHOOFi4ODSMpDUPK5x2T/MyqNwOkeR4Odj6At/ oOfvMvw1XoVQi/2/WMF8QiETfWnwNRWU2jOhLXOy5VihzJDjyXHaEuREJAHB8yQe+HPs eC6XCwnE/tOJKUqsyvuWmz8xOSe3sgwDP29oeqk7LjgJts4y6+xYY2O8IBZ+bFkbNo9a rboFwP6hsg1Slo2L4XzQoNrSDo3k5hDwVfL56Ihy/tOkwJXL76o/6XqV3opCC4aCWcLe ruCQ== X-Gm-Message-State: AKwxytd3E6n3gC8xVbKosRGnko1jgZKpihFWjPsERcwZ4xmodCVcQc8o u9LgrwKNVV3zUBR3lyY70hbeRD/9 X-Google-Smtp-Source: AH8x225ICULDbAAy1MEsi643xE7/MF6iNlYsd6T+eLpnbGQLBLQclwGdIqao3egJJGJXT68Dttr9zQ== X-Received: by 10.25.234.193 with SMTP id y62mr28805572lfi.53.1517817954178; Mon, 05 Feb 2018 00:05:54 -0800 (PST) Received: from localhost (ppp109-252-75-138.pppoe.spdop.ru. [109.252.75.138]) by smtp.gmail.com with ESMTPSA id f14sm1713626lje.84.2018.02.05.00.05.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Feb 2018 00:05:53 -0800 (PST) Date: Mon, 5 Feb 2018 11:05:52 +0300 From: Vladimir Zakharov To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180205080552.3zkghfcc3j3sibbk@vzakharov> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <20180202063755.02aa231a@freyja.zeit4.iv.bundesimmobilien.de> <20180203081053.rxyog5iewqrjezp6@vzakharov> <20180203111733.7d64a066@thor.intern.walstatt.dynvpn.de> <20180204133636.763674ee@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180204133636.763674ee@thor.intern.walstatt.dynvpn.de> X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 05 Feb 2018 08:05:57 -0000 On Sun, Feb 04, 2018, O. Hartmann wrote: > Am Sat, 3 Feb 2018 11:17:06 +0100 > "O. Hartmann" schrieb: > > > Am Sat, 3 Feb 2018 11:10:53 +0300 > > Vladimir Zakharov schrieb: > > > > > Hello, Oliver! > > > > > > On Fri, Feb 02, 2018, O. Hartmann wrote: > > > > On Thu, 1 Feb 2018 12:10:30 +0300 > > > > Vladimir Zakharov wrote: > > > > > > > > > Hello! > > > > > > > > > > For some time (about a week) building and installing kernel fails with > > > > > the error "Variable OBJTOP is recursive." when going to build/install > > > > > module from ports. > > > > > > > > > > Last successful build was at r328426. Next build at r328527 failed and > > > > > still broken at r328649. > > > > > > > > > > Without PORTS_MODULES building and installing kernel succeeds. Another > > > > > workaround: ignore error and build/install module directly from ports. > > > > > > > > > > > > > I have had the very same issue! > > > > > > > > You need to perform a "installworld" first (just comment out the PORTS_MODULES= > > > > parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel (maybe not > > > > a full buildworld, but I do not know the state of your source tree) and perform > > > > a regular installation of the world. It could be something easier by direkctly > > > > install-only the mk-portions, but recently, some changes to world (LLVM) made > > > > it worth anyway to buildworld. > > > > > > > > As recommended by others earlier on this list according to this subject, this > > > > procedure makes the problem go away. > > > > > > Thanks for your answer. Unfortunately, this didn't help. > > > > > > > You are correct! I made a mistake and had the portions still commented out. I'm very > > sorry. > > > > This remains a bug! > > > > This problem has been introduced with > > svn commit: r328489 - head/sys/conf > > The the appropriate list for reference. > Indeed, reverting r328489 fixes the problem. -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Mon Feb 5 10:58:06 2018 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 DB518EE516E for ; Mon, 5 Feb 2018 10:58:06 +0000 (UTC) (envelope-from taav@protonmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 700D96DD07 for ; Mon, 5 Feb 2018 10:58:06 +0000 (UTC) (envelope-from taav@protonmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 27235EE5166; Mon, 5 Feb 2018 10:58:06 +0000 (UTC) Delivered-To: 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 14F5CEE5165 for ; Mon, 5 Feb 2018 10:58:06 +0000 (UTC) (envelope-from taav@protonmail.com) Received: from mail4.protonmail.ch (mail4.protonmail.ch [185.70.40.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3F3A6DD06 for ; Mon, 5 Feb 2018 10:58:05 +0000 (UTC) (envelope-from taav@protonmail.com) Date: Mon, 05 Feb 2018 05:49:41 -0500 To: Cy Schubert From: Taavi Cc: "current@freebsd.org" Reply-To: Taavi Subject: Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes Message-ID: In-Reply-To: <201802041819.w14IJSFi003912@slippy.cwsent.com> References: <201802041819.w14IJSFi003912@slippy.cwsent.com> Feedback-ID: DE6O6gJFyPb0hA7-V94Wt75T4HquYkFeRTcwrdLs1TBZ4KxqXiHBLQzVbD_COG_zInavwSAKPkGJOuM7R7l3xQ==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-Mailman-Approved-At: Mon, 05 Feb 2018 11:30:06 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 05 Feb 2018 10:58:07 -0000 Hi Not really wanting to do that. Using pkg binary system for purpose That would lead to question why binary package driver crashes kernel? regards, Taavi =E2=80=8B Sent with ProtonMail Secure Email. =E2=80=8B -------- Original Message -------- On February 4, 2018 8:19 PM, Cy Schubert wrote= : >In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5 > FMckEUy >rF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=3D@protonmail.com>, Taavi writes: >>see subject >> > > Try rebuilding and reinstalling virtualbox-ose-kmod. > > > >Cheers, > Cy Schubert Cy.Schubert@cschubert.com >FreeBSD UNIX: cy@FreeBSD.org Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > From owner-freebsd-current@freebsd.org Mon Feb 5 17:48:31 2018 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 B54E3EE0DD2 for ; Mon, 5 Feb 2018 17:48:31 +0000 (UTC) (envelope-from filippomore@yahoo.com) Received: from sonic302-4.consmr.mail.bf2.yahoo.com (sonic302-4.consmr.mail.bf2.yahoo.com [74.6.135.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F8117EB4A for ; Mon, 5 Feb 2018 17:48:31 +0000 (UTC) (envelope-from filippomore@yahoo.com) X-YMail-OSG: rOlM.AsVM1nwkwZcKryycc0ejMAryJx0Uk48kK9Zo_ijCTkxHQrg_PKZMR824Vq 340naJYKA5Yi.AKaL3QroKEhntL38vGnbguhAhmSBESpdaNX9D4JRMXd5fRFfIbMQPaJ9i3uFb.T S9iPdb_zVyIbNue.T.Ft7dvCnY7w33pABJCuupmy30ZnR.BZPpnoe8tvhj_QS38ZgXcPu_cfkRqG DMSWlVgHpy7udNOweAQksI1MHbAJjpWgn59pXiLEPvXu6Mbyx2RiJ5xM6OT4TgzXQzCdNYt9k0jk 3pOawmNwsSnAafeE7ngAE.In4BXy7U6qcov0EnV5v8aU9S8jWJTIJZsWDknXTxsQFsMn6fzzu3nn Sush23Y5eM7HykRCplUfuPTbw0Msg755WiNHwJVbrd1ZC26av72dxxn5VuybQFSM1RbJIbISwkFc 4bKk84aiSaQG1CZWlSmlzIRJFWlDq69Lg9x4JX.dFB6N16sd3psEei60R Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.bf2.yahoo.com with HTTP; Mon, 5 Feb 2018 17:48:24 +0000 Date: Mon, 5 Feb 2018 17:48:20 +0000 (UTC) From: Filippo Moretti To: FreeBSD Current Message-ID: <3408872.3417987.1517852900450@mail.yahoo.com> Subject: problem with buildworld MIME-Version: 1.0 References: <3408872.3417987.1517852900450.ref@mail.yahoo.com> X-Mailer: WebService/1.1.11316 YMailNorrin Mozilla/5.0 (X11; FreeBSD i386; rv:58.0) Gecko/20100101 Firefox/58.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 05 Feb 2018 17:48:31 -0000 Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr but I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug: Bad file descriptorrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: /usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: Directory not emptyrm: /usr/obj/usr: Directory not empty[root@sting /usr/src]# Any help would be appreciatedsincerelyFilippo From owner-freebsd-current@freebsd.org Mon Feb 5 18:44:03 2018 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 7CB6BEE5A62 for ; Mon, 5 Feb 2018 18:44:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 116F8828AD for ; Mon, 5 Feb 2018 18:44:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C6A44EE5A61; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) Delivered-To: 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 A4727EE5A60 for ; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E66A828AB for ; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x230.google.com with SMTP id q62so18275335vkb.11 for ; Mon, 05 Feb 2018 10:44:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hDApsuOoeY6Vy4sM3PYhlfU5PcZ0s24A4PAK5x0wHRw=; b=hKa0zb5ziOWthv7+K7uFZBgLUA1pastT3x0lGn/afDBm9dKr6WYjan4GOWg/V3z31i TgKAHBGwZEvhxJitpMQZ/2KswY2+WKu0O7dwCFBY03jMoYKqryw9KNtKynxkeZKIG1fy 53PeRkgvSVV+mbbczuUz6/qB17GbzWb03ZVILT8lhOlh8L/R01Z5EfqwUBoPdoL4gHCB q0YA47Z8yYYd/OwPEePhOOOb7HH6co7aFmtx3VQNHTGlBWrqRg/MJc7H2ghHUR5p8Tdl rFKQMycl3YZ0uXbyHoQzX4ZiagmJQ0Rn+LJJmwJY+KKCF4gtspolB7lWpJmD1zvIOr6/ XJxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hDApsuOoeY6Vy4sM3PYhlfU5PcZ0s24A4PAK5x0wHRw=; b=uMxr//6pADEQshZ/5fR5AVBgqYYWjJjrX+JCLj2UGB6dvVAYuoG1XVexEZNsrEJlTC gxx79I9f3LcBAMNLKvFlkHvn2pWuV2bf1Eky5SZHn23JN5DGN9OFubEJRxYf2AvZZw5E BHVwkme6ThVSmDO2scxaWVoSyI/4+9H7B+tbwCEZi6GZ4VTwyL5CwJ7rJG+x9jToDlDZ jPahmtIfS8NF2HyUATlafJgk/yOKHi/wKVLA+tSJMHvbPUlP3FXaYp6tLyGTT8/dZVyh Nf7VnGV/6+JT2877KFZUrAz6wnxCdMLliEDembH0siEFY6GFMhcaSO8EatDxB3vWjz7s mXCg== X-Gm-Message-State: AKwxytd7uSHiQE1Cx1kgua2EXVFibFWG3mUw2oBlh3piL2rkbpujoH0d wGmRw1Sa2qRZTNN9Ia0tQkQZlua+SXhfUofL+Cs= X-Google-Smtp-Source: AH8x224lxKaGCLg7NH/AC7gsfTvTL/PtDpL/FfVfrHdXoyeEqMwFMMH3CjnNn2eEHsDLzZHcubkrZ6R6SAZ1oa4tlaE= X-Received: by 10.31.134.74 with SMTP id i71mr41871955vkd.128.1517856241658; Mon, 05 Feb 2018 10:44:01 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.39.199 with HTTP; Mon, 5 Feb 2018 10:44:01 -0800 (PST) In-Reply-To: References: <201802041819.w14IJSFi003912@slippy.cwsent.com> From: Kevin Oberman Date: Mon, 5 Feb 2018 10:44:01 -0800 X-Google-Sender-Auth: kYsydzVvkowh7IIscf1alvwShhI Message-ID: Subject: Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes To: Taavi Cc: Cy Schubert , "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 05 Feb 2018 18:44:03 -0000 On Mon, Feb 5, 2018 at 2:49 AM, Taavi wrote: > Hi > > Not really wanting to do that. Using pkg binary system for purpose > > That would lead to question why binary package driver crashes kernel? > > regards, > Taavi > This is a real problem with kmod packages. If hte kernel is modified in any way, modules must be re-built. It may take a while for the package to get re-built for a given change as the port has not been modified. The recommended method is to put port modules into /etc/src.conf PORTS_MODULES list so that kernel rebuild will always rebuild the modules, but that only works if the kernel IS built from sources and re-installed. It will be a bigger issue when more people start doing binary updates to the kernel.more routinely. From owner-freebsd-current@freebsd.org Mon Feb 5 19:06:35 2018 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 D7B1AEE79D4 for ; Mon, 5 Feb 2018 19:06:35 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 726968441C for ; Mon, 5 Feb 2018 19:06:35 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 59E6219383; Mon, 5 Feb 2018 20:06:33 +0100 (CET) From: Dimitry Andric Message-Id: <1AD4A33E-DFF3-4E1C-8085-5A85AF3CEF1F@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_771270A0-3FDF-442C-9E2A-C12DBC0E763B"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: problem with buildworld Date: Mon, 5 Feb 2018 20:06:32 +0100 In-Reply-To: <3408872.3417987.1517852900450@mail.yahoo.com> Cc: FreeBSD Current To: Filippo Moretti References: <3408872.3417987.1517852900450.ref@mail.yahoo.com> <3408872.3417987.1517852900450@mail.yahoo.com> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 05 Feb 2018 19:06:36 -0000 --Apple-Mail=_771270A0-3FDF-442C-9E2A-C12DBC0E763B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 5 Feb 2018, at 18:48, Filippo Moretti wrote: >=20 > Buildworld failed with libpam/modules error.I tried to delete = /usr/obj/usr but I get the following error[root@sting /usr/src]# rm -rf = /usr/obj/usrrm: = /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieacces= s.so.6.debug: Bad file descriptorrm: = /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory = not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory = not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam: Directory not = emptyrm: /usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: = /usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: = Directory not emptyrm: /usr/obj/usr: Directory not empty[root@sting = /usr/src]# Any help would be appreciatedsincerelyFilippo Try rebooting into single user mode, and running "fsck -f -y" until all your filesystems are completely clean. Also, please switch to a mail client that does not completely mangle your messages. -Dimitry --Apple-Mail=_771270A0-3FDF-442C-9E2A-C12DBC0E763B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWnirOAAKCRCwXqMKLiCW o1ndAKClpNvwgPOjic3Sxv+lwfGnkTvxkACgnW2Iry+RapswI5B9IEkLw7Q+j78= =GS8o -----END PGP SIGNATURE----- --Apple-Mail=_771270A0-3FDF-442C-9E2A-C12DBC0E763B-- From owner-freebsd-current@freebsd.org Tue Feb 6 18:25:29 2018 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 B3B64EF024B for ; Tue, 6 Feb 2018 18:25:29 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [69.87.218.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A61E777BC5 for ; Tue, 6 Feb 2018 18:25:28 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.23] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail5.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w16Ht1gd000396 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Feb 2018 10:55:03 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.23] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. From: John Nielsen In-Reply-To: Date: Tue, 6 Feb 2018 10:54:58 -0700 Cc: freebsd-current , Daisuke Aoyama Content-Transfer-Encoding: quoted-printable Message-Id: References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> To: Maurizio Vairani X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 18:25:29 -0000 > On Feb 4, 2018, at 2:50 AM, Maurizio Vairani = wrote: >=20 > 2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] >=20 >> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani = wrote: >>=20 >> I am running >> # uname >> -a >>=20 >> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 = 04:48:52 >> UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >>=20 >> After compiling the kernel module as discussed in this thread : >> = https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068272.ht= ml >>=20 >> I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the = iSCSI >> boot driver version 0.2.13, starts I receive a panic: >> = https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4 >>=20 >> Any idea? >=20 > Bummer!=20 >=20 > Aoyama-san- >=20 > Are you still maintaining isboot? Can you help debug this issue on = FreeBSD 12-CURRENT? >=20 > Once we get it working I will update the port with whatever is needed = and send you the patches in case you'd like to cut a new release. >=20 > Thank you! >=20 > I have solved the issue changing the function isboot_ifup() in the = source file isboot.c. Here is a patch with some changes to minimize the diff. Except for the = printed error messages does that look functionally equivalent? Now the question is why is this change needed and for what values of = __FreeBSD_version is it appropriate? # diff -u isboot.c.patched1 isboot.c --- isboot.c.patched1 2018-02-06 10:35:20.808692000 -0700 +++ isboot.c 2018-02-06 10:50:05.347663000 -0700 @@ -417,28 +417,36 @@ isboot_ifup(struct ifnet *ifp) { struct ifreq ifr; + struct socket *so; struct thread *td; int error; =20 memset(&ifr, 0, sizeof(ifr)); td =3D curthread; =20 + error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); + if (error) { + printf("%s: socreate, error=3D%d\n", __func__, error); + return (error); + } + /* boot NIC */ strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); =20 /* set IFF_UP */ - error =3D ifioctl(NULL, SIOCGIFFLAGS, (caddr_t)&ifr, td); + error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); if (error) { printf("ifioctl SIOCGIFFLAGS\n"); return (error); } ifr.ifr_flags |=3D IFF_UP; - error =3D ifioctl(NULL, SIOCSIFFLAGS, (caddr_t)&ifr, td); + error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); if (error) { printf("ifioctl SIOCSIFFLAGS\n"); return (error); } =20 + soclose(so); return (0); } > static int > isboot_ifup(struct ifnet *ifp) > { > struct socket *so; > struct ifreq ifr; > struct thread *td; > int error; >=20 > td =3D curthread; > error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); > if (error) { > printf("%s: socreate, error=3D%d\n", __func__, error); > return (error); > } >=20 > /* boot NIC */ > memset(&ifr, 0, sizeof(ifr)); > strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); >=20 > /* set IFF_UP */ > error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("%s: ifioctl SIOCGIFFLAGS, error=3D%d\n", __func__, = error); > return (error); > } >=20 > ifr.ifr_flags |=3D IFF_UP; > error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("%s, ifioctl SIOCSIFFLAGS, error=3D%d\n", __func__, = error); > return (error); > } > soclose(so); > return (0); > } >=20 > I have added a socket in the ifioctl() call as in the = /usr/src/sys/nfs/bootp_subr.c source. > Please let me know if you prefer a patch. > -- > Regards, > Maurizio >=20 From owner-freebsd-current@freebsd.org Tue Feb 6 18:25:30 2018 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 170C2EF024D for ; Tue, 6 Feb 2018 18:25:30 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [69.87.218.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A629777BC7 for ; Tue, 6 Feb 2018 18:25:29 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.23] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail5.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w15KHpIq090642 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Feb 2018 13:17:54 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.23] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. From: John Nielsen In-Reply-To: Date: Mon, 5 Feb 2018 13:17:51 -0700 Cc: freebsd-current , Daisuke Aoyama Content-Transfer-Encoding: quoted-printable Message-Id: <5F8F604B-BDD5-44EE-A83C-5D37ED5199EB@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> To: Maurizio Vairani X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 18:25:30 -0000 > On Feb 4, 2018, at 2:50 AM, Maurizio Vairani = wrote: >=20 > 2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] >=20 >> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani = wrote: >>=20 >> I am running >> # uname >> -a >>=20 >> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 = 04:48:52 >> UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >>=20 >> After compiling the kernel module as discussed in this thread : >> = https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068272.ht= ml >>=20 >> I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the = iSCSI >> boot driver version 0.2.13, starts I receive a panic: >> = https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4 >>=20 >> Any idea? >=20 > Bummer!=20 >=20 > Aoyama-san- >=20 > Are you still maintaining isboot? Can you help debug this issue on = FreeBSD 12-CURRENT? >=20 > Once we get it working I will update the port with whatever is needed = and send you the patches in case you'd like to cut a new release. >=20 > Thank you! >=20 > I have solved the issue changing the function isboot_ifup() in the = source file isboot.c. Nice work, thank you! I'll put the below together with the necessary = changes to iscsi.c and update the port. If you could re-install from the = port at that point as a further test/sanity check that would be great. > static int > isboot_ifup(struct ifnet *ifp) > { > struct socket *so; > struct ifreq ifr; > struct thread *td; > int error; >=20 > td =3D curthread; > error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); > if (error) { > printf("%s: socreate, error=3D%d\n", __func__, error); > return (error); > } >=20 > /* boot NIC */ > memset(&ifr, 0, sizeof(ifr)); > strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); >=20 > /* set IFF_UP */ > error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("%s: ifioctl SIOCGIFFLAGS, error=3D%d\n", __func__, = error); > return (error); > } >=20 > ifr.ifr_flags |=3D IFF_UP; > error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("%s, ifioctl SIOCSIFFLAGS, error=3D%d\n", __func__, = error); > return (error); > } > soclose(so); > return (0); > } >=20 > I have added a socket in the ifioctl() call as in the = /usr/src/sys/nfs/bootp_subr.c source. > Please let me know if you prefer a patch. > -- > Regards, > Maurizio From owner-freebsd-current@freebsd.org Tue Feb 6 18:33:27 2018 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 94DB5EF0E86 for ; Tue, 6 Feb 2018 18:33:27 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [69.87.218.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F385784BB for ; Tue, 6 Feb 2018 18:33:26 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.23] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail5.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w16IXMJC000659 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Feb 2018 11:33:25 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.23] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. From: John Nielsen In-Reply-To: Date: Tue, 6 Feb 2018 11:33:22 -0700 Cc: freebsd-current , Daisuke Aoyama Content-Transfer-Encoding: quoted-printable Message-Id: <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> To: Maurizio Vairani X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 18:33:27 -0000 > On Feb 6, 2018, at 10:54 AM, John Nielsen wrote: >=20 >>=20 >> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani = wrote: >>=20 >> 2018-01-29 18:38 GMT+01:00 John Nielsen : >> [ resending from correct email address ] >>=20 >>> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani = wrote: >>>=20 >>> I am running >>> # uname >>> -a >>>=20 >>> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 = 04:48:52 >>> UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >>> amd64 >>>=20 >>> After compiling the kernel module as discussed in this thread : >>> = https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068272.ht= ml >>>=20 >>> I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the = iSCSI >>> boot driver version 0.2.13, starts I receive a panic: >>> = https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4 >>>=20 >>> Any idea? >>=20 >> Bummer!=20 >>=20 >> Aoyama-san- >>=20 >> Are you still maintaining isboot? Can you help debug this issue on = FreeBSD 12-CURRENT? >>=20 >> Once we get it working I will update the port with whatever is needed = and send you the patches in case you'd like to cut a new release. >>=20 >> Thank you! >>=20 >> I have solved the issue changing the function isboot_ifup() in the = source file isboot.c. >=20 > Here is a patch with some changes to minimize the diff. Except for the = printed error messages does that look functionally equivalent? >=20 > Now the question is why is this change needed and for what values of = __FreeBSD_version is it appropriate? Apparently sending a NULL socket pointer to ifioctl hasn't worked since = this commit in 2011: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D218757 So I'm going to add this patch to the port unconditionally once it = works. Unfortunately, I can't compile the port with either my patch below or = your original replacement version of isboot_ifup(). :( Did you make = other changes? Here's the error I'm getting: --- isboot.o --- isboot.c:425:53: error: incomplete definition of type 'struct thread' error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); ~~^ /usr/src/sys/sys/systm.h:185:8: note: forward declaration of 'struct = thread' struct thread; ^ 1 error generated. > # diff -u isboot.c.patched1 isboot.c > --- isboot.c.patched1 2018-02-06 10:35:20.808692000 -0700 > +++ isboot.c 2018-02-06 10:50:05.347663000 -0700 > @@ -417,28 +417,36 @@ > isboot_ifup(struct ifnet *ifp) > { > struct ifreq ifr; > + struct socket *so; > struct thread *td; > int error; >=20 > memset(&ifr, 0, sizeof(ifr)); > td =3D curthread; >=20 > + error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); > + if (error) { > + printf("%s: socreate, error=3D%d\n", __func__, error); > + return (error); > + } > + > /* boot NIC */ > strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); >=20 > /* set IFF_UP */ > - error =3D ifioctl(NULL, SIOCGIFFLAGS, (caddr_t)&ifr, td); > + error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("ifioctl SIOCGIFFLAGS\n"); > return (error); > } > ifr.ifr_flags |=3D IFF_UP; > - error =3D ifioctl(NULL, SIOCSIFFLAGS, (caddr_t)&ifr, td); > + error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); > if (error) { > printf("ifioctl SIOCSIFFLAGS\n"); > return (error); > } >=20 > + soclose(so); > return (0); > } >=20 >=20 >> static int >> isboot_ifup(struct ifnet *ifp) >> { >> struct socket *so; >> struct ifreq ifr; >> struct thread *td; >> int error; >>=20 >> td =3D curthread; >> error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); >> if (error) { >> printf("%s: socreate, error=3D%d\n", __func__, error); >> return (error); >> } >>=20 >> /* boot NIC */ >> memset(&ifr, 0, sizeof(ifr)); >> strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); >>=20 >> /* set IFF_UP */ >> error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); >> if (error) { >> printf("%s: ifioctl SIOCGIFFLAGS, error=3D%d\n", __func__, = error); >> return (error); >> } >>=20 >> ifr.ifr_flags |=3D IFF_UP; >> error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); >> if (error) { >> printf("%s, ifioctl SIOCSIFFLAGS, error=3D%d\n", __func__, = error); >> return (error); >> } >> soclose(so); >> return (0); >> } >>=20 >> I have added a socket in the ifioctl() call as in the = /usr/src/sys/nfs/bootp_subr.c source. >> Please let me know if you prefer a patch. >> -- >> Regards, >> Maurizio From owner-freebsd-current@freebsd.org Tue Feb 6 18:50:24 2018 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 DA5E9EF2482 for ; Tue, 6 Feb 2018 18:50:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63CF2791B8 for ; Tue, 6 Feb 2018 18:50:23 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 8bb023b9-0b6e-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 8bb023b9-0b6e-11e8-91c6-33ffc249f3e8; Tue, 06 Feb 2018 18:50:11 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w16Io1YV019128; Tue, 6 Feb 2018 11:50:01 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1517943001.1366.100.camel@freebsd.org> Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. From: Ian Lepore To: John Nielsen , Maurizio Vairani Cc: freebsd-current , Daisuke Aoyama Date: Tue, 06 Feb 2018 11:50:01 -0700 In-Reply-To: <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 18:50:24 -0000 On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > > > > On Feb 6, 2018, at 10:54 AM, John Nielsen > > wrote: > > > > > > > > > > > On Feb 4, 2018, at 2:50 AM, Maurizio Vairani > > com> wrote: > > > > > > 2018-01-29 18:38 GMT+01:00 John Nielsen : > > > [ resending from correct email address ] > > > > > > > > > > > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani > > > il.com> wrote: > > > > > > > > I am running > > > > # uname > > > > -a > > > > > > > > FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan > > > > 25 04:48:52 > > > > UTC 2018     root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd6 > > > > 4.amd64/sys/GENERIC > > > > amd64 > > > > > > > > After compiling the kernel module as discussed in this thread : > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-Januar > > > > y/068272.html > > > > > > > > I can boot FreeBSD via iSCSI using iPXE. But when the isboot, > > > > the iSCSI > > > > boot driver version 0.2.13, starts I receive a panic: > > > > https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdU > > > > A1BorD4 > > > > > > > > Any idea? > > > Bummer!  > > > > > > Aoyama-san- > > > > > > Are you still maintaining isboot? Can you help debug this issue > > > on FreeBSD 12-CURRENT? > > > > > > Once we get it working I will update the port with whatever is > > > needed and send you the patches in case you'd like to cut a new > > > release. > > > > > > Thank you! > > > > > > I have solved the issue changing the function isboot_ifup() in > > > the source file isboot.c. > > Here is a patch with some changes to minimize the diff. Except for > > the printed error messages does that look functionally equivalent? > > > > Now the question is why is this change needed and for what values > > of __FreeBSD_version is it appropriate? > Apparently sending a NULL socket pointer to ifioctl hasn't worked > since this commit in 2011: > https://svnweb.freebsd.org/base?view=revision&revision=218757 > > So I'm going to add this patch to the port unconditionally once it > works. > > Unfortunately, I can't compile the port with either my patch below or > your original replacement version of isboot_ifup(). :( Did you make > other changes? Here's the error I'm getting: > > --- isboot.o --- > isboot.c:425:53: error: incomplete definition of type 'struct thread' >     error = socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); >                                                   ~~^ > /usr/src/sys/sys/systm.h:185:8: note: forward declaration of 'struct > thread' > struct thread; >        ^ > 1 error generated. > Try adding #include if it's not already in the list.  It may be that that file got included via pollution from some other header file in the past and maybe now that has changed. If you're already including sys/proc.h then I'm clueless. -- Ian From owner-freebsd-current@freebsd.org Tue Feb 6 19:52:17 2018 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 640E1F00836 for ; Tue, 6 Feb 2018 19:52:17 +0000 (UTC) (envelope-from manfredantar@gmail.com) Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB9807D5CD for ; Tue, 6 Feb 2018 19:52:16 +0000 (UTC) (envelope-from manfredantar@gmail.com) Received: by mail-pl0-x230.google.com with SMTP id 36so1909935ple.13 for ; Tue, 06 Feb 2018 11:52:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=Nnhbjuq56uM8PVkPBHpKeu5S/8s4AshEnsjFSDJkn0g=; b=BdHZ38/Mx1jpmjI/fbxMo/wgk0uZ4rSiVeHxMFgIHXXmvEF0NQjvAT+rXO8iq8CDm4 ea+56Lz2Verdhod1QtLyUfey6UEI+Vk5xUAkupqFEIiiI9NhzV9XlXbj9sdFjKyhenfV A4z/e+P0R7+YwIoqkcfB/GEYcDzycH8tfbqH2SBFerPl+EUNYpQK6GMYA/kCNfXikmkw +9fWiLqSVH1et1Lqc9b9NQS+lzzWj+Tzyg1lYzdMJUe125L/QnlRnfU8cXniKX4xPDUJ 2JbRwM78rFUmLGANlCVItFfOTyhSJBx5VIUbErUNBd4umj45uQSa8X2oFe5K7VOAxToh +sTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=Nnhbjuq56uM8PVkPBHpKeu5S/8s4AshEnsjFSDJkn0g=; b=FZETvwSkH8n9sNnl2e6cbJQiFUk2MkDlhbccPg6WlJOE4QzCk8uRGrTR6hH10QB7Si b2k/QwSrMWaR2k/2jv5LJwYNY2d5l1UqmZlEch+9nDwE7Rxn83tLeqpwDCtsf9naUWpg M4Hmx4vWCUNc8R/pt7ltJc9V3MNYn+YS2oRQf4I1R9OqDlUjnWZ3oQ/rn9KgaX/saQDd TRkljJTnG5mq2NXMTiNblN9kMP0twXUz1EPgrnUWvApcd5qOrcYS3A5StB7YfLuKpEsL +xqd42Z2Vhm9d0U8vcMxNi7zgwLoInzAbMnSpnKMpkd4Q9MKSwA7pKptYxNlMt2VzaEc 4Vkg== X-Gm-Message-State: APf1xPCHOkVCi9eci1bq927Dg69XANFcxxSL2DNY2lDmvFtDhnzffyuH tOrhPF2Mbn3/RC4YPdhowCOSiA== X-Google-Smtp-Source: AH8x225iXzTrObm3chMqyNe3nE/jzNbq17wBLQohGyIuBWwvoHFpdLL1ULlcQeq0Mr065cOnpTi4PA== X-Received: by 2002:a17:902:8585:: with SMTP id e5-v6mr3416671plo.165.1517946735796; Tue, 06 Feb 2018 11:52:15 -0800 (PST) Received: from octo.pozo.com (50-197-129-138-static.hfc.comcastbusiness.net. [50.197.129.138]) by smtp.gmail.com with ESMTPSA id h13sm24714420pfd.14.2018.02.06.11.52.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 11:52:15 -0800 (PST) From: Manfred Antar Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Panic on Boot - Current AMD64 Message-Id: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> Date: Tue, 6 Feb 2018 11:52:14 -0800 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 19:52:17 -0000 I get panic on boot from current kernel. Since last night - changes to vm system ? World is Current as of this morning FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #0 r328948: Tue Feb 6 11:30:57 PST 2018 root@pozo.com:/usr/src/sys/amd64/compile/pozo amd64 FreeBSD clang version 6.0.0 (branches/release_60 324090) (based on LLVM = 6.0.0) Table 'FACP' at 0xdfbc57e8 Table 'APIC' at 0xdfbc585c Table 'ASF!' at 0xdfbc58e0 Table 'MCFG' at 0xdfbc5943 Table 'TCPA' at 0xdfbc597f Table 'SLIC' at 0xdfbc59b1 Table 'HPET' at 0xdfbc5b27 ACPI: No SRAT table found panic: UMA: Increase vm.boot_pages cpuid =3D 0 time =3D 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xffffffff820bc820 vpanic() at vpanic+0x18d/frame 0xffffffff820bc880 panic() at panic+0x43/frame 0xffffffff820bc8e0 startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> bt Tracing pid 0 tid 0 td 0xffffffff80ff1240 kdb_enter() at kdb_enter+0x3b/frame 0xffffffff820bc820 vpanic() at vpanic+0x1aa/frame 0xffffffff820bc880 panic() at panic+0x43/frame 0xffffffff820bc8e0 startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 btext() at btext+0x2c db>=20 From owner-freebsd-current@freebsd.org Tue Feb 6 21:42:12 2018 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 456D0F09537 for ; Tue, 6 Feb 2018 21:42:12 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.1]) (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 09C77833AB for ; Tue, 6 Feb 2018 21:42:11 +0000 (UTC) (envelope-from listjm@club.fr) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) by msfrf2615.sfr.fr (SMTP Server) with ESMTP id 640AD1C00041D for ; Tue, 6 Feb 2018 22:36:51 +0100 (CET) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juanmolina@sfr.fr) by msfrf2615.sfr.fr (SMTP Server) with ESMTPSA; Tue, 6 Feb 2018 22:36:51 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=juanmolina@sfr.fr To: freebsd-current@freebsd.org References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> Subject: Panic on Boot - Current AMD64 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Message-ID: <98e318af-2771-82ff-7abe-2bd6cbf90e6a@club.fr> Date: Tue, 6 Feb 2018 22:36:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> X-sfr-mailing: LEGIT Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: fr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 21:42:12 -0000 > I get panic on boot from current kernel. > Since last night - changes to vm system ? > World is Current as of this morning > > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 12.0-CURRENT #0 r328948: Tue Feb 6 11:30:57 PST 2018 > root at pozo.com > :/usr/src/sys/amd64/compile/pozo amd64 > FreeBSD clang version 6.0.0 (branches/release_60 324090) (based on LLVM 6.0.0) > Table 'FACP' at 0xdfbc57e8 > Table 'APIC' at 0xdfbc585c > Table 'ASF!' at 0xdfbc58e0 > Table 'MCFG' at 0xdfbc5943 > Table 'TCPA' at 0xdfbc597f > Table 'SLIC' at 0xdfbc59b1 > Table 'HPET' at 0xdfbc5b27 > ACPI: No SRAT table found > panic: UMA: Increase vm.boot_pages > cpuid = 0 > time = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff820bc820 > vpanic() at vpanic+0x18d/frame 0xffffffff820bc880 > panic() at panic+0x43/frame 0xffffffff820bc8e0 > startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 > keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 > keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 > zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 > zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 > zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 > uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 > vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 > vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 > mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 > btext() at btext+0x2c > KDB: enter: panic > [ thread pid 0 tid 0 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> bt > Tracing pid 0 tid 0 td 0xffffffff80ff1240 > kdb_enter() at kdb_enter+0x3b/frame 0xffffffff820bc820 > vpanic() at vpanic+0x1aa/frame 0xffffffff820bc880 > panic() at panic+0x43/frame 0xffffffff820bc8e0 > startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 > keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 > keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 > zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 > zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 > zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 > uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 > vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 > vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 > mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 > btext() at btext+0x2c > db> Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 with 4 GB. Workaround: break into the loader prompt and: set vm.boot_pages=120 boot When booting kernel.old, vm.boot_pages is 64. There is something wrong with r328916. Hope it helps, Juan From owner-freebsd-current@freebsd.org Tue Feb 6 22:02:26 2018 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 E411EF0B357 for ; Tue, 6 Feb 2018 22:02:25 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [69.87.218.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F5C584657; Tue, 6 Feb 2018 22:02:24 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.23] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail5.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w16M2COk002223 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Feb 2018 15:02:14 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.23] From: John Nielsen Message-Id: <1C97132B-099B-4BAA-9C39-A1BE00481CAC@jnielsen.net> Content-Type: multipart/mixed; boundary="Apple-Mail=_B7DB8F21-4A50-46D9-ABF3-A6D79284F287" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. Date: Tue, 6 Feb 2018 15:02:10 -0700 In-Reply-To: <1517943001.1366.100.camel@freebsd.org> Cc: freebsd-current , Daisuke Aoyama , Ian Lepore To: Maurizio Vairani References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> <1517943001.1366.100.camel@freebsd.org> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 06 Feb 2018 22:02:26 -0000 --Apple-Mail=_B7DB8F21-4A50-46D9-ABF3-A6D79284F287 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: >=20 > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: >>=20 >> Apparently sending a NULL socket pointer to ifioctl hasn't worked >> since this commit in 2011: >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D218757 >>=20 >> So I'm going to add this patch to the port unconditionally once it >> works. >>=20 >> Unfortunately, I can't compile the port with either my patch below or >> your original replacement version of isboot_ifup(). :( Did you make >> other changes? Here's the error I'm getting: >>=20 >> --- isboot.o --- >> isboot.c:425:53: error: incomplete definition of type 'struct thread' >> error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); >> ~~^ >> /usr/src/sys/sys/systm.h:185:8: note: forward declaration of 'struct >> thread' >> struct thread; >> ^ >> 1 error generated. >>=20 >=20 > Try adding #include if it's not already in the list. It > may be that that file got included via pollution from some other = header > file in the past and maybe now that has changed. >=20 > If you're already including sys/proc.h then I'm clueless. Thanks Ian, that appears to work. Maurizio, can you apply the attached patch to a clean ports tree and see = if isboot-kmod will build and function properly for you? This is all the = changes from this thread and the previous one. If you let me know it = works I'll get the port updated. --Apple-Mail=_B7DB8F21-4A50-46D9-ABF3-A6D79284F287 Content-Disposition: attachment; filename=isboot_patch.txt Content-Type: text/plain; x-unix-mode=0644; name="isboot_patch.txt" Content-Transfer-Encoding: quoted-printable diff -uPr isboot-kmod.orig/Makefile isboot-kmod/Makefile --- isboot-kmod.orig/Makefile 2018-01-11 07:18:01.000000000 -0700 +++ isboot-kmod/Makefile 2018-02-06 14:56:23.654737000 -0700 @@ -2,7 +2,7 @@ =20 PORTNAME=3D isboot-kmod PORTVERSION=3D 0.2.13 -PORTREVISION=3D 1 +PORTREVISION=3D 2 CATEGORIES=3D net MASTER_SITES=3D http://www.peach.ne.jp/archives/isboot/ DISTNAME=3D isboot-${PORTVERSION} @@ -12,9 +12,7 @@ =20 LICENSE=3D BSD2CLAUSE =20 -BROKEN_aarch64=3D fails to compile: = /usr/src/sys/sys/bus.h:724:10: fatal error: 'device_if.h' file not found BROKEN_armv6=3D fails to compile: implicit declaration of = function 'cp15_pmccntr_get' is invalid in C99 -BROKEN_armv7=3D fails to compile: = /usr/src/sys/sys/bus.h:724:10: fatal error: 'device_if.h' file not found BROKEN_powerpc64=3D fails to compile: pcpu.h: size of array = '__assert_0' is negative =20 USES=3D kmod uidfix diff -uPr isboot-kmod.orig/files/patch-Makefile = isboot-kmod/files/patch-Makefile --- isboot-kmod.orig/files/patch-Makefile 1969-12-31 = 17:00:00.000000000 -0700 +++ isboot-kmod/files/patch-Makefile 2018-01-29 10:24:27.372206000 = -0700 @@ -0,0 +1,10 @@ +--- Makefile.orig 2015-09-23 22:33:04.000000000 -0600 ++++ Makefile 2018-01-29 10:20:10.453188000 -0700 +@@ -6,6 +6,7 @@ + SRCS=3D isboot.c ibft.c iscsi.c + SRCS+=3D isboot.h ibft.h iscsi_compat.h + SRCS+=3D opt_cam.h ++SRCS+=3D device_if.h bus_if.h + #CFLAGS+=3D -DVIMAGE + #CFLAGS+=3D -DIBFT_VERBOSE + #CFLAGS+=3D -DDEBUG diff -uPr isboot-kmod.orig/files/patch-isboot.c = isboot-kmod/files/patch-isboot.c --- isboot-kmod.orig/files/patch-isboot.c 2016-05-06 = 08:34:57.000000000 -0600 +++ isboot-kmod/files/patch-isboot.c 2018-02-06 14:24:47.447244000 = -0700 @@ -1,6 +1,14 @@ ---- isboot.c.orig 2015-11-05 16:50:51 UTC -+++ isboot.c -@@ -347,9 +347,9 @@ isboot_set_v4gw(struct sockaddr_in *gate +--- isboot.c.orig 2015-11-05 09:50:51.000000000 -0700 ++++ isboot.c 2018-02-06 14:23:24.479249000 -0700 +@@ -38,6 +38,7 @@ + #include + #include + #include ++#include + #include + #include + #include +@@ -347,9 +348,9 @@ netmask.sin_addr.s_addr =3D htonl(0); =20 /* delete gateway if exists */ @@ -12,7 +20,7 @@ if (error) { if (error !=3D ESRCH) { printf("rtrequest RTM_DELETE error %d\n", -@@ -359,9 +359,9 @@ isboot_set_v4gw(struct sockaddr_in *gate +@@ -359,9 +360,9 @@ } =20 /* set new default gateway */ @@ -24,7 +32,7 @@ if (error) { printf("rtrequest RTM_ADD error %d\n", error); return (error); -@@ -391,9 +391,9 @@ isboot_set_v6gw(struct sockaddr_in6 *gat +@@ -391,9 +392,9 @@ memset(&netmask.sin6_addr, 0, 16); =20 /* delete gateway if exists */ @@ -36,7 +44,7 @@ if (error) { if (error !=3D ESRCH) { printf("rtrequest RTM_DELETE error %d\n", -@@ -403,9 +403,9 @@ isboot_set_v6gw(struct sockaddr_in6 *gat +@@ -403,9 +404,9 @@ } =20 /* set new default gateway */ @@ -48,3 +56,42 @@ if (error) { printf("rtrequest RTM_ADD error %d\n", error); return (error); +@@ -417,28 +418,36 @@ + isboot_ifup(struct ifnet *ifp) + { + struct ifreq ifr; ++ struct socket *so; + struct thread *td; + int error; +=20 + memset(&ifr, 0, sizeof(ifr)); + td =3D curthread; +=20 ++ error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); ++ if (error) { ++ printf("%s: socreate, error=3D%d\n", __func__, error); ++ return (error); ++ } ++ + /* boot NIC */ + strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); +=20 + /* set IFF_UP */ +- error =3D ifioctl(NULL, SIOCGIFFLAGS, (caddr_t)&ifr, td); ++ error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); + if (error) { + printf("ifioctl SIOCGIFFLAGS\n"); + return (error); + } + ifr.ifr_flags |=3D IFF_UP; +- error =3D ifioctl(NULL, SIOCSIFFLAGS, (caddr_t)&ifr, td); ++ error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); + if (error) { + printf("ifioctl SIOCSIFFLAGS\n"); + return (error); + } +=20 ++ soclose(so); + return (0); + } +=20 diff -uPr isboot-kmod.orig/files/patch-iscsi.c = isboot-kmod/files/patch-iscsi.c --- isboot-kmod.orig/files/patch-iscsi.c 1969-12-31 = 17:00:00.000000000 -0700 +++ isboot-kmod/files/patch-iscsi.c 2018-01-29 10:24:54.854580000 = -0700 @@ -0,0 +1,27 @@ +--- iscsi.c.orig 2015-11-05 09:50:51.000000000 -0700 ++++ iscsi.c 2018-01-29 10:20:00.586277000 -0700 +@@ -1070,9 +1070,11 @@ + return (n); + } +=20 +- +-#if __FreeBSD_version >=3D 1100000 ++#if __FreeBSD_version >=3D 1200051 + static void ++isboot_free_mbufext(struct mbuf *m) ++#elif __FreeBSD_version >=3D 1100000 ++static void + isboot_free_mbufext(struct mbuf *m, void *p, void *optarg) + #elif __FreeBSD_version >=3D 1000050 && __FreeBSD_version < 1100000 + static int +@@ -1082,7 +1084,9 @@ + isboot_free_mbufext(void *p, void *optarg) + #endif + { +- ++#if __FreeBSD_version >=3D 1200051 ++ void *p =3D m->m_ext.ext_arg1; ++#endif + ISBOOT_TRACE("isboot_free_mbufext\n"); + if (p =3D=3D NULL) + #if __FreeBSD_version >=3D 1000050 && __FreeBSD_version < 1100000 --Apple-Mail=_B7DB8F21-4A50-46D9-ABF3-A6D79284F287 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii --Apple-Mail=_B7DB8F21-4A50-46D9-ABF3-A6D79284F287-- From owner-freebsd-current@freebsd.org Wed Feb 7 11:23:41 2018 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 C4AFDEF4FC8 for ; Wed, 7 Feb 2018 11:23:41 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.10]) (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 5D8058412C for ; Wed, 7 Feb 2018 11:23:40 +0000 (UTC) (envelope-from listjm@club.fr) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) by msfrf2623.sfr.fr (SMTP Server) with ESMTP id 926F21C05400A for ; Wed, 7 Feb 2018 12:18:31 +0100 (CET) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juanmolina@sfr.fr) by msfrf2623.sfr.fr (SMTP Server) with ESMTPSA; Wed, 7 Feb 2018 12:18:31 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=juanmolina@sfr.fr From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Subject: Panic on Boot - Current AMD64 To: freebsd-current@freebsd.org Cc: manfredantar@gmail.com, glebius@freebsd.org References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> Message-ID: Date: Wed, 7 Feb 2018 12:18:26 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> X-sfr-mailing: LEGIT Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: fr Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 11:23:42 -0000 >> I get panic on boot from current kernel. >> Since last night - changes to vm system ? >> World is Current as of this morning >> >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 12.0-CURRENT #0 r328948: Tue Feb 6 11:30:57 PST 2018 >> root at pozo.com >> :/usr/src/sys/amd64/compile/pozo amd64 >> FreeBSD clang version 6.0.0 (branches/release_60 324090) (based on LLVM 6.0.0) >> Table 'FACP' at 0xdfbc57e8 >> Table 'APIC' at 0xdfbc585c >> Table 'ASF!' at 0xdfbc58e0 >> Table 'MCFG' at 0xdfbc5943 >> Table 'TCPA' at 0xdfbc597f >> Table 'SLIC' at 0xdfbc59b1 >> Table 'HPET' at 0xdfbc5b27 >> ACPI: No SRAT table found >> panic: UMA: Increase vm.boot_pages >> cpuid = 0 >> time = 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff820bc820 >> vpanic() at vpanic+0x18d/frame 0xffffffff820bc880 >> panic() at panic+0x43/frame 0xffffffff820bc8e0 >> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 >> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 >> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 >> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 >> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 >> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 >> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 >> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 >> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 >> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 >> btext() at btext+0x2c >> KDB: enter: panic >> [ thread pid 0 tid 0 ] >> Stopped at kdb_enter+0x3b: movq $0,kdb_why >> db> bt >> Tracing pid 0 tid 0 td 0xffffffff80ff1240 >> kdb_enter() at kdb_enter+0x3b/frame 0xffffffff820bc820 >> vpanic() at vpanic+0x1aa/frame 0xffffffff820bc880 >> panic() at panic+0x43/frame 0xffffffff820bc8e0 >> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 >> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 >> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 >> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 >> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 >> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 >> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 >> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 >> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 >> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 >> btext() at btext+0x2c >> db> > > > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 > with 4 GB. > > Workaround: break into the loader prompt and: > > set vm.boot_pages=120 > boot > > When booting kernel.old, vm.boot_pages is 64. > > There is something wrong with r328916. > > Hope it helps, > Juan Hi! Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the issue here. Hope it helps, Juan From owner-freebsd-current@freebsd.org Wed Feb 7 11:50:46 2018 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 23DBCEF6FB6 for ; Wed, 7 Feb 2018 11:50:46 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DF4F850FD; Wed, 7 Feb 2018 11:50:45 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?iso-8859-1?Q?M=26S_-_Krasznai_Andr=E1s?= To: =?iso-8859-1?Q?Juan_Ram=F3n_Molina_Menor?= , "freebsd-current@freebsd.org" CC: "manfredantar@gmail.com" , "glebius@freebsd.org" Subject: RE: Panic on Boot - Current AMD64 Thread-Topic: Panic on Boot - Current AMD64 Thread-Index: AQHTn4SGbU2ulYiOtkewDBpbsNdQwqOYuvIAgAATExA= Date: Wed, 7 Feb 2018 11:35:31 +0000 Message-ID: References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> In-Reply-To: Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.4.90] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 11:50:46 -0000 Hi yesterday I experienced the problem, but after completely synchronizing the= src tree (deleting the content of the /usr/src folder and svnlite checkout= etc.) and recompiling the kernel I can boot my FreeBSD-CURRENT (12.0, amd6= 4, r328967) with the default setting (64) for vm.boot_pages. rgds Andr=E1s Krasznai -----Eredeti =FCzenet----- Felad=F3: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@f= reebsd.org] Meghatalmaz=F3 Juan Ram=F3n Molina Menor K=FCldve: 2018. febru=E1r 7. 12:18 C=EDmzett: freebsd-current@freebsd.org M=E1solatot kap: manfredantar@gmail.com; glebius@freebsd.org T=E1rgy: Panic on Boot - Current AMD64 >> I get panic on boot from current kernel. >> Since last night - changes to vm system ? >> World is Current as of this morning >> >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 12.0-CURRENT #0 r328948: Tue Feb 6 11:30:57 PST 2018 >> root at pozo.com >> :/usr/src >> /sys/amd64/compile/pozo amd64 FreeBSD clang version 6.0.0=20 >> (branches/release_60 324090) (based on LLVM 6.0.0) Table 'FACP' at=20 >> 0xdfbc57e8 Table 'APIC' at 0xdfbc585c Table 'ASF!' at 0xdfbc58e0=20 >> Table 'MCFG' at 0xdfbc5943 Table 'TCPA' at 0xdfbc597f Table 'SLIC' at=20 >> 0xdfbc59b1 Table 'HPET' at 0xdfbc5b27 >> ACPI: No SRAT table found >> panic: UMA: Increase vm.boot_pages >> cpuid =3D 0 >> time =3D 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame=20 >> 0xffffffff820bc820 >> vpanic() at vpanic+0x18d/frame 0xffffffff820bc880 >> panic() at panic+0x43/frame 0xffffffff820bc8e0 >> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 >> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 >> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 >> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 >> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 >> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 >> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 >> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 >> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 >> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 >> btext() at btext+0x2c >> KDB: enter: panic >> [ thread pid 0 tid 0 ] >> Stopped at kdb_enter+0x3b: movq $0,kdb_why >> db> bt >> Tracing pid 0 tid 0 td 0xffffffff80ff1240 >> kdb_enter() at kdb_enter+0x3b/frame 0xffffffff820bc820 >> vpanic() at vpanic+0x1aa/frame 0xffffffff820bc880 >> panic() at panic+0x43/frame 0xffffffff820bc8e0 >> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940 >> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0 >> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20 >> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50 >> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0 >> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0 >> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0 >> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20 >> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50 >> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70 >> btext() at btext+0x2c >> db> >=20 >=20 > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad=20 > S440 with 4 GB. >=20 > Workaround: break into the loader prompt and: >=20 > set vm.boot_pages=3D120 > boot >=20 > When booting kernel.old, vm.boot_pages is 64. >=20 > There is something wrong with r328916. >=20 > Hope it helps, > Juan Hi! Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the iss= ue here. Hope it helps, Juan _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/= listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 7 13:07:37 2018 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 07E04F046F6 for ; Wed, 7 Feb 2018 13:07:37 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83A3B685AD; Wed, 7 Feb 2018 13:07:36 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pf0-x22f.google.com with SMTP id 17so280462pfw.11; Wed, 07 Feb 2018 05:07:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7Wog/49uS1dO1qS47KyriWg7Xl0WIIH7f2ofillcDak=; b=chIfQSTpVcrX5tO3B8/KCtP5Kv/UMV8qEbfFgJ0nnF3hLKw1jotaf27VDr2Qm9uBRP i4q6Dl4zGXAfaYvzf1xMdzJ7gKmIh8a0mowejdCuFZqUBh0R9qR61ftaIe1RYfS00bmT lQ76fHi3b8eYGuWNWaqnc1nRuj36yk5uTWS3Cp1zmTq/NoMxFTnTcY2/z/6MsX+ikeTs E/JQ9AMd+flVPUgs8tRbpXUTEvaWv46etMd2OzlSNOdDMM7x+3YR1uGwYc1QU5n+zPnU AhvjQmFVt29WSgXSx6WEzIVimTKNHwksYAuVUALEaBrfhaiLEgGO50X+85IarqczbY0V dm4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7Wog/49uS1dO1qS47KyriWg7Xl0WIIH7f2ofillcDak=; b=cuxb01ToQ3Y8cuRzcZjqXt2Vs2hcLSx3NCZZnWyAQDHsSoW2XIl3oEG1IRDXgDWF0z L7r4JAyZhzHQ/uKKFl9Q1td38YAYYdhXG37g91gEdGP+UBz9d0C/uaNB+Uutkr6QAu2T B0irK++kweOoJ0NuMr7mQKRXv4ifBijSNbG9if3eX9Jgt8Mm5CRe/xUaV81RQKwAQnZP TpHJbO8xQ8o2GlPB1FPVLC7bIsvohg3TcP9BipeV3rSi9401+wy0P7VPPpT8y0iwwG/N 8kx00QSWcy+QJWqlFTxOLWsDi2as5HTAZa1qNjhEo8Hc8pr7ebmNtPYcjxe+RVTZkJ7C EzVA== X-Gm-Message-State: APf1xPCfrwq34O+nKv50lPhIaxjMIQLyUqQhxtPTos4hHB5LZwFN9Ifv eFlKlnXjIUNFOMtgpQLrl+fF9habFhjQGIg10zwuvQ== X-Google-Smtp-Source: AH8x224HRFcJ4hrRKOO/tRlslqu2mmfOoQalq1pSzrRd76rBc+zoEg2X703od2kZXag2QLPgrUk1s4ueb02Yudz9wb8= X-Received: by 10.101.74.132 with SMTP id b4mr5044873pgu.355.1518008855563; Wed, 07 Feb 2018 05:07:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.138.144 with HTTP; Wed, 7 Feb 2018 05:07:34 -0800 (PST) In-Reply-To: <1C97132B-099B-4BAA-9C39-A1BE00481CAC@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> <1517943001.1366.100.camel@freebsd.org> <1C97132B-099B-4BAA-9C39-A1BE00481CAC@jnielsen.net> From: Maurizio Vairani Date: Wed, 7 Feb 2018 14:07:34 +0100 Message-ID: Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. To: John Nielsen Cc: freebsd-current , Daisuke Aoyama , Ian Lepore Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 13:07:37 -0000 2018-02-06 23:02 GMT+01:00 John Nielsen : > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > >> > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > >> since this commit in 2011: > >> https://svnweb.freebsd.org/base?view=revision&revision=218757 > >> > >> So I'm going to add this patch to the port unconditionally once it > >> works. > >> > >> Unfortunately, I can't compile the port with either my patch below or > >> your original replacement version of isboot_ifup(). :( Did you make > >> other changes? Here's the error I'm getting: > >> > >> --- isboot.o --- > >> isboot.c:425:53: error: incomplete definition of type 'struct thread' > >> error = socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); > >> ~~^ > >> /usr/src/sys/sys/systm.h:185:8: note: forward declaration of 'struct > >> thread' > >> struct thread; > >> ^ > >> 1 error generated. > >> > > > > Try adding #include if it's not already in the list. It > > may be that that file got included via pollution from some other header > > file in the past and maybe now that has changed. > > > > If you're already including sys/proc.h then I'm clueless. > > Thanks Ian, that appears to work. > > Maurizio, can you apply the attached patch to a clean ports tree and see > if isboot-kmod will build and function properly for you? This is all the > changes from this thread and the previous one. If you let me know it works > I'll get the port updated. > > > Hi John, I need some help. I am running: # uname -a FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 after upgrading the ports tree with: # portsnap fetch update I have copied the directory /usr/ports/net/isboot-kmod/ in /root/src/isboot-kmod and /root/src/isboot-kmod.orig # ls -l /root/src total 6 drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod.orig -rw-rw-rw- 1 root wheel 5630 Feb 7 11:38 isboot_patch.txt Trying to apply the patch I obtain the error: # cd /root/src # patch -sC < isboot_patch.txt 2 out of 2 hunks failed while patching isboot-kmod/Makefile 5 out of 5 hunks failed while patching isboot-kmod/files/patch-isboot.c What I am missing ? Thanks again for your work. -- Maurizio From owner-freebsd-current@freebsd.org Wed Feb 7 18:30:00 2018 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 ADDE9F1B376 for ; Wed, 7 Feb 2018 18:30:00 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [69.87.218.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49B5C770EA; Wed, 7 Feb 2018 18:29:59 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.23] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail5.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w17ITs1i058293 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Feb 2018 11:29:56 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.23] From: John Nielsen Message-Id: <7D39479C-85AB-45B2-BF39-0566AC073C5A@jnielsen.net> Content-Type: multipart/mixed; boundary="Apple-Mail=_4C5D394E-499F-4656-9C33-02147582A1EE" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. Date: Wed, 7 Feb 2018 11:29:53 -0700 In-Reply-To: Cc: freebsd-current , Daisuke Aoyama , Ian Lepore To: Maurizio Vairani References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> <1517943001.1366.100.camel@freebsd.org> <1C97132B-099B-4BAA-9C39-A1BE00481CAC@jnielsen.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 18:30:00 -0000 --Apple-Mail=_4C5D394E-499F-4656-9C33-02147582A1EE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Feb 7, 2018, at 6:07 AM, Maurizio Vairani = wrote: >=20 > 2018-02-06 23:02 GMT+01:00 John Nielsen : > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > >> > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > >> since this commit in 2011: > >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D218757 > >> > >> So I'm going to add this patch to the port unconditionally once it > >> works. > >> > >> Unfortunately, I can't compile the port with either my patch below = or > >> your original replacement version of isboot_ifup(). :( Did you make > >> other changes? Here's the error I'm getting: > >> > >> --- isboot.o --- > >> isboot.c:425:53: error: incomplete definition of type 'struct = thread' > >> error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); > >> ~~^ > >> /usr/src/sys/sys/systm.h:185:8: note: forward declaration of = 'struct > >> thread' > >> struct thread; > >> ^ > >> 1 error generated. > >> > > > > Try adding #include if it's not already in the list. = It > > may be that that file got included via pollution from some other = header > > file in the past and maybe now that has changed. > > > > If you're already including sys/proc.h then I'm clueless. >=20 > Thanks Ian, that appears to work. >=20 > Maurizio, can you apply the attached patch to a clean ports tree and = see if isboot-kmod will build and function properly for you? This is all = the changes from this thread and the previous one. If you let me know it = works I'll get the port updated. >=20 >=20 > Hi John, I need some help. >=20 > I am running: > # uname -a =20 > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 = 04:48:52 UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC = amd64 >=20 > after upgrading the ports tree with: > # portsnap fetch update >=20 > I have copied the directory /usr/ports/net/isboot-kmod/ in = /root/src/isboot-kmod and /root/src/isboot-kmod.orig > # ls -l /root/src > total 6 > drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod > drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod.orig > -rw-rw-rw- 1 root wheel 5630 Feb 7 11:38 isboot_patch.txt >=20 > Trying to apply the patch I obtain the error: > # cd /root/src > # patch -sC < isboot_patch.txt > 2 out of 2 hunks failed while patching isboot-kmod/Makefile > 5 out of 5 hunks failed while patching = isboot-kmod/files/patch-isboot.c=20 >=20 > What I am missing ? > Thanks again for your work. Not sure but I ran in to similar issues testing here as well. Here's the = "svn diff" patch which does work for me. Note that this one should be = applied from within the isboot-kmod directory. --Apple-Mail=_4C5D394E-499F-4656-9C33-02147582A1EE Content-Disposition: attachment; filename=isboot-kmod-0.2.13_2.diff.txt Content-Type: text/plain; x-unix-mode=0644; name="isboot-kmod-0.2.13_2.diff.txt" Content-Transfer-Encoding: quoted-printable Index: Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- Makefile (revision 461112) +++ Makefile (working copy) @@ -2,7 +2,7 @@ =20 PORTNAME=3D isboot-kmod PORTVERSION=3D 0.2.13 -PORTREVISION=3D 1 +PORTREVISION=3D 2 CATEGORIES=3D net MASTER_SITES=3D http://www.peach.ne.jp/archives/isboot/ DISTNAME=3D isboot-${PORTVERSION} @@ -12,9 +12,7 @@ =20 LICENSE=3D BSD2CLAUSE =20 -BROKEN_aarch64=3D fails to compile: = /usr/src/sys/sys/bus.h:724:10: fatal error: 'device_if.h' file not found BROKEN_armv6=3D fails to compile: implicit declaration = of function 'cp15_pmccntr_get' is invalid in C99 -BROKEN_armv7=3D fails to compile: = /usr/src/sys/sys/bus.h:724:10: fatal error: 'device_if.h' file not found BROKEN_powerpc64=3D fails to compile: pcpu.h: size of array = '__assert_0' is negative =20 USES=3D kmod uidfix Index: files/patch-Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- files/patch-Makefile (nonexistent) +++ files/patch-Makefile (working copy) @@ -0,0 +1,10 @@ +--- Makefile.orig 2015-09-23 22:33:04.000000000 -0600 ++++ Makefile 2018-01-29 10:20:10.453188000 -0700 +@@ -6,6 +6,7 @@ + SRCS=3D isboot.c ibft.c iscsi.c + SRCS+=3D isboot.h ibft.h iscsi_compat.h + SRCS+=3D opt_cam.h ++SRCS+=3D device_if.h bus_if.h + #CFLAGS+=3D -DVIMAGE + #CFLAGS+=3D -DIBFT_VERBOSE + #CFLAGS+=3D -DDEBUG Property changes on: files/patch-Makefile ___________________________________________________________________ Added: fbsd:nokeywords ## -0,0 +1 ## +yes \ No newline at end of property Added: svn:eol-style ## -0,0 +1 ## +native \ No newline at end of property Added: svn:mime-type ## -0,0 +1 ## +text/plain \ No newline at end of property Index: files/patch-isboot.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- files/patch-isboot.c (revision 461112) +++ files/patch-isboot.c (working copy) @@ -1,6 +1,14 @@ ---- isboot.c.orig 2015-11-05 16:50:51 UTC -+++ isboot.c -@@ -347,9 +347,9 @@ isboot_set_v4gw(struct sockaddr_in *gate +--- isboot.c.orig 2015-11-05 09:50:51.000000000 -0700 ++++ isboot.c 2018-02-06 14:23:24.479249000 -0700 +@@ -38,6 +38,7 @@ + #include + #include + #include ++#include + #include + #include + #include +@@ -347,9 +348,9 @@ netmask.sin_addr.s_addr =3D htonl(0); =20 /* delete gateway if exists */ @@ -12,7 +20,7 @@ if (error) { if (error !=3D ESRCH) { printf("rtrequest RTM_DELETE error %d\n", -@@ -359,9 +359,9 @@ isboot_set_v4gw(struct sockaddr_in *gate +@@ -359,9 +360,9 @@ } =20 /* set new default gateway */ @@ -24,7 +32,7 @@ if (error) { printf("rtrequest RTM_ADD error %d\n", error); return (error); -@@ -391,9 +391,9 @@ isboot_set_v6gw(struct sockaddr_in6 *gat +@@ -391,9 +392,9 @@ memset(&netmask.sin6_addr, 0, 16); =20 /* delete gateway if exists */ @@ -36,7 +44,7 @@ if (error) { if (error !=3D ESRCH) { printf("rtrequest RTM_DELETE error %d\n", -@@ -403,9 +403,9 @@ isboot_set_v6gw(struct sockaddr_in6 *gat +@@ -403,9 +404,9 @@ } =20 /* set new default gateway */ @@ -48,3 +56,42 @@ if (error) { printf("rtrequest RTM_ADD error %d\n", error); return (error); +@@ -417,28 +418,36 @@ + isboot_ifup(struct ifnet *ifp) + { + struct ifreq ifr; ++ struct socket *so; + struct thread *td; + int error; +=20 + memset(&ifr, 0, sizeof(ifr)); + td =3D curthread; +=20 ++ error =3D socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, = td); ++ if (error) { ++ printf("%s: socreate, error=3D%d\n", __func__, error); ++ return (error); ++ } ++ + /* boot NIC */ + strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name)); +=20 + /* set IFF_UP */ +- error =3D ifioctl(NULL, SIOCGIFFLAGS, (caddr_t)&ifr, td); ++ error =3D ifioctl(so, SIOCGIFFLAGS, (caddr_t)&ifr, td); + if (error) { + printf("ifioctl SIOCGIFFLAGS\n"); + return (error); + } + ifr.ifr_flags |=3D IFF_UP; +- error =3D ifioctl(NULL, SIOCSIFFLAGS, (caddr_t)&ifr, td); ++ error =3D ifioctl(so, SIOCSIFFLAGS, (caddr_t)&ifr, td); + if (error) { + printf("ifioctl SIOCSIFFLAGS\n"); + return (error); + } +=20 ++ soclose(so); + return (0); + } +=20 Index: files/patch-iscsi.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- files/patch-iscsi.c (nonexistent) +++ files/patch-iscsi.c (working copy) @@ -0,0 +1,27 @@ +--- iscsi.c.orig 2015-11-05 09:50:51.000000000 -0700 ++++ iscsi.c 2018-01-29 10:20:00.586277000 -0700 +@@ -1070,9 +1070,11 @@ + return (n); + } +=20 +- +-#if __FreeBSD_version >=3D 1100000 ++#if __FreeBSD_version >=3D 1200051 + static void ++isboot_free_mbufext(struct mbuf *m) ++#elif __FreeBSD_version >=3D 1100000 ++static void + isboot_free_mbufext(struct mbuf *m, void *p, void *optarg) + #elif __FreeBSD_version >=3D 1000050 && __FreeBSD_version < 1100000 + static int +@@ -1082,7 +1084,9 @@ + isboot_free_mbufext(void *p, void *optarg) + #endif + { +- ++#if __FreeBSD_version >=3D 1200051 ++ void *p =3D m->m_ext.ext_arg1; ++#endif + ISBOOT_TRACE("isboot_free_mbufext\n"); + if (p =3D=3D NULL) + #if __FreeBSD_version >=3D 1000050 && __FreeBSD_version < 1100000 Property changes on: files/patch-iscsi.c ___________________________________________________________________ Added: fbsd:nokeywords ## -0,0 +1 ## +yes \ No newline at end of property Added: svn:eol-style ## -0,0 +1 ## +native \ No newline at end of property Added: svn:mime-type ## -0,0 +1 ## +text/plain \ No newline at end of property --Apple-Mail=_4C5D394E-499F-4656-9C33-02147582A1EE-- From owner-freebsd-current@freebsd.org Wed Feb 7 20:36:02 2018 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 E8752ED6BEA for ; Wed, 7 Feb 2018 20:36:01 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 747817DDAE for ; Wed, 7 Feb 2018 20:36:01 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id w17KZprO014280 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Feb 2018 12:35:51 -0800 (PST) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id w17KZoCX014279; Wed, 7 Feb 2018 12:35:50 -0800 (PST) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 7 Feb 2018 12:35:50 -0800 From: Gleb Smirnoff To: Juan =?iso-8859-1?Q?Ram=F3n?= Molina Menor Cc: freebsd-current@freebsd.org, manfredantar@gmail.com Subject: Re: Panic on Boot - Current AMD64 Message-ID: <20180207203550.GM1063@FreeBSD.org> References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 20:36:02 -0000 On Wed, Feb 07, 2018 at 12:18:26PM +0100, Juan Ramón Molina Menor wrote: J> > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 J> > with 4 GB. J> > J> > Workaround: break into the loader prompt and: J> > J> > set vm.boot_pages=120 J> > boot J> > J> > When booting kernel.old, vm.boot_pages is 64. J> > J> > There is something wrong with r328916. J> J> Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the J> issue here. r328982 should fix the boot without specifing vm.boot_pages. I'm sorry for problems. -- Gleb Smirnoff From owner-freebsd-current@freebsd.org Thu Feb 8 08:31:33 2018 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 59AFFF0E741 for ; Thu, 8 Feb 2018 08:31:33 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B940C7A8EA for ; Thu, 8 Feb 2018 08:31:29 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MA8hF-1eZ0NM2eEr-00BO1c; Thu, 08 Feb 2018 09:31:21 +0100 Date: Thu, 8 Feb 2018 09:31:15 +0100 From: "O. Hartmann" To: freebsd-jails@freebsd.org, freebsd-current Subject: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:OUWcXoiXsA4ganD2clqBdMmWm6X8JceTeupdg6AH/f7gwYf9zew /Esqgrk3muoJNkioHhCG5uEQRVnKHrnSTiE0AKhYV9NS9w52PNZeFq872dPxd3DqGoGyeQS ympYRzR3PdJ7cMf4CWYF13tkvrKURzTL9W6OvWrHy6EgeQ/3CnOZVSjtVER8CD2cquJCjwx 8GaYgZR7e7VT50xCqH/vw== X-UI-Out-Filterresults: notjunk:1;V01:K0:MN1Q0iqUwWU=:Ev1QrE9CBbvVTZVjCZxnWm jjgTD23H5RlEfNt9SbwXsPtRKrvfYj0jNnZF38Wnr2le9h6+pNfODXaWRT+w97MwhEe1MCr8E kQAQ2HxjZ6UQnuUkAM/WbC5fxIubR/B3Luu8KzSHbX6F2ZZa6unYA2uSaSokaBa7VyYnxKaaC 0FfFB1CL9BEmGJxTkviCdri8JyPrnBPuxI2RG2O9zBUGhcMdxwu+dG8dBEbQot6EMAx2g1tzI Jx2JdkeugOTRBMyq0mu5Kwpc5nvdKCdkqnsLlRab8OUxw5Zh/CyF+velbWLCbdLHxbAk1hvPc VU71bxmBSuwSoqoe18OjsPOlIkDskZ8/oSgHUcvdJ7bbMBbwaWu6VOOoZ5nxPVNvEVTZ8IZPs OwVPmLdlO4PRFMeNlHUqg0HWShgsIHYzvufz8aOdNFttKq06nDc5ZJCmADIzy4ApL1MSQ0gS1 fC54C9ZOANYK86B+HHHDCML3TqyWggL8aPYmlFDwmkUzTq9nQ2BteidY04+tZ1rUiwBftpRrQ cqwjIY831RQEpBpJ6c0wTwtq3rj9ToO1SW3lpIt2ca3HcfG+O9lvsSX+aLM1yWkyV+csOHKfk LZJN9clKDaZTT7/pe9KE0Xdvs9lyF0Z+m9XZJYH4rp/1RvKEFdE90OeFgoGReCBE3e8WNbS+d pSSqnj7+pFVkFaDcNU0yuTjfCPowD6eYnpdWZFx9t7CTS0VdOWajb8QfO9WPxPqJ4dhQPBBxB BmQ/YYESs5CImA30U6xkXU1DnDPJw366/mtO+jWbm7ay3Lu6Tjfa65ek6SF6BHarzfq9jv0pw X/52tcySp/U9P6ZPa/s6vdZBmdJ5LjxY3vw5m/EXIqEYZdt99s= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 08:31:33 -0000 Hello, I fight with the following problem without any kind of success and I need some help and/or advice. We are running several CURRENT and 11.1-RELENG-p6 boxes. CURRENT is at the most recent version as of today. VIMAGE is compiled in into all kernels. IPFW is compiled into all kernels and is the one and only firewall used. On CURRENT, the host's ipfw is set to "OPEN" (using the rc.-scripts so far). By convention, I address the host running the kernel by "host". Every jail is created/configured with its own "vnet" cloned network stack (vnet=new). All hosts do have at least three physical NICs. The host itself is supposed to be member of the "friendly" network via a dedicated NIC. The two remaining NICs are split into fractions belonging to an "hostile" network on which I'd like to place exposed jails (for now), and to the "friendly" network, on which also jails will be hosted, but via a dedicated NIC. Inbetween those two networks, the host will have a third, intermediate, network, call it the "service" network. The following will be true for ALL jails created, including the host itself: net.link.bridge.pfil_member=0 net.link.bridge.pfil_bridge=0 net.link.bridge.pfil_onlyip=0 First, I clone/create three bridge(4) devices, bridge0 (considered to be the "glue" between the "service" jails), bridge1 (considered to be the glue between the jails on the friednly network side) and bridge2, which is the glue between the jails on the hostile side. bridge1 has eth1 as a member, which provides the physical access to the friendly network, eth2 is member of bridge2, which provides access to the hostile network. By convention, when creating epair(4), the a-portion belongs to the jail itself and is assigned with an IPv6 address. The b-portion of the epair(4) is member of its bridge according to its realm (friendly, service or hostile network). Additionally, there is a special jail, the router, which has three epair(4) devices, the b-portion of the epair is member of the appropriate bridge(4) and this router jail has static routes assigned, pointing to the appropriate epairXXXa that is suppoesd to be the link into the correct bridge/network. IPFW is set to open on this jail (for now). On this special jail it is set: net.inet.ip.forwarding=1. I hope, the topology is clear so far. All epairs or epair endpoints as well as the bridges are UP! Double checked this. Jails on bridge0 (service net) have IPs in the range 10.10.0.0/24, the b-portion of the routing jail's epair is member of bridge0, as described above, and the a-portion of the epair has IP 10.10.0.1. Default route on each jeail on bridge0 is set to 10.10.0.1 accordingly. Consider a similar setup on the other jails on the friendly and hostile network, except the fact that their bridges do have a physical NIC to which they may have access to a real network. The setup might not be ideal and/or applicable for the purpose of separartion of networks virtually, but that shouldn't be the subject here. More important is that I assume that I haven't understood some essentials, because the setup doens't work as expected. Furthermore, it behaves on FreeBSD 11.1-RELENG-p6 sometimes completely unpredictable - but in that special case, I think I ran IPFW on the host as "WORKSTATION" and dynamic rules may play an important role here. But focussing on the CURRENT box, the host's IPFW is set to OPEN. With jexec -l hostA I gain access to host A on the "service" bridge0 and I want to ping its neighbour, hostB, on the same bridge and in the same net. It doesn't work! From the routing jail, I CAN NOT ping any host on bridge0. The routing jail has these network settings: [... routing jail ...] lo0: flags=8049 metric 0 mtu 16384 options=600003 inet 127.0.0.1 netmask 0xff000000 groups: lo [epair to bridge0 - service net] epair4000a: flags=8843 metric 0 mtu 1500 options=8 ether 02:57:d0:00:07:0a inet 10.10.0.1 netmask 0xffffff00 broadcast 10.10.0.255 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair [epair to bridge1, friendly net] epair4001a: flags=8843 metric 0 mtu 1500 options=8 ether 02:57:d0:00:09:0a inet 192.168.11.1 netmask 0xffffff00 broadcast 192.168.11.255 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair [epair to bridge2, hostile net] epair4002a: flags=8843 metric 0 mtu 1500 options=8 ether 02:57:d0:00:0b:0a inet 10.10.10.1 netmask 0xfffffc00 broadcast 10.10.10.255 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair routing: netstat -Warn Routing tables Internet: Destination Gateway Flags Use Mtu Netif Expire 10.10.0.0/24 link#2 U 11 1500 epair4000a 10.10.0.1 link#2 UHS 4 16384 lo0 10.10.10.0/24 link#4 U 210 1500 epair4002a 10.10.10.1 link#4 UHS 44 16384 lo0 127.0.0.1 link#1 UH 0 16384 lo0 192.168.11.0/24 link#3 U 9 1500 epair4001a 192.168.11.1 link#3 UHS 0 16384 lo0 Consider a jail hostCC on bridge2 in the hostile network, IP 10.10.10.128. I can ping that jail, although it has conceptionally the very same setup as the unreachable jails on bridge0! It is weird. On bridge0, no jail can be pinged, it looks like the ethernet is somehwo down on that bridge. I would expect to ping each host member of the very same bridge! On 11.1-RELENG-p6, there are other weird issues, I was able to ping those jails, even ssh to them, but that vanished after several restarts of the jails system (each bridge, epair is created by jail.conf and destroyed after the jails has been deactivated and doing so a considerable amount brings down the FreeBSD 11.1-RELENG-p6 host verys successfully - it crashes!). So, since VIMAGE is now default in CURRENT's GENERIC, I consider its functionality at least "predictable", but I fail somehow here. Does someone have a deeper insight or realise the mistake I'm celebrating here? Thanks in adavnce, Oliver From owner-freebsd-current@freebsd.org Thu Feb 8 09:58:36 2018 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 8E25BF14C90 for ; Thu, 8 Feb 2018 09:58:36 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.10]) (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 307147E69F for ; Thu, 8 Feb 2018 09:58:35 +0000 (UTC) (envelope-from listjm@club.fr) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) by msfrf2627.sfr.fr (SMTP Server) with ESMTP id 481D51C00043C for ; Thu, 8 Feb 2018 10:58:34 +0100 (CET) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juanmolina@sfr.fr) by msfrf2627.sfr.fr (SMTP Server) with ESMTPSA; Thu, 8 Feb 2018 10:58:33 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=juanmolina@sfr.fr From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Subject: Panic on Boot - Current AMD64 To: freebsd-current@freebsd.org Cc: glebius@freebsd.org References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> Message-ID: <0f14ae85-7fbe-9486-0aed-441cf51879bb@club.fr> Date: Thu, 8 Feb 2018 10:58:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> X-sfr-mailing: LEGIT Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 09:58:36 -0000 > On Wed, Feb 07, 2018 at 12:18:26PM +0100, Juan Ramón Molina Menor wrote: > J> > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 > J> > with 4 GB. > J> > > J> > Workaround: break into the loader prompt and: > J> > > J> > set vm.boot_pages=120 > J> > boot > J> > > J> > When booting kernel.old, vm.boot_pages is 64. > J> > > J> > There is something wrong with r328916. > J> > J> Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the > J> issue here. > > r328982 should fix the boot without specifing vm.boot_pages. > > I'm sorry for problems. > > -- > Gleb Smirnoff Yes, it is fixed, thanks! From owner-freebsd-current@freebsd.org Thu Feb 8 12:32:20 2018 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 A67DFF20648 for ; Thu, 8 Feb 2018 12:32:20 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A19484A94; Thu, 8 Feb 2018 12:32:20 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pg0-x22b.google.com with SMTP id t4so515623pgp.8; Thu, 08 Feb 2018 04:32:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dayRaF4YSNv7AW8Xy6d207+iupuIjD+Mdrw0UJcHsIg=; b=VYhVqFFH81wlgo0sdmzDLUK2TquE+8fwSFVBTAIUsFDfZ5b3IzZ+Lf7Yfw3WQJTciO +aTJ+hb4FwtFkYAK8fzzzksC4hhCNYQOk1O4aXQKU2JcdgoGV0scCKX1RGjYO5iPKfYl mGIAoqX6jLDEMobVGORBN6HwrpNn6lztSrmdfbfcfNTWBRmyX5FvLMzbGG8NMKJlijE4 G/6n6nIdkFUSN3UupcIUOYViueZYYSeEuLR4KK66BF3iblr2D0bQO0BwT3CJXXQ8DUR5 IThV8l+PGwywnvvYByiPW2YsThPjm4vJ7f7lLSJL8VQbGmdxqKbG1AX1TAr9jt8Ghjv2 vRZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dayRaF4YSNv7AW8Xy6d207+iupuIjD+Mdrw0UJcHsIg=; b=mmepGm3AKIdfinya4j6zugwePw5of2Ec5gkztlLFAP+y3c9+vfgqH16rXkKrPp3oR7 fl7ECcrJ6f+D23fa3KcKU1DzzIg4GYc5rHyma7AhQeZk8lbA3sgo1sWWdBEbT2VPyc7U Y13+QXLVxv1wPWwAN6mrKNm4lFpnYuVZjKfL9JMTg309Uj0DQsgnHEN1fCFbve6XxFof yTb3zRx+pwx+ZrEFIr2VhSNiaO0BXYCJiO3e8U5r26lrlqyPCN5XpVh0iHH+w4+oTzHx 6rCD8b0cg9X/B7TJoOSkGA1PWH6318rnNR8JqDMSv0mspY1B9+IF0Xo8gA3s2kPD499h W4nw== X-Gm-Message-State: APf1xPA0zyKBT2OLTirp1Z6gqywi5Hafuku1L0oQJ3hKurQHKDFCd3LH K7+cU74nYzEQE1JDeGSWFSLZyts1ocvId95krFBHWA== X-Google-Smtp-Source: AH8x227bPpFlf7hHZKkptF91MfiI/oVVNPem75EVaFcRHz/gZp60gj64eXG15oP76hX/b0GneTbq5VVhAV3PEweL+D8= X-Received: by 10.98.72.18 with SMTP id v18mr524142pfa.107.1518093139220; Thu, 08 Feb 2018 04:32:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.138.144 with HTTP; Thu, 8 Feb 2018 04:32:18 -0800 (PST) In-Reply-To: <7D39479C-85AB-45B2-BF39-0566AC073C5A@jnielsen.net> References: <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net> <5EDB0747-41DE-4ECF-925E-EF24FAA550F3@jnielsen.net> <1517943001.1366.100.camel@freebsd.org> <1C97132B-099B-4BAA-9C39-A1BE00481CAC@jnielsen.net> <7D39479C-85AB-45B2-BF39-0566AC073C5A@jnielsen.net> From: Maurizio Vairani Date: Thu, 8 Feb 2018 13:32:18 +0100 Message-ID: Subject: Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module. To: John Nielsen Cc: freebsd-current , Daisuke Aoyama , Ian Lepore Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 12:32:20 -0000 2018-02-07 19:29 GMT+01:00 John Nielsen : > > On Feb 7, 2018, at 6:07 AM, Maurizio Vairani > wrote: > > > > 2018-02-06 23:02 GMT+01:00 John Nielsen : > > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > > >> > > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > > >> since this commit in 2011: > > >> https://svnweb.freebsd.org/base?view=revision&revision=218757 > > >> > > >> So I'm going to add this patch to the port unconditionally once it > > >> works. > > >> > > >> Unfortunately, I can't compile the port with either my patch below or > > >> your original replacement version of isboot_ifup(). :( Did you make > > >> other changes? Here's the error I'm getting: > > >> > > >> --- isboot.o --- > > >> isboot.c:425:53: error: incomplete definition of type 'struct thread' > > >> error = socreate(AF_INET, &so, SOCK_DGRAM, 0, td->td_ucred, td); > > >> ~~^ > > >> /usr/src/sys/sys/systm.h:185:8: note: forward declaration of 'struct > > >> thread' > > >> struct thread; > > >> ^ > > >> 1 error generated. > > >> > > > > > > Try adding #include if it's not already in the list. It > > > may be that that file got included via pollution from some other header > > > file in the past and maybe now that has changed. > > > > > > If you're already including sys/proc.h then I'm clueless. > > > > Thanks Ian, that appears to work. > > > > Maurizio, can you apply the attached patch to a clean ports tree and see > if isboot-kmod will build and function properly for you? This is all the > changes from this thread and the previous one. If you let me know it works > I'll get the port updated. > > > > > > Hi John, I need some help. > > > > I am running: > > # uname -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 > 04:48:52 UTC 2018 root@releng3.nyi.freebsd.org:/ > usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > > after upgrading the ports tree with: > > # portsnap fetch update > > > > I have copied the directory /usr/ports/net/isboot-kmod/ in > /root/src/isboot-kmod and /root/src/isboot-kmod.orig > > # ls -l /root/src > > total 6 > > drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod > > drwxr-xr-x 3 root wheel 6 Feb 7 13:46 isboot-kmod.orig > > -rw-rw-rw- 1 root wheel 5630 Feb 7 11:38 isboot_patch.txt > > > > Trying to apply the patch I obtain the error: > > # cd /root/src > > # patch -sC < isboot_patch.txt > > 2 out of 2 hunks failed while patching isboot-kmod/Makefile > > 5 out of 5 hunks failed while patching isboot-kmod/files/patch-isboot.c > > > > What I am missing ? > > Thanks again for your work. > > Not sure but I ran in to similar issues testing here as well. Here's the > "svn diff" patch which does work for me. Note that this one should be > applied from within the isboot-kmod directory. > > With this patch I receive this error : # pwd /root/src/isboot-kmod # patch -sC < ../isboot-kmod-0.2.13_2.diff.txt 2 out of 2 hunks failed while patching Makefile 5 out of 5 hunks failed while patching files/patch-isboot.c From owner-freebsd-current@freebsd.org Thu Feb 8 13:24:45 2018 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 76F31F03814 for ; Thu, 8 Feb 2018 13:24:45 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14B1587EF9; Thu, 8 Feb 2018 13:24:45 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id t78so3455616oih.4; Thu, 08 Feb 2018 05:24:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=hBBbJSBRkfbSYssMSbXW/WhnN/Pv6DO+QfglXrcbIRs=; b=jth58CmfqANJgcMX/kE/utesF+ZFxX66mdGy/cItF5KLTYBuV4W53tlTUQbFINhPH1 fVWKJG2PB39zEbSxtq0YiI7zyJkqswC6qVUYW7BejE2hduLIGkrLbt+Fmg/Ae1DmCj5U R/l7g8mqv4yMsJe/7RmKnsuhRejkBpSxm4/8sCShnVBqoycMRHysbS/LifYsMuVxBG4S 5J1yEbKMR1zOrlnGO/ROZLYPuChebIWFYOPn9D0NQMzfwwQduKIsB74/C/51WtOaQxhF 5ThCb3RkKQB07qlUB4uSIqPlF93USzD526C/cCN3UItgPtnTDSEsjbpG4ZyGbDU3lJRJ QRAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=hBBbJSBRkfbSYssMSbXW/WhnN/Pv6DO+QfglXrcbIRs=; b=CDigjqvTK2ldLX/IxUQEQxMqifXF+7SwLnCfIm4Wep/c8Fpv6RjSx4UZw0Al0nztRY 4IScGOCL5SWJuWXDs4NG3nTJX0v3oG+tiOCEDqP/hgSKKulfMpjAyt3XnlS5h9EqNUNJ SNUROopSDUq/Y+x4zjSHn8BVg3cWX/2v/YeJ8yg9xZDAw+s3aNf0xxbKeS1OuNk09np7 rH9TTCwPLtysSeyUDZel4KmweXpNXKkiZ8ic+PSDdcfNiGPl6triZxcw9cgetW8KYTUP Nl5KYVZT40/fJO8w0EF1e0FeWYvhbShfwC9Zp8QxfMfRClmCG6qjI0yc2WgUO4RyAKkG 32CQ== X-Gm-Message-State: APf1xPCMAFBQmQ6IbCfigVfSB43zMPy29rX7Uq3y12iH/ik0zmIwXhRG lrvdCYSZkQMkroIhMnSJsHE03gy+SFGX0WETGziQr0Kr X-Google-Smtp-Source: AH8x227dV1YEky+OnPQhzn8J/CaBgplBLL6aqeJd4KO9kDAjmQwzFU9jEWdjBcFI0Z2aBMC1nMZcUbAMbYrIfct7ePM= X-Received: by 10.202.91.84 with SMTP id p81mr449470oib.232.1518096284261; Thu, 08 Feb 2018 05:24:44 -0800 (PST) MIME-Version: 1.0 Sender: uspoerlein@gmail.com Received: by 10.157.39.3 with HTTP; Thu, 8 Feb 2018 05:24:43 -0800 (PST) From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Thu, 8 Feb 2018 14:24:43 +0100 X-Google-Sender-Auth: JZmmHk2jHv1XCqxka_fWP-BIsGY Message-ID: Subject: openssl in base should install c_rehash To: freebsd-current@freebsd.org, Jung-uk Kim Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 13:24:45 -0000 Hey, c_rehash has somehow disappeared from the base system. We still install the manpage it seems, but the tool itself is missing. Can we have that back? root@acme:/etc/ssl# locate c_rehash ... /usr/share/openssl/man/man1/c_rehash.1.gz /usr/src/crypto/openssl/doc/apps/c_rehash.pod /usr/src/secure/usr.bin/openssl/man/c_rehash.1 The port seems to install it just fine: root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ /usr/ports/security/openssl/pkg-plist:bin/c_rehash /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm reading the history with git pickaxe right). Cheers, Uli From owner-freebsd-current@freebsd.org Thu Feb 8 13:52:23 2018 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 32D8AF057D0 for ; Thu, 8 Feb 2018 13:52:23 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [138.201.35.217]) (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 CC32369074 for ; Thu, 8 Feb 2018 13:52:22 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.bultmann.eu (unknown [IPv6:2a00:c380:c0d5:1:f844:c372:df6f:2f38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 12ABDDB13 for ; Thu, 8 Feb 2018 13:52:15 +0000 (UTC) Subject: Re: openssl in base should install c_rehash To: freebsd-current@freebsd.org References: From: Jan Bramkamp Message-ID: Date: Thu, 8 Feb 2018 14:52:14 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 13:52:23 -0000 On 08.02.18 14:24, Ulrich Spörlein wrote: > Hey, > > c_rehash has somehow disappeared from the base system. We still install the > manpage it seems, but the tool itself is missing. Can we have that back? > > > root@acme:/etc/ssl# locate c_rehash > ... > /usr/share/openssl/man/man1/c_rehash.1.gz > /usr/src/crypto/openssl/doc/apps/c_rehash.pod > /usr/src/secure/usr.bin/openssl/man/c_rehash.1 > > > The port seems to install it just fine: > > root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ > /usr/ports/security/openssl/pkg-plist:bin/c_rehash > /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz > > It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm reading the > history with git pickaxe right). The LibreSSL port lacks a c_rehash script as well. Putting c_rehash back into base wouldn't solve the problem because it requires Perl 5. From owner-freebsd-current@freebsd.org Thu Feb 8 16:51:44 2018 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 E32C9F129B1 for ; Thu, 8 Feb 2018 16:51:43 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8301970AB2 for ; Thu, 8 Feb 2018 16:51:43 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-yw0-x231.google.com with SMTP id m84so3069337ywd.5 for ; Thu, 08 Feb 2018 08:51:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=SB9NwyqFxZC9An+GnoW5ZZ44qFTuqfv/8r9DbTzOgmg=; b=l96Mi5l5BYczTuQZuRltxL1fLQAOEweDwM7eKeAjSYz0p5y1Y8Hli6t7ilQYmVkvaM nb75X/RjmV2BZWq0IV+QqfSXX/ZC30qXY4Vu28jjGaXqtLdlT01DCrA/64NJIX+cyQ/L JwZaO2QxTFotP8BBQAd7hOGicze+Pbm7wDG1Ao990/34zT5xZ2sm4j+oYTXeWCRycBy2 af6Qo9O3F3VQRiJOUROzvTcs8UI7eVt9hAuY8V1I2Ntbzx+vU15QKB3Dk2E3NFwyCjkd ebd+gQ0/sKPDhPe5TRLRaJ9JnXZeD9KcWddkqBnRwoIze+kUNLgyLlXCU2Yt2KG+icDY DMEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=SB9NwyqFxZC9An+GnoW5ZZ44qFTuqfv/8r9DbTzOgmg=; b=hvTF29VvUBGEUTkdTZUSzTm7J3745gaWmeIbMx/B4LCZD4HMZm1JlX1REv1UoIGr1n 7ITdW2myoodk2KdrUo5bvyC5N2cv0k5nfI08yHyg2TISPBFwB9VdAUye2Trm+36s5RkQ FGNf9465Lg5yYRNaboP16DJiEg4isKztGpv9CbOUfPxbjiQvowhxfxepJnJgMCFBc1Ab psO1B5qXHFYKb1PfBt1Dz9uU190hkq4UD+UkP1LEywaf08YzI7NrCfB14+FNVvxcxMLb 91/lOz0fGOQpfQN8T96msDd9kzQ6300v/4MEJ1etfYTTosRxsVBnHlKC6WJrryFA1fmp dreg== X-Gm-Message-State: APf1xPDup3L7m+Dwk0RV0GHYQcnW1O/7g+sgC0AEMnNaRQI665TaSLg/ 8m1M0HUSeDKAcz8YKrEA2KcIadMWzMeAFESoIf5toia4VXO9/tejPd822v8+4wafLgkbIV7SiQf Tus3qSmttUHlOl4IPOG/vqtbvmepsmb3B32b6HO+9N8aThRwp7DvGEESnULMieF+/prFlvCEvK7 DH1YcAcGtXgzQ= X-Google-Smtp-Source: AH8x226STT7b7R2rL9j+xaqIhGqyZKDf7DQH+5e3sOJNO3CbyEq3i3f91woF3k93GTUg9yhV5yMvLQ== X-Received: by 10.129.159.140 with SMTP id w134mr1020615ywg.469.1518108702436; Thu, 08 Feb 2018 08:51:42 -0800 (PST) Received: from zen.clue.co.za ([64.53.114.237]) by smtp.gmail.com with ESMTPSA id x143sm126767ywx.34.2018.02.08.08.51.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Feb 2018 08:51:41 -0800 (PST) To: FreeBSD Current From: Ian FREISLICH Subject: I2C trackpad Message-ID: Date: Thu, 8 Feb 2018 11:27:23 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 16:51:44 -0000 Hey, I recently acquired a new laptop (Asus UX490U) which for the most part works with current except that: 1. Sound output doesn't work. 2. The trackpad doesn't work. I'm not bothered about sound and I haven't investigated that yet.=C2=A0 The trackpad not working is a nuisance, but I don't think that there's a short term fix.=C2=A0 I think it's connected via an I2C bus on one of two I= 2C controllers that don't have a driver attached: none2@pci0:0:21:0:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 class=3D0x118000 card=3D0x= 1c301043 chip=3D0x9d608086 rev=3D0x21 hdr=3D0x00 =C2=A0=C2=A0=C2=A0 vendor=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Intel Corporation' =C2=A0=C2=A0=C2=A0 device=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Sunrise Point-LP Ser= ial IO I2C Controller' =C2=A0=C2=A0=C2=A0 class=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D dasp none3@pci0:0:21:1:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 class=3D0x118000 card=3D0x= 1c301043 chip=3D0x9d618086 rev=3D0x21 hdr=3D0x00 =C2=A0=C2=A0=C2=A0 vendor=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Intel Corporation' =C2=A0=C2=A0=C2=A0 device=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Sunrise Point-LP Ser= ial IO I2C Controller' =C2=A0=C2=A0=C2=A0 class=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D dasp I've done some research and it looks like support is a long way off but I'm hoping someone has a work in progress I can test or hack on. Ian --=20 Ian Freislich --=20 From owner-freebsd-current@freebsd.org Thu Feb 8 17:41:23 2018 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 3CD2DF16481 for ; Thu, 8 Feb 2018 17:41:23 +0000 (UTC) (envelope-from callenjohan@gmail.com) Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAB6E72EBA for ; Thu, 8 Feb 2018 17:41:22 +0000 (UTC) (envelope-from callenjohan@gmail.com) Received: by mail-ot0-x22d.google.com with SMTP id f56so5078638otj.13 for ; Thu, 08 Feb 2018 09:41:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=eoXfrI4nCWvzOG0qsLJIbzyeGqm2QydTmy+McYn3dIQ=; b=BHkcxgF/EPSjZU7L9gylpaiqEXjGuW6mjHRrJ8PZkTfY4zE/M7wdwhyGRctLYPosvm mYd6ZMxmtk2vWFcnpWvmnWgQ9Lv7tkZbS5KqWGgnxkHVc4qPU/L2/wYMcalZj6jH7C0B ktfYvK5cuNZWSA/VBwezKU/XK2rsdZL3Umq7GZlcP9HUHWYpLssPkBA8hrNRPp15Xbno 4tA+vZ2kLztl7Kz6n+F/f94kMFEeLKugqEhZojIsqd8MRXzFiwxw6pbxQ2PuTY/wDFYb hwr7J3Ikskw6LfXXTGaqTsP4QHK13X7X+Yia819sxr7GwZEkHIQ+LyGHln38B2AUztAU gDbw== 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=eoXfrI4nCWvzOG0qsLJIbzyeGqm2QydTmy+McYn3dIQ=; b=owFNVbVjurLUsPphhts5BOEGbVqPYsljCOuqAFtpnDZS4cmBDkVxDullZv5RWnLcZX pVyp9KqBzlvJVU4Ek1lXfZu3MTvNxrhA4x67HF9luVk8WuyLp0qsdg2CQiR6LBRBHgGm 2PoQvyI4kc3qY5FyqyYSAajyZXT/1baZ2ECypAwwJuo4kt70HiM04Kl5VMOCMWuVwceN ogjkKBXvpuy0yhW7h1RWJxciPZBJ1SIWkrQFvaIE1YKzW6ZsV1cmMjRQrrNVX7I1EIhG 3KYUjL0+KV8KQ7sCc2+iahMC0l30sh3ytOfXiQJPCtF6wGSqnTw56ky13pdTTZYV3CfD YwTQ== X-Gm-Message-State: APf1xPAK05mGUkQJzqDuxxNImLNg52mE/p++EVsNMvETSmVcglpX2+B9 OSJbNnkyBK26ZP8XcHcxLDNCe5ZvD7tw4hF0/xmBHQ== X-Google-Smtp-Source: AH8x227tPKSR/IWowoX2y2xQwLGLaPTUMngU2UO2QWAeGTmL2K1ustC/OAIfarSoMekTKpuosLcLvLWF6mTlsezeWsk= X-Received: by 10.157.15.225 with SMTP id m30mr1111385otd.215.1518111681662; Thu, 08 Feb 2018 09:41:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.177.194 with HTTP; Thu, 8 Feb 2018 09:41:21 -0800 (PST) From: johan callen Date: Thu, 8 Feb 2018 18:41:21 +0100 Message-ID: Subject: KDE crashed To: FreeBSD Current X-Mailman-Approved-At: Thu, 08 Feb 2018 18:09:21 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 17:41:23 -0000 Hi, Just after update my system on FreeBSD - HEAD, r328986, I have a crash on my KDE with this message : reading pre-existiting kdmrc /usr/local/share/config/kdm/kdmrc shared object "libdl.so.1" not found, required by "kdm" Desinstall and reinstall doesn't work by the way. Anyone has an idea to solve it? Thanks to all, Johan From owner-freebsd-current@freebsd.org Thu Feb 8 19:47:28 2018 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 BF025F1F838 for ; Thu, 8 Feb 2018 19:47:28 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 57C807915D for ; Thu, 8 Feb 2018 19:47:28 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1ejsAA-000ENu-Ql; Thu, 08 Feb 2018 11:47:19 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w18JlH52055297; Thu, 8 Feb 2018 11:47:17 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 8 Feb 2018 11:47:17 -0800 From: Oleksandr Tymoshenko To: Ian FREISLICH Cc: FreeBSD Current Subject: Re: I2C trackpad Message-ID: <20180208194717.GA55269@bluezbox.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Ian FREISLICH (ian.freislich@capeaugusta.com) wrote: > Hey, > > I recently acquired a new laptop (Asus UX490U) which for the most part > works with current except that: > > 1. Sound output doesn't wor [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 19:47:28 -0000 Ian FREISLICH (ian.freislich@capeaugusta.com) wrote: > Hey, > > I recently acquired a new laptop (Asus UX490U) which for the most part > works with current except that: > > 1. Sound output doesn't work. > 2. The trackpad doesn't work. > > I'm not bothered about sound and I haven't investigated that yet.  The > trackpad not working is a nuisance, but I don't think that there's a > short term fix.  I think it's connected via an I2C bus on one of two I2C > controllers that don't have a driver attached: > > none2@pci0:0:21:0:      class=0x118000 card=0x1c301043 chip=0x9d608086 > rev=0x21 hdr=0x00 >     vendor     = 'Intel Corporation' >     device     = 'Sunrise Point-LP Serial IO I2C Controller' >     class      = dasp > none3@pci0:0:21:1:      class=0x118000 card=0x1c301043 chip=0x9d618086 > rev=0x21 hdr=0x00 >     vendor     = 'Intel Corporation' >     device     = 'Sunrise Point-LP Serial IO I2C Controller' >     class      = dasp > > I've done some research and it looks like support is a long way off but > I'm hoping someone has a work in progress I can test or hack on. There is work in progress for I2C controller, not sure about touchpad part: https://reviews.freebsd.org/D13654 -- gonzo From owner-freebsd-current@freebsd.org Thu Feb 8 20:00:17 2018 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 1DE64F2088D for ; Thu, 8 Feb 2018 20:00:17 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id A80AE79EB9; Thu, 8 Feb 2018 20:00:16 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: openssl in base should install c_rehash To: =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= , Jan Bramkamp , FreeBSD-current References: From: Jung-uk Kim Message-ID: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> Date: Thu, 8 Feb 2018 15:00:10 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ezU6ntMFj8HkjXP9CdA9UDDPa7AyOTleQ" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 20:00:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ezU6ntMFj8HkjXP9CdA9UDDPa7AyOTleQ Content-Type: multipart/mixed; boundary="LGLxuCKGmAMuzBD4ZD6rA3L2PVl8DIoE9"; protected-headers="v1" From: Jung-uk Kim To: =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= , Jan Bramkamp , FreeBSD-current Message-ID: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> Subject: Re: openssl in base should install c_rehash References: In-Reply-To: --LGLxuCKGmAMuzBD4ZD6rA3L2PVl8DIoE9 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/08/2018 08:52, Jan Bramkamp wrote: > On 08.02.18 14:24, Ulrich Sp=C3=B6rlein wrote: >> Hey, >> >> c_rehash has somehow disappeared from the base system. We still >> install the >> manpage it seems, but the tool itself is missing. Can we have that bac= k? >> >> >> root@acme:/etc/ssl# locate c_rehash >> ... >> /usr/share/openssl/man/man1/c_rehash.1.gz >> /usr/src/crypto/openssl/doc/apps/c_rehash.pod >> /usr/src/secure/usr.bin/openssl/man/c_rehash.1 >> >> >> The port seems to install it just fine: >> >> root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ >> /usr/ports/security/openssl/pkg-plist:bin/c_rehash >> /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz >> >> It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm >> reading the >> history with git pickaxe right). >=20 > The LibreSSL port lacks a c_rehash script as well. Putting c_rehash bac= k > into base wouldn't solve the problem because it requires Perl 5. Correct. I just removed the manual page to not confuse users. https://svnweb.freebsd.org/changeset/base/329024 Thanks for letting me know! Jung-uk Kim --LGLxuCKGmAMuzBD4ZD6rA3L2PVl8DIoE9-- --ezU6ntMFj8HkjXP9CdA9UDDPa7AyOTleQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlp8rFAACgkQfJ+WJvzb 8UZPZQf+OOD5xtUxML/Yvn+tu0g3sJckl30O8+ctJLBitxpTDS67yD3Xdvw7bKtU sDDSYo5uKWuPewisPwI0JAhMU7V/+rkxZ1NAvh9wpu3DIRZeif1wi9Z0EXsuwG/f BHsFnOGXgxXJtBVIrnbjxnY4wRJ1IeLQHT9f7r3MeXGtLHEIfVZ7PTbkRpk2/TrR 0NiEY8xiowNswivjV6TfPvPoWAJJbOr9PlfdvibugyxjjK0I0HMqLNFUGQiz5pfA E2ubajrwTip4tZqLQr0Wh5gdeHaFBJ1c7WRlsIrxzCxvGhq1454rYnSVIxp3qoL8 RylXJDGp0BOOe0vR6TItGrCd8rkHIQ== =K+SA -----END PGP SIGNATURE----- --ezU6ntMFj8HkjXP9CdA9UDDPa7AyOTleQ-- From owner-freebsd-current@freebsd.org Thu Feb 8 20:15:18 2018 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 9B9A2F00B1C for ; Thu, 8 Feb 2018 20:15:18 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BAB47ADC9; Thu, 8 Feb 2018 20:15:18 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mail-ot0-x230.google.com with SMTP id q12so5535386otg.10; Thu, 08 Feb 2018 12:15:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0Bki2XVnCm1XmjRTiu3twRCMCClg5wcS1VSNXz49t84=; b=qNyg6zcrZtUB4d9+s291qwJQxZWDCeMTXGOwvO583btiaM8+LBcEa73R4p2SjA/mZ7 oLPvn9MsPKewNWBApRqh9neIWWVcLXxCTpmKNdMex7kHnE4kfoKNzKIlh+eX2h5gSd42 y2oJqzF8/SBjMItxnF/+t21mw92ayCY7fplryvyIaYnSEq+TA1/hDuESNdBVkYF2+cz3 6eVeoIAY9J7l9gsaF4T4Uj0jkUUCnJbeSGvgpAWUoYvQm4lBs9R5FstUkaXd5zUIFego er1s8+qKPMpBK4EnHxuvmbEPOHKU7H4mNLj6xRgxCcSUpypMISHtZ2FW5ov1XJ4dN2Le zkpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=0Bki2XVnCm1XmjRTiu3twRCMCClg5wcS1VSNXz49t84=; b=ZgupDJU4jDa9bmOyETfGumn9n5VZWMLNsvn4asu+bVQ0kUqZGvS5A11EYcUpNmSj+k zov0ZU7fmAVvLtm03nw5emcXUYa72JdjrfDXxT2Txk9HPW8c5evBHkzN4aMD0vAA+Jdr AVlSnChp+vaoydXJY5OY1MEEh7S1bkX/0yNQNqfb/U+xjSX6tCWWKqZt+TRr79F7M/Z/ 6lKj53x55NA8oksHwh3s75NVxPqDQhrbLie+dPMvy/zgPypJyfbdr+7FI+SCN86s+UdN jMcR2wgrYQON9/yQERZvEki4owYL9Tr9URtKIUYLV4KIcnkd9+0GVnk1vb1TNkQZgb5u ZiNQ== X-Gm-Message-State: APf1xPBMArE4Ue/y0DZE47GrB08Z173xdsU2PzWILFel1z/tMibAbF6V k8suaN7gxSAWFS9qZvDzsUjb6Yepke94eDMfSBI/9o/w X-Google-Smtp-Source: AH8x226lEx8kOYPD0fGY/QDwIR0GODHWZGU45F/fYDIBlCPOJExk/c1IpDYfWchFjP6t4AeucoXlKHDUGX3jkCfFcwA= X-Received: by 10.157.90.153 with SMTP id w25mr348767oth.36.1518120917310; Thu, 08 Feb 2018 12:15:17 -0800 (PST) MIME-Version: 1.0 Sender: uspoerlein@gmail.com Received: by 10.157.39.3 with HTTP; Thu, 8 Feb 2018 12:15:16 -0800 (PST) In-Reply-To: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> References: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Thu, 8 Feb 2018 21:15:16 +0100 X-Google-Sender-Auth: SUkRU9yZkuoufzYyf-ga67-6zYo Message-ID: Subject: Re: openssl in base should install c_rehash To: Jung-uk Kim Cc: Jan Bramkamp , FreeBSD-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 20:15:18 -0000 2018-02-08 21:00 GMT+01:00 Jung-uk Kim : > On 02/08/2018 08:52, Jan Bramkamp wrote: > > On 08.02.18 14:24, Ulrich Sp=C3=B6rlein wrote: > >> Hey, > >> > >> c_rehash has somehow disappeared from the base system. We still > >> install the > >> manpage it seems, but the tool itself is missing. Can we have that bac= k? > >> > >> > >> root@acme:/etc/ssl# locate c_rehash > >> ... > >> /usr/share/openssl/man/man1/c_rehash.1.gz > >> /usr/src/crypto/openssl/doc/apps/c_rehash.pod > >> /usr/src/secure/usr.bin/openssl/man/c_rehash.1 > >> > >> > >> The port seems to install it just fine: > >> > >> root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ > >> /usr/ports/security/openssl/pkg-plist:bin/c_rehash > >> /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz > >> > >> It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm > >> reading the > >> history with git pickaxe right). > > > > The LibreSSL port lacks a c_rehash script as well. Putting c_rehash bac= k > > into base wouldn't solve the problem because it requires Perl 5. > > Correct. I just removed the manual page to not confuse users. > > https://svnweb.freebsd.org/changeset/base/329024 > > Thanks for letting me know! > > Jung-uk Kim > > I would rather that c_rehash is brought back. I can install perl just fine (or have it anyway installed), that's not the case with openssl from ports, as that will mess up many things. Guess I'll download my own version ... :( Uli From owner-freebsd-current@freebsd.org Thu Feb 8 20:21:43 2018 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 D0665F0141F for ; Thu, 8 Feb 2018 20:21:42 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CA0B7B47C; Thu, 8 Feb 2018 20:21:42 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io0-x231.google.com with SMTP id b198so7161616iof.6; Thu, 08 Feb 2018 12:21:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=cc:message-id:from:to:in-reply-to:content-transfer-encoding :mime-version:subject:date:references; bh=wIuk3QfUnJaE28I/dCX6NM5+x19bQFMdhQ5QTrSJtqA=; b=cK78FY1tnCPiiumz0j+BorGLu4DiQnZaPbICWBNCWjPShA3JWqIziNAhmJCViT1oHK VbTmeXNC0ixuy5l7C39Scs6zUSGGnwTAEKpVOjPyvnnv7RDcKSMgBsGDgvCVFB0Dq3Nh qL6OjIYCSZ0etp2BY2294NWetJH/lVKKWJdWlLTBdBf4xIJkKF1x6LfUbf9M877Nul/C bYtE0CIEJNy1/SslJ1WJcpH6EvCASuBouCy8LcgUeAaUwsWVJ3t33cdGj3dmWUsyPdZx Yot+IE5SHomV0psHszy1oOyeYVrIeLZ1G5OdhSplbeI83URpavSHGIWG9D+BUHBcfQia rViA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:cc:message-id:from:to:in-reply-to :content-transfer-encoding:mime-version:subject:date:references; bh=wIuk3QfUnJaE28I/dCX6NM5+x19bQFMdhQ5QTrSJtqA=; b=SVv/9U1DtlaoJH2+JfPCDf+hU/ed7R3VPbIw6QCH/iEEYhGca5pcIMjY57UeQ9djF7 ZzzOdH7OXlYG1UL6AyCNn4s9dVGIkP4BwGI7cR9hkmd80XSIFc7mJl8iN1yD4sQmMyRp ii6qwMj/fVcGUlKz7835bo0fGFh4hEvAniuMm689T3CcaVApE1zW8OpSf4Nx6lKqZpih plwGWr58RTUGHFJ487/nLSey4b/5AentYh4aOssM6L7NAhVFiVbVa+hDBVQr8QVtxJ1q 4mZFA+kUDhcSmtDM0NdI0KBnGyPLxP4rM5t2ELtYPQM6mO48ZZYMz2Q7pNlNyRfhYYb4 5U7g== X-Gm-Message-State: APf1xPAc8xNWcx2D/Oj8sJy3KA9Y7+2z+A3lT7ajwR17xNxJ5urDHELn ccPPc7+G/vUAQ73uuWpniOE5Vw== X-Google-Smtp-Source: AH8x2259caQUtortTQUzHIqDghTRaake/UfJoUqaTNtMYj5nHD36McF6VAPXLztCdKf1SBOrzP+ofw== X-Received: by 10.107.36.195 with SMTP id k186mr340084iok.131.1518121301267; Thu, 08 Feb 2018 12:21:41 -0800 (PST) Received: from Triad.knownspace (173-25-245-129.client.mchsi.com. [173.25.245.129]) by smtp.gmail.com with ESMTPSA id 17sm540122ioc.33.2018.02.08.12.21.39 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 08 Feb 2018 12:21:40 -0800 (PST) Cc: Jung-uk Kim , Jan Bramkamp , FreeBSD-current Message-Id: <0E1EC83C-BFFD-48C8-8CF2-0C9A56F88988@gmail.com> From: Justin Hibbits To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: openssl in base should install c_rehash Date: Thu, 8 Feb 2018 14:21:38 -0600 References: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 20:21:43 -0000 On Feb 8, 2018, at 2:15 PM, Ulrich Sp=F6rlein wrote: > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim : > >> On 02/08/2018 08:52, Jan Bramkamp wrote: >>> On 08.02.18 14:24, Ulrich Sp=F6rlein wrote: >>>> Hey, >>>> >>>> c_rehash has somehow disappeared from the base system. We still >>>> install the >>>> manpage it seems, but the tool itself is missing. Can we have =20 >>>> that back? >>>> >>>> >>>> root@acme:/etc/ssl# locate c_rehash >>>> ... >>>> /usr/share/openssl/man/man1/c_rehash.1.gz >>>> /usr/src/crypto/openssl/doc/apps/c_rehash.pod >>>> /usr/src/secure/usr.bin/openssl/man/c_rehash.1 >>>> >>>> >>>> The port seems to install it just fine: >>>> >>>> root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ >>>> /usr/ports/security/openssl/pkg-plist:bin/c_rehash >>>> /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz >>>> >>>> It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm >>>> reading the >>>> history with git pickaxe right). >>> >>> The LibreSSL port lacks a c_rehash script as well. Putting =20 >>> c_rehash back >>> into base wouldn't solve the problem because it requires Perl 5. >> >> Correct. I just removed the manual page to not confuse users. >> >> https://svnweb.freebsd.org/changeset/base/329024 >> >> Thanks for letting me know! >> >> Jung-uk Kim >> >> > I would rather that c_rehash is brought back. I can install perl =20 > just fine > (or have it anyway installed), that's not the case with openssl from =20= > ports, > as that will mess up many things. > > Guess I'll download my own version ... :( > > Uli Would this be something useful to add to src/tools? Or create an =20 explicit port for it? Or just keep it handy yourself? - Justin From owner-freebsd-current@freebsd.org Thu Feb 8 20:26:24 2018 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 D3605F01A4A for ; Thu, 8 Feb 2018 20:26:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 617097BAA9 for ; Thu, 8 Feb 2018 20:26:24 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 251777ee-0d0e-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 251777ee-0d0e-11e8-bb8e-b35b57339d60; Thu, 08 Feb 2018 20:25:04 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w18KPDnh024904; Thu, 8 Feb 2018 13:25:13 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518121513.32585.101.camel@freebsd.org> Subject: Re: openssl in base should install c_rehash From: Ian Lepore To: Ulrich =?ISO-8859-1?Q?Sp=F6rlein?= , Jung-uk Kim Cc: Jan Bramkamp , FreeBSD-current Date: Thu, 08 Feb 2018 13:25:13 -0700 In-Reply-To: References: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 20:26:25 -0000 On Thu, 2018-02-08 at 21:15 +0100, Ulrich Spörlein wrote: > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim : > > > > > On 02/08/2018 08:52, Jan Bramkamp wrote: > > > > > > On 08.02.18 14:24, Ulrich Spörlein wrote: > > > > > > > > Hey, > > > > > > > > c_rehash has somehow disappeared from the base system. We still > > > > install the > > > > manpage it seems, but the tool itself is missing. Can we have > > > > that back? > > > > > > > > > > > > root@acme:/etc/ssl# locate c_rehash > > > > ... > > > > /usr/share/openssl/man/man1/c_rehash.1.gz > > > > /usr/src/crypto/openssl/doc/apps/c_rehash.pod > > > > /usr/src/secure/usr.bin/openssl/man/c_rehash.1 > > > > > > > > > > > > The port seems to install it just fine: > > > > > > > > root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ > > > > /usr/ports/security/openssl/pkg-plist:bin/c_rehash > > > > /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz > > > > > > > > It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm > > > > reading the > > > > history with git pickaxe right). > > > The LibreSSL port lacks a c_rehash script as well. Putting > > > c_rehash back > > > into base wouldn't solve the problem because it requires Perl 5. > > Correct.  I just removed the manual page to not confuse users. > > > > https://svnweb.freebsd.org/changeset/base/329024 > > > > Thanks for letting me know! > > > > Jung-uk Kim > > > > > I would rather that c_rehash is brought back. I can install perl just > fine > (or have it anyway installed), that's not the case with openssl from > ports, > as that will mess up many things. > > Guess I'll download my own version ... :( > > Uli Maybe we should just replace ours in base with a non-perl version, something like this one? https://opensource.apple.com/source/OpenSSL/OpenSSL-5/openssl/tools/c_rehash.in.auto.html -- Ian From owner-freebsd-current@freebsd.org Thu Feb 8 20:37:51 2018 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 03912F02943 for ; Thu, 8 Feb 2018 20:37:51 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 9FAF87C529; Thu, 8 Feb 2018 20:37:50 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: openssl in base should install c_rehash To: =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= Cc: Jan Bramkamp , FreeBSD-current References: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> From: Jung-uk Kim Message-ID: Date: Thu, 8 Feb 2018 15:37:46 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="W29JvWUCEFahBCJMJyoRnBktHcevo9FKD" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 20:37:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --W29JvWUCEFahBCJMJyoRnBktHcevo9FKD Content-Type: multipart/mixed; boundary="HTA3SRaR8yNVemDPKL9P0wKuyKUUaGBWx"; protected-headers="v1" From: Jung-uk Kim To: =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= Cc: Jan Bramkamp , FreeBSD-current Message-ID: Subject: Re: openssl in base should install c_rehash References: <277d8257-019b-714b-8014-7c741e427547@FreeBSD.org> In-Reply-To: --HTA3SRaR8yNVemDPKL9P0wKuyKUUaGBWx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/08/2018 15:15, Ulrich Sp=C3=B6rlein wrote: >=20 > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim >: >=20 > On 02/08/2018 08:52, Jan Bramkamp wrote: > > On 08.02.18 14:24, Ulrich Sp=C3=B6rlein wrote: > >> Hey, > >> > >> c_rehash has somehow disappeared from the base system. We still > >> install the > >> manpage it seems, but the tool itself is missing. Can we have th= at back? > >> > >> > >> root@acme:/etc/ssl# locate c_rehash > >> ... > >> /usr/share/openssl/man/man1/c_rehash.1.gz > >> /usr/src/crypto/openssl/doc/apps/c_rehash.pod > >> /usr/src/secure/usr.bin/openssl/man/c_rehash.1 > >> > >> > >> The port seems to install it just fine: > >> > >> root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ > >> /usr/ports/security/openssl/pkg-plist:bin/c_rehash > >> /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz > >> > >> It looks like the merge of OpenSSL 1.0.1c got rid of it (if I'm > >> reading the > >> history with git pickaxe right). > > > > The LibreSSL port lacks a c_rehash script as well. Putting c_reha= sh back > > into base wouldn't solve the problem because it requires Perl 5. >=20 > Correct.=C2=A0 I just removed the manual page to not confuse users.= >=20 > https://svnweb.freebsd.org/changeset/base/329024 > >=20 > Thanks for letting me know! >=20 > Jung-uk Kim >=20 >=20 > I would rather that c_rehash is brought back. I can install perl just > fine (or have it anyway installed), that's not the case with openssl > from ports, as that will mess up many things. Although c_rehash was available from src/crypto/openssl/tools, we have never installed it in the base, AFAIK. Actually, it does not use proper perl binary (i.e., /usr/bin/perl vs. /usr/local/bin/perl) and certs directory (i.e., /usr/local/ssl/certs vs. /etc/ssl/certs). https://svnweb.freebsd.org/base/vendor-crypto/openssl/dist-0.9.8/tools/c_= rehash?revision=3D247942&view=3Dco Jung-uk Kim > Guess I'll download my own version ... :( --HTA3SRaR8yNVemDPKL9P0wKuyKUUaGBWx-- --W29JvWUCEFahBCJMJyoRnBktHcevo9FKD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlp8tRoACgkQfJ+WJvzb 8UaLRwf/dGEnBycnFf6QzWhWZaCVcyhXpabWarbmv7GtMyXjiFieiyQflcGc8Gvc bnk+8+9y/SfrBgMysxvrHhUg1029lL/2fntyKA1p4EqAYs/mW8EUSePQD7rDUlga RCkcw2zL+ikwmm+AtiwKV4dmU/ZwImL9CRL0vLykO07DX3XoP0I+5MwtzqaRN3re eFggr9t2lVwd9b1Il9ARA3W9pdTG0vUUxU47fJIZZ4DMW41hChmOsDlVDtMtsw8d ds0qvbSjUm9tiooI5/Vw/Esc4C00ENuNgAdE8uIyI5+SjJkQopIIYKEbVvu5FycH r/hMpqJLAhD78kbxBquj1DrZgNyxhw== =F6in -----END PGP SIGNATURE----- --W29JvWUCEFahBCJMJyoRnBktHcevo9FKD-- From owner-freebsd-current@freebsd.org Thu Feb 8 22:30:27 2018 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 DB625F0AE00 for ; Thu, 8 Feb 2018 22:30:27 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60084822AD for ; Thu, 8 Feb 2018 22:30:27 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w18MV9W0075028 for ; Thu, 8 Feb 2018 14:31:15 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 In-Reply-To: <1518121513.32585.101.camel@freebsd.org> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD-current" Subject: Re: openssl in base should install c_rehash Date: Thu, 08 Feb 2018 14:31:15 -0800 Message-Id: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 22:30:28 -0000 On Thu, 08 Feb 2018 13:25:13 -0700 "Ian Lepore" said > On Thu, 2018-02-08 at 21:15 +0100, Ulrich Sp=C3=B6rlein wrote: > > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim : > >=20 > > >=20 > > > On 02/08/2018 08:52, Jan Bramkamp wrote: > > > >=20 > > > > On 08=2E02=2E18 14:24, Ulrich Sp=C3=B6rlein wrote: > > > > >=20 > > > > > Hey, > > > > >=20 > > > > > c_rehash has somehow disappeared from the base system=2E We still > > > > > install the > > > > > manpage it seems, but the tool itself is missing=2E Can we have > > > > > that back? > > > > >=20 > > > > >=20 > > > > > root@acme:/etc/ssl# locate c_rehash > > > > > =2E=2E=2E > > > > > /usr/share/openssl/man/man1/c_rehash=2E1=2Egz > > > > > /usr/src/crypto/openssl/doc/apps/c_rehash=2Epod > > > > > /usr/src/secure/usr=2Ebin/openssl/man/c_rehash=2E1 > > > > >=20 > > > > >=20 > > > > > The port seems to install it just fine: > > > > >=20 > > > > > root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ > > > > > /usr/ports/security/openssl/pkg-plist:bin/c_rehash > > > > > /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash=2E1=2Egz > > > > >=20 > > > > > It looks like the merge of OpenSSL 1=2E0=2E1c got rid of it (if I'm > > > > > reading the > > > > > history with git pickaxe right)=2E > > > > The LibreSSL port lacks a c_rehash script as well=2E Putting > > > > c_rehash back > > > > into base wouldn't solve the problem because it requires Perl 5=2E > > > Correct=2E=C2=A0=C2=A0I just removed the manual page to not confuse use= rs=2E > > >=20 > > > https://svnweb=2Efreebsd=2Eorg/changeset/base/329024 > > >=20 > > > Thanks for letting me know! > > >=20 > > > Jung-uk Kim > > >=20 > > >=20 > > I would rather that c_rehash is brought back=2E I can install perl just > > fine > > (or have it anyway installed), that's not the case with openssl from > > ports, > > as that will mess up many things=2E > >=20 > > Guess I'll download my own version =2E=2E=2E :( > >=20 > > Uli >=20 >=20 > Maybe we should just replace ours in base with a non-perl version, > something like this one? >=20 > https://opensource=2Eapple=2Ecom/source/OpenSSL/OpenSSL-5/openssl/tools/c_reh= ash=2Ein=2Eauto=2Ehtml >=20 > -- Ian Excellent link, Ian=2E Thanks! Couldn't this be in $base? I'd like to vote yes=2E :-) --Chris >=20 > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= " From owner-freebsd-current@freebsd.org Thu Feb 8 22:47:36 2018 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 C2C30F0C2BE for ; Thu, 8 Feb 2018 22:47:36 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8CD83544; Thu, 8 Feb 2018 22:47:36 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: openssl in base should install c_rehash To: bsd-lists@BSDforge.com, FreeBSD-current References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> From: Jung-uk Kim Message-ID: <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> Date: Thu, 8 Feb 2018 17:47:32 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FKvY31DcefibxzhQF6nwYtB3zTWpBETHz" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 22:47:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --FKvY31DcefibxzhQF6nwYtB3zTWpBETHz Content-Type: multipart/mixed; boundary="0IKo2E7Tn8ERHPhwKLHkxCkWuhOvZwzNg"; protected-headers="v1" From: Jung-uk Kim To: bsd-lists@BSDforge.com, FreeBSD-current Message-ID: <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> Subject: Re: openssl in base should install c_rehash References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> In-Reply-To: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> --0IKo2E7Tn8ERHPhwKLHkxCkWuhOvZwzNg Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/08/2018 17:31, Chris H wrote: > On Thu, 08 Feb 2018 13:25:13 -0700 "Ian Lepore" said >> On Thu, 2018-02-08 at 21:15 +0100, Ulrich Sp=C3=B6rlein wrote: >> > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim : >> > > > > > On 02/08/2018 08:52, Jan Bramkamp wrote: >> > > > > > > On 08.02.18 14:24, Ulrich Sp=C3=B6rlein wrote: >> > > > > > > > > Hey, >> > > > > > > > > c_rehash has somehow disappeared from the base system.= >> We still >> > > > > install the >> > > > > manpage it seems, but the tool itself is missing. Can we have >> > > > > that back? >> > > > > > > > > > > > > root@acme:/etc/ssl# locate c_rehash >> > > > > ... >> > > > > /usr/share/openssl/man/man1/c_rehash.1.gz >> > > > > /usr/src/crypto/openssl/doc/apps/c_rehash.pod >> > > > > /usr/src/secure/usr.bin/openssl/man/c_rehash.1 >> > > > > > > > > > > > > The port seems to install it just fine: >> > > > > > > > > root@acme:/etc/ssl# grep -r c_rehash /usr/ports/ >> > > > > /usr/ports/security/openssl/pkg-plist:bin/c_rehash >> > > > > /usr/ports/security/openssl/pkg-plist:man/man1/c_rehash.1.gz >> > > > > > > > > It looks like the merge of OpenSSL 1.0.1c got rid of >> it (if I'm >> > > > > reading the >> > > > > history with git pickaxe right). >> > > > The LibreSSL port lacks a c_rehash script as well. Putting >> > > > c_rehash back >> > > > into base wouldn't solve the problem because it requires Perl 5.= >> > > Correct.=C2=A0=C2=A0I just removed the manual page to not confuse = users. >> > > > > https://svnweb.freebsd.org/changeset/base/329024 >> > > > > Thanks for letting me know! >> > > > > Jung-uk Kim >> > > > > > I would rather that c_rehash is brought back. I can install >> perl just >> > fine >> > (or have it anyway installed), that's not the case with openssl from= >> > ports, >> > as that will mess up many things. >> > > Guess I'll download my own version ... :( >> > > Uli >> >> >> Maybe we should just replace ours in base with a non-perl version, >> something like this one? >> >> https://opensource.apple.com/source/OpenSSL/OpenSSL-5/openssl/tools/c_= rehash.in.auto.html >> >> >> -- Ian > Excellent link, Ian. Thanks! > Couldn't this be in $base? I'd like to vote yes. :-) =46rom OpenSSL 1.1.0, openssl(1) added "rehash" command. https://www.openssl.org/docs/man1.1.0/apps/rehash.html I don't think we need yet another implementation in the base. Jung-uk Kim --0IKo2E7Tn8ERHPhwKLHkxCkWuhOvZwzNg-- --FKvY31DcefibxzhQF6nwYtB3zTWpBETHz Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlp804QACgkQfJ+WJvzb 8UYHcQf+Jbi9Dl9aTCdV+MIq0+AdVbeDSujNp3oqRZPL1KIlaEzi7kz5QXHbb2Ue Rksro0+lxJRoHW0HznE2PwcyY78Ljse+cz++kmfDpGfPgU5ROzZSkgs1FZPwdQt+ 1+UKH03lSEI68JSNo52yzlzkpuSAVV4m34IannRTlynLvFm+JawPLJHflhEolQrN 8n0/hBUoooQJ/zc0hHKJrHLhgz5UHBFLdHZ+UU9EpkhUZVFaYZNwS/zjYsUQTa82 0W9DD3hNULVrDth3zVytFdPoxakEKiT0t6xQDOO3O3ZBx9iPkq3LMzdoYa1mbAHK d/L1nvdZw8x6j9qLeMk1KeVpeUi0tg== =0OIs -----END PGP SIGNATURE----- --FKvY31DcefibxzhQF6nwYtB3zTWpBETHz-- From owner-freebsd-current@freebsd.org Thu Feb 8 23:52:38 2018 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 79D4BF10C50 for ; Thu, 8 Feb 2018 23:52:38 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 01AE5861F4 for ; Thu, 8 Feb 2018 23:52:37 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: eff0fd58-0d2a-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id eff0fd58-0d2a-11e8-b951-f99fef315fd9; Thu, 08 Feb 2018 23:51:10 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w18NpR0g025301; Thu, 8 Feb 2018 16:51:27 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518133887.32585.110.camel@freebsd.org> Subject: Re: openssl in base should install c_rehash From: Ian Lepore To: Jung-uk Kim , bsd-lists@BSDforge.com, FreeBSD-current Date: Thu, 08 Feb 2018 16:51:27 -0700 In-Reply-To: <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 08 Feb 2018 23:52:38 -0000 On Thu, 2018-02-08 at 17:47 -0500, Jung-uk Kim wrote: > On 02/08/2018 17:31, Chris H wrote: > > > > [...] > > Couldn't this be in $base? I'd like to vote yes. :-) > From OpenSSL 1.1.0, openssl(1) added "rehash" command. > > https://www.openssl.org/docs/man1.1.0/apps/rehash.html > > I don't think we need yet another implementation in the base. > > Jung-uk Kim > But on a machine I just set up last weekend using -current I get: ian@th > openssl rehash openssl:Error: 'rehash' is an invalid command. ian@th > openssl version OpenSSL 1.0.2n-freebsd  7 Dec 2017 Are we going to update to 1.1.0 soon?  If not, how does it help that a version we don't use has rehash built in? -- Ian From owner-freebsd-current@freebsd.org Fri Feb 9 00:36:00 2018 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 49478F13B1C for ; Fri, 9 Feb 2018 00:36:00 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id E869187B8B; Fri, 9 Feb 2018 00:35:59 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: openssl in base should install c_rehash To: Ian Lepore , bsd-lists@BSDforge.com, FreeBSD-current References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> <1518133887.32585.110.camel@freebsd.org> From: Jung-uk Kim Message-ID: <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> Date: Thu, 8 Feb 2018 19:35:55 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1518133887.32585.110.camel@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="m3RUgdgybGv8OHDLqLYQ9lmjv8AszSMF5" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 00:36:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --m3RUgdgybGv8OHDLqLYQ9lmjv8AszSMF5 Content-Type: multipart/mixed; boundary="2R7oQMRPn3SajJ4i3hBtxsSseEGAscT2w"; protected-headers="v1" From: Jung-uk Kim To: Ian Lepore , bsd-lists@BSDforge.com, FreeBSD-current Message-ID: <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> Subject: Re: openssl in base should install c_rehash References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> <1518133887.32585.110.camel@freebsd.org> In-Reply-To: <1518133887.32585.110.camel@freebsd.org> --2R7oQMRPn3SajJ4i3hBtxsSseEGAscT2w Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/08/2018 18:51, Ian Lepore wrote: > On Thu, 2018-02-08 at 17:47 -0500, Jung-uk Kim wrote: >> On 02/08/2018 17:31, Chris H wrote: >>> >>> [...] >>> Couldn't this be in $base? I'd like to vote yes. :-) >> From OpenSSL 1.1.0, openssl(1) added "rehash" command. >> >> https://www.openssl.org/docs/man1.1.0/apps/rehash.html >> >> I don't think we need yet another implementation in the base. >=20 > But on a machine I just set up last weekend using -current I get: >=20 > ian@th > openssl rehash > openssl:Error: 'rehash' is an invalid command. > ian@th > openssl version > OpenSSL 1.0.2n-freebsd=C2=A0=C2=A07 Dec 2017 >=20 > Are we going to update to 1.1.0 soon? When I find some free time. I don't know how "soon", however. > If not, how does it help that a version we don't use has rehash > built in? We will have the feature when we import OpenSSL 1.1.0. Knowing that it is obsoleted by the upstream, I don't want to add an equivalent script in the base. If it is really necessary, you can always install the c_rehash script (security/openssl), openssl with rehash command (security/openssl-devel), openssl with certhash command (security/libressl), etc. from the ports tree. BTW, we never had it in the base and it was removed from head src tree more than 5 years ago. Why is it so important now? :-( Jung-uk Kim --2R7oQMRPn3SajJ4i3hBtxsSseEGAscT2w-- --m3RUgdgybGv8OHDLqLYQ9lmjv8AszSMF5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlp87OsACgkQfJ+WJvzb 8Uan/Af/Rd7ZFyyW2A1xfnwHPsYI5Yp0szG9evLWdwYAlukYbccdpci91H7z5xmp 7gH9IESX7h03uMDF5OJ+je1Wh7gXH5xijtQv5W94JMWqDo9iKN4KUGMHC10/WpUh VOEAC5CWESmnpr390VFJ63NjzDvIzpy8jtXzSV0QyX7OM04D2CYOgwFyR5Og7C/A QEBk2fIlsNRntp+aS47gObV+nD0zWo2NzylnecjdsLIUMYXMwT07hRaSlYJU8Oiq DLMJevHvK1KZo4wBy3LGTo77T5DaRRTka4GezYRyD1KztFh+PkPu+Re6+EGEF4LN XfnMzYLo1/OVUlvq5/5j9g8/QVqNkw== =kNHF -----END PGP SIGNATURE----- --m3RUgdgybGv8OHDLqLYQ9lmjv8AszSMF5-- From owner-freebsd-current@freebsd.org Fri Feb 9 00:43:33 2018 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 84A5FF146BC for ; Fri, 9 Feb 2018 00:43:33 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 0726668407 for ; Fri, 9 Feb 2018 00:43:32 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 3531c64d-0d32-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 3531c64d-0d32-11e8-b951-f99fef315fd9; Fri, 09 Feb 2018 00:43:13 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w190hUe0025378; Thu, 8 Feb 2018 17:43:30 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518137010.32585.127.camel@freebsd.org> Subject: Re: openssl in base should install c_rehash From: Ian Lepore To: Jung-uk Kim , bsd-lists@BSDforge.com, FreeBSD-current Date: Thu, 08 Feb 2018 17:43:30 -0700 In-Reply-To: <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> <1518133887.32585.110.camel@freebsd.org> <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 00:43:33 -0000 On Thu, 2018-02-08 at 19:35 -0500, Jung-uk Kim wrote: > On 02/08/2018 18:51, Ian Lepore wrote: > > > > On Thu, 2018-02-08 at 17:47 -0500, Jung-uk Kim wrote: > > > > > > On 02/08/2018 17:31, Chris H wrote: > > > > > > > > > > > > [...] > > > > Couldn't this be in $base? I'd like to vote yes. :-) > > > From OpenSSL 1.1.0, openssl(1) added "rehash" command. > > > > > > https://www.openssl.org/docs/man1.1.0/apps/rehash.html > > > > > > I don't think we need yet another implementation in the base. > > But on a machine I just set up last weekend using -current I get: > > > >     ian@th > openssl rehash > >     openssl:Error: 'rehash' is an invalid command. > >     ian@th > openssl version > >     OpenSSL 1.0.2n-freebsd  7 Dec 2017 > > > > Are we going to update to 1.1.0 soon? > When I find some free time.  I don't know how "soon", however. > > > > > If not, how does it help that a version we don't use has rehash > > built in? > We will have the feature when we import OpenSSL 1.1.0.  Knowing that it > is obsoleted by the upstream, I don't want to add an equivalent script > in the base. > > If it is really necessary, you can always install the c_rehash script > (security/openssl), openssl with rehash command > (security/openssl-devel), openssl with certhash command > (security/libressl), etc. from the ports tree. > > BTW, we never had it in the base and it was removed from head src tree > more than 5 years ago.  Why is it so important now? :-( When looking for info (because of this thread) I noticed that lots of how-to writeups on the web tell you to use the c_rehash command, so if we don't supply one that's bad (or if we supply an alternate-named thing we should document that somehow). If we're just a bit behind but we're going to catch up eventually, then that's good enough I think.  It's not clear if openssl 1.1.0 installs a link or wrapper for c_rehash or not.  That manpage seems to imply that "openssl rehash" and "c_rehash" are equivelent. -- Ian From owner-freebsd-current@freebsd.org Fri Feb 9 01:02:01 2018 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 6A1E9F15AA9 for ; Fri, 9 Feb 2018 01:02:01 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 0C13D690C4; Fri, 9 Feb 2018 01:02:01 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: openssl in base should install c_rehash To: Ian Lepore , bsd-lists@BSDforge.com, FreeBSD-current References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> <1518133887.32585.110.camel@freebsd.org> <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> <1518137010.32585.127.camel@freebsd.org> From: Jung-uk Kim Message-ID: <105ac442-a79b-42b2-f78d-4c4d80e08bc4@FreeBSD.org> Date: Thu, 8 Feb 2018 20:01:56 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1518137010.32585.127.camel@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="A1A36sJvNzwCrat3Yiu2B0EDOqgLm9ftU" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 01:02:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --A1A36sJvNzwCrat3Yiu2B0EDOqgLm9ftU Content-Type: multipart/mixed; boundary="gavM52q2UWDlG48xbabcIxWS4OPEDn5su"; protected-headers="v1" From: Jung-uk Kim To: Ian Lepore , bsd-lists@BSDforge.com, FreeBSD-current Message-ID: <105ac442-a79b-42b2-f78d-4c4d80e08bc4@FreeBSD.org> Subject: Re: openssl in base should install c_rehash References: <2647c9a31e203a8891637aaa89462afe@udns.ultimatedns.net> <9306ff93-e606-c958-655b-1e12ddf9c579@FreeBSD.org> <1518133887.32585.110.camel@freebsd.org> <250d888c-2c9b-553d-7d19-9dc03cd94713@FreeBSD.org> <1518137010.32585.127.camel@freebsd.org> In-Reply-To: <1518137010.32585.127.camel@freebsd.org> --gavM52q2UWDlG48xbabcIxWS4OPEDn5su Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/08/2018 19:43, Ian Lepore wrote: > It's not clear if openssl 1.1.0 installs a link or wrapper for c_rehash= > or not. =C2=A0That manpage seems to imply that "openssl rehash" and > "c_rehash" are equivelent. "openssl rehash" is not a wrapper for "c_rehash". This command is available for all Unix-like platforms. https://github.com/openssl/openssl/blob/master/apps/rehash.c "c_rehash" is not a wrapper for "openssl rehash", either. For Unix-like platforms, it is only provided as a backup. https://github.com/openssl/openssl/blob/master/tools/c_rehash.in I guess they just forgot to add "functionally" in front of "equivalent". = ;-) Jung-uk Kim --gavM52q2UWDlG48xbabcIxWS4OPEDn5su-- --A1A36sJvNzwCrat3Yiu2B0EDOqgLm9ftU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlp88wQACgkQfJ+WJvzb 8UbKFwf/d30wiic1+3jVj8GtS1uwXfFh3XURQElsEqKxS3c8K6S9OQifj5b32UlP jGZyeZgQoOzQ/JxC6zJts3nQVVo6Mmb+9dmpRmXACP97Z+cnNIZxKc8j9N+p7cCY XPsRe/0n8bz9/lDOxFQ8AGrblttudtBgd72v6R3BgpXl9xJUaDzAzNOl72WnWpBv lt+KbzAsOGfKLxwUSN7rKFFrX5SqnakQFnbzmtD1JdNJDvyv5fiPWnjfO/IA167Z djw6hZ/IZdGf3Uj+2L9jTTcRJdy7TOGnZk/FiyKynZcvmSvTQ9xdXb7hdbNneEP8 URUd7VlTbtPEZTpj9kw68V/ZNAtMSg== =xl0Y -----END PGP SIGNATURE----- --A1A36sJvNzwCrat3Yiu2B0EDOqgLm9ftU-- From owner-freebsd-current@freebsd.org Fri Feb 9 16:23:16 2018 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 E6877F10215 for ; Fri, 9 Feb 2018 16:23:15 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1E26B7C4 for ; Fri, 9 Feb 2018 16:23:15 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.181.254.98]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LwJRe-1elfhS0bpG-017zay; Fri, 09 Feb 2018 17:23:08 +0100 Date: Fri, 9 Feb 2018 17:22:32 +0100 From: "O. Hartmann" To: "O. Hartmann" Cc: freebsd-jails@freebsd.org, freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/jHX=/o7OQav.vD032FciI5b"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:4G0hdEl1rGhUtwDT5+umWVXmmI2+HtNMylT2HwrjoEU4AF1HWAg 5xlQtQVyJzgZnPT6dOtqB7EKu+fl+M8nhGO+sduKsu0PJQ1d0NIG91IFQ9q9FdrAjjBg5yl 5s2fQi3HbudUWli/kKOj32/cEg7W1SKVfbEe/KSXaNlB4R7nRbxStC0/Uuqs7q7MqHk6K2A t1V68KFw7YWR0nhN+pVUw== X-UI-Out-Filterresults: notjunk:1;V01:K0:RIaHtrpECP4=:8oV7SefvNM0kso+u/ZxlXw 90tsZPUGTqwPvsYLgLSKGqWU6B6hPqPsivgyoj3HtN1kcoJGDoRMYhL9DiaTCc/UXnfKfz3dw 7Kaj5CwrQJKTNtT3BB7+6F545WnIdh8mhBT1P5FJR0CQjU8kc7ZAPO3AC76dXJMl0Vh01XrPW QG0mXkjqBNJf+RLzksnL6J+c+xgO1g+FBED3HwKhamL09Hk3YpwurS+iOErjUHSSvm/nmE0CE RSQyEEOPi5ZC7XPWMsPrkvK4EivIlRQeSTHdLUOvkJtGUIEdZ34ERjr1q4o+pgpFFla6KaJYi 5gz+iQelPOYVnk0gdcFz2s1xWudP/fhsqDxOQs+PQXQOnXCimtP3Je3E5573tuSrVg346lIM0 Suu1+BsvNEBK7JNGjmh0/1aTGPwLSzZ90u+jIq5m6IeNKzxlEfeHSgcQM+txXurj7FqqyRX6s Bml62VVakl5IfKedsHdSPLvXwuIMi+ulfj7N5c4WPGTJReX08JpsUq9GrXGprvhrqIbOb+oPJ PwIVJl1RrRUE5MS0jR8WfsOSs7m924AZ8gm2IQ45TrbyUb6LnpvCkFRRJG/Qwji1a+kAUdqJI lD1Sjkb12ISN8RGEUhjAzsNu+6ZfRcgXgk2z2PcAak1+MwyYbcOgqA16CeQQAJ2QMxQBSca91 xIALTpVgveXVgKhs6o/KoiKyDqJKYfKlVGOffhaEyhSNZjxq6t+yK59vhNT3I1oJ4m9BidmOu iTGScrNmq6gZM+DGu6cpG3S+QKb5s4z+cvy8ISFyIuQnwqS5XHz0o26legmllVkVhCzPc25jE QEdhIDv2LsFOBvgyfgFaIr3yzXqlA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 16:23:16 -0000 --Sig_/jHX=/o7OQav.vD032FciI5b Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 8 Feb 2018 09:31:15 +0100 "O. Hartmann" schrieb: > Hello, >=20 > I fight with the following problem without any kind of success and I need= some > help and/or advice. >=20 > We are running several CURRENT and 11.1-RELENG-p6 boxes. CURRENT is at th= e most > recent version as of today. >=20 > VIMAGE is compiled in into all kernels. > IPFW is compiled into all kernels and is the one and only firewall used. > On CURRENT, the host's ipfw is set to "OPEN" (using the rc.-scripts so fa= r). By > convention, I address the host running the kernel by "host". >=20 > Every jail is created/configured with its own "vnet" cloned network stack > (vnet=3Dnew). >=20 > All hosts do have at least three physical NICs. The host itself is suppos= ed to > be member of the "friendly" network via a dedicated NIC. The two remainin= g NICs > are split into fractions belonging to an "hostile" network on which I'd l= ike to > place exposed jails (for now), and to the "friendly" network, on which al= so > jails will be hosted, but via a dedicated NIC. >=20 > Inbetween those two networks, the host will have a third, intermediate, > network, call it the "service" network. >=20 > The following will be true for ALL jails created, including the host itse= lf: >=20 > net.link.bridge.pfil_member=3D0 > net.link.bridge.pfil_bridge=3D0 > net.link.bridge.pfil_onlyip=3D0 >=20 > First, I clone/create three bridge(4) devices, bridge0 (considered to be = the > "glue" between the "service" jails), bridge1 (considered to be the glue b= etween > the jails on the friednly network side) and bridge2, which is the glue be= tween > the jails on the hostile side. bridge1 has eth1 as a member, which provid= es the > physical access to the friendly network, eth2 is member of bridge2, which > provides access to the hostile network. >=20 > By convention, when creating epair(4), the a-portion belongs to the jail = itself > and is assigned with an IPv6 address. The b-portion of the epair(4) is me= mber > of its bridge according to its realm (friendly, service or hostile networ= k).=20 >=20 > Additionally, there is a special jail, the router, which has three epair(= 4) > devices, the b-portion of the epair is member of the appropriate bridge(4= ) and > this router jail has static routes assigned, pointing to the appropriate > epairXXXa that is suppoesd to be the link into the correct bridge/network= . IPFW > is set to open on this jail (for now). On this special > jail it is set: net.inet.ip.forwarding=3D1. >=20 > I hope, the topology is clear so far. All epairs or epair endpoints as we= ll as > the bridges are UP! Double checked this. >=20 > Jails on bridge0 (service net) have IPs in the range 10.10.0.0/24, the > b-portion of the routing jail's epair is member of bridge0, as described = above, > and the a-portion of the epair has IP 10.10.0.1. Default route on each je= ail > on bridge0 is set to 10.10.0.1 accordingly. >=20 > Consider a similar setup on the other jails on the friendly and hostile > network, except the fact that their bridges do have a physical NIC to whi= ch > they may have access to a real network. >=20 > The setup might not be ideal and/or applicable for the purpose of separar= tion > of networks virtually, but that shouldn't be the subject here. More impor= tant > is that I assume that I haven't understood some essentials, because the s= etup > doens't work as expected. Furthermore, it behaves on FreeBSD 11.1-RELENG-= p6 > sometimes completely unpredictable - but in that special case, I think I = ran > IPFW on the host as "WORKSTATION" and dynamic rules may play an important= role > here. But focussing on the CURRENT box, the host's IPFW is set to OPEN. >=20 > With jexec -l hostA I gain access to host A on the "service" bridge0 and I > want to ping its neighbour, hostB, on the same bridge and in the same net= . It > doesn't work! From the routing jail, I CAN NOT ping any host on bridge0. = The > routing jail has these network settings: >=20 > [... routing jail ...] > lo0: flags=3D8049 metric 0 mtu 16384 > options=3D600003 > inet 127.0.0.1 netmask 0xff000000=20 > groups: lo > [epair to bridge0 - service net]=20 > epair4000a: flags=3D8843 metric 0= mtu 1500 > options=3D8 > ether 02:57:d0:00:07:0a > inet 10.10.0.1 netmask 0xffffff00 broadcast 10.10.0.255=20 > media: Ethernet 10Gbase-T (10Gbase-T ) > status: active > groups: epair > [epair to bridge1, friendly net]=20 > epair4001a: flags=3D8843 metric 0= mtu 1500 > options=3D8 > ether 02:57:d0:00:09:0a > inet 192.168.11.1 netmask 0xffffff00 broadcast 192.168.11.255=20 > media: Ethernet 10Gbase-T (10Gbase-T ) > status: active > groups: epair > [epair to bridge2, hostile net]=20 > epair4002a: flags=3D8843 metric 0= mtu 1500 > options=3D8 > ether 02:57:d0:00:0b:0a > inet 10.10.10.1 netmask 0xfffffc00 broadcast 10.10.10.255=20 > media: Ethernet 10Gbase-T (10Gbase-T ) > status: active > groups: epair=20 >=20 > routing: > netstat -Warn > Routing tables >=20 > Internet: > Destination Gateway Flags Use Mtu Netif E= xpire > 10.10.0.0/24 link#2 U 11 1500 epair4000a > 10.10.0.1 link#2 UHS 4 16384 lo0 > 10.10.10.0/24 link#4 U 210 1500 epair4002a > 10.10.10.1 link#4 UHS 44 16384 lo0 > 127.0.0.1 link#1 UH 0 16384 lo0 > 192.168.11.0/24 link#3 U 9 1500 epair4001a > 192.168.11.1 link#3 UHS 0 16384 lo0 >=20 > Consider a jail hostCC on bridge2 in the hostile network, IP 10.10.10.128= .=20 > I can ping that jail, although it has conceptionally the very same setup = as the > unreachable jails on bridge0! >=20 > It is weird. On bridge0, no jail can be pinged, it looks like the etherne= t is > somehwo down on that bridge. I would expect to ping each host member of t= he > very same bridge! On 11.1-RELENG-p6, there are other weird issues, I was = able > to ping those jails, even ssh to them, but that vanished after several > restarts of the jails system (each bridge, epair is created by jail.conf = and > destroyed after the jails has been deactivated and doing so a considerable > amount brings down the FreeBSD 11.1-RELENG-p6 host verys successfully - it > crashes!). >=20 > So, since VIMAGE is now default in CURRENT's GENERIC, I consider its > functionality at least "predictable", but I fail somehow here. >=20 > Does someone have a deeper insight or realise the mistake I'm celebrating= here? >=20 > Thanks in adavnce, >=20 > Oliver=20 Is this problem to trivial? oh --Sig_/jHX=/o7OQav.vD032FciI5b Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWn3K4wAKCRDS528fyFhY lPY3Af48aP52clF4lWkMfRUKUX46rG/ZhmxdQ3wllMhOEUi8ASG2VHtrt/wSuIRq Xes2dCF8IIVUdsOPRjmde8Z/bCD1Af4mQT+H5pdcnSYeSIWFjWBs1yw9GEwyxurx sqSzggNjdSLWIJTSNyZI6WCdEBO53jfdC0OokRM9i027/T6VZ8s2 =+Vwl -----END PGP SIGNATURE----- --Sig_/jHX=/o7OQav.vD032FciI5b-- From owner-freebsd-current@freebsd.org Fri Feb 9 16:43:24 2018 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 06D93F11AD9 for ; Fri, 9 Feb 2018 16:43:24 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 821466C63D for ; Fri, 9 Feb 2018 16:43:23 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 8266825D37C7; Fri, 9 Feb 2018 16:43:21 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id D55CFD1F8E2; Fri, 9 Feb 2018 16:43:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id ovx63o_HG-66; Fri, 9 Feb 2018 16:43:18 +0000 (UTC) Received: from [10.248.100.198] (fresh-ayiya.sbone.de [IPv6:fde9:577b:c1a9:f001::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 8E926D1F8DB; Fri, 9 Feb 2018 16:43:18 +0000 (UTC) From: "Bjoern A. Zeeb" To: "O. Hartmann" Cc: freebsd-jails@freebsd.org, freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Date: Fri, 09 Feb 2018 16:43:17 +0000 X-Mailer: MailMate (2.0BETAr6103) Message-ID: <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> In-Reply-To: <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 16:43:24 -0000 On 9 Feb 2018, at 16:22, O. Hartmann wrote: > Am Thu, 8 Feb 2018 09:31:15 +0100 > "O. Hartmann" schrieb: > > Is this problem to trivial? I read through it yesterday and found myself in the position that I need a whiteboard or paper and pencil or an ASCII art of your situation. But by the time I made it to the question I was basically lost. Could you massively simplify this and maybe produce the ASCII art? /bz From owner-freebsd-current@freebsd.org Fri Feb 9 17:03:26 2018 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 3F543F13420 for ; Fri, 9 Feb 2018 17:03:26 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A49646D509 for ; Fri, 9 Feb 2018 17:03:25 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id 141so17434221wme.3 for ; Fri, 09 Feb 2018 09:03:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=wuCSqieECaXc/7mA01J8UBPLF9N22sG3IZHrAtRDM3A=; b=kdmrb0ta0jD4+wiVgIDTzGc+gQBdVnvLwk7SwKaNYWrztrSdAbq0ZMlgYeua2thClN NFf/0/aFkD5G4eZUwE2ubNcVRl9xUoBeS9EMpsi94huv4IY2cqoKDMFDvdUU2xKnk4zR 47QPBNDAKcui/wvm9KTuEGYprwvIu5K6/ljcgG65qQL+fsvaDnS23H988rVOUKFb1Wyz /UoR21q+16+QA9LnOzmgE+IvdiN41V2+b+1DyR3ns7C4gDAPqYWqQBcXy6DPgWXNH+uD uKMyx/XTJNXVoky/UwcXjV0ztgEbDWK59orZy3lunD43EC/b1vxqNqU9ThS9ZHbhdXMy dFZA== 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=wuCSqieECaXc/7mA01J8UBPLF9N22sG3IZHrAtRDM3A=; b=jjQ8aI8TJjxuuQVi8cDaW3IVNxTMPzFsSO5oCjBkKLhS7rSnQ7y2VcAe4vh3u5iN6s 3Ex3AfCU8yYx0g1H+c1oFt9FBPT4bVqhoVgvd+F/xhq4yzpNQ+XwnePFcXeH6EBG04eW 2PAHu6kGcSZDo1y3XYPt3zhQlJk+0QFkrQ5+Xv76oOY0TTLB3wVPIAxBjl/866L40dlH TgTH/9LAh42g78ByY9siJ68qOQKI0UADayJXAhhSflVmvVbKt44WPiKsKLN7BwQBNnhz jsBN2voU4aJ/CV3MUFhwPA5+ym9cagXRS2qXjUOtZyLngfW3S5tlL0M//8thwdflsLRF jZIw== X-Gm-Message-State: APf1xPCmZGtX3n1ox0u3lfAYECGN1UyIS0W7fiP+y5VMbyKHBExR21zU FtfNSLfT/jIusMox1xAkuPmHV7MgBXI5ArmV5YHI3w== X-Google-Smtp-Source: AH8x224y/oIydqy994SCr/nQwzkg6/chIea8+jxtzx9msxEsCZtq0oo+jC6eqYppvV3se7sDlc/uZEvjIMRCntOnUfQ= X-Received: by 10.28.101.196 with SMTP id z187mr2707599wmb.29.1518195804362; Fri, 09 Feb 2018 09:03:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Fri, 9 Feb 2018 09:02:43 -0800 (PST) From: Johannes Lundberg Date: Fri, 9 Feb 2018 17:02:43 +0000 Message-ID: Subject: Makefile and nested variables question To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 17:03:26 -0000 Hi Is there some way to use nested variables in the dependency line like so: ${OBJS}: ${${.TARGET:S/$/_DEPS/}} In my case I get nothing.. Cheers! From owner-freebsd-current@freebsd.org Fri Feb 9 17:09:36 2018 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 8CAA1F13BEC for ; Fri, 9 Feb 2018 17:09:36 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from dnvrco-cmomta02.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (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 18D786D886 for ; Fri, 9 Feb 2018 17:09:35 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from bashful.bsd1.net ([74.138.140.144]) by cmsmtp with ESMTPA id kBy3eT3EZmf07kBy6exN4R; Fri, 09 Feb 2018 16:56:10 +0000 Message-ID: <1518195361.5829.2.camel@twc.com> Subject: 12.0-CURRENT missing timezones From: David Boyd To: freebsd-current@freebsd.org Date: Fri, 09 Feb 2018 11:56:01 -0500 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfGTBdBXEFxzOrnnAHRdp278yG3opWyFmDRBqs8pLQSf6uaB7bKa6aPz1glp+3Yc4zSGDTMprA3z+4J3FBJFzPraT2amC9y4av6bwq568xe8CIbl/YU83 ayftBwy1RANFi6/Cm/GBjWn6P0qI/lvjGT8mpYcVNTSM8whDsPjB3CilE5j9SEg0bwC6doXqNMqbAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 17:09:36 -0000 In the most recent images for 12.0-CURRENT FreeBSD-12.0-CURRENT-amd64-20180208-r329009.vmdk.xz FreeBSD-12.0-CURRENT-amd64-20180208-r329009-disc1.iso FreeBSD-12.0-CURRENT-amd64-20180131-r328637-memstick.img the /usr/share/zoneinfo directory is sparsely populated with directories. The only file present is "zone.tab". Thanks for looking into this. David Boyd From owner-freebsd-current@freebsd.org Fri Feb 9 17:13:15 2018 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 62316F14132 for ; Fri, 9 Feb 2018 17:13:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E86D46DDA2 for ; Fri, 9 Feb 2018 17:13:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22d.google.com with SMTP id f4so10379649ioh.8 for ; Fri, 09 Feb 2018 09:13:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2Mr1hMTKAVHSp+1+fFbCrU+PJak2NolRngH+OIX33gs=; b=Wvu8Z6FgPsMJa82L/2YanfF652zjBaidMx08HFeLF/PeFqvYLWcXuNN1a4e7qYbxvo tdF5dOnLgO+ryXwZ5zbPC7HQr54XavuSIJpkR6oaHfxdGq2SWOBGMQfOY8dWwKtZ8ZM2 hPmHmY1lREFAdo0s+ATDA6PY1GOuENjygz9GydvKAEkHkkRkHQLlf2/qNo6wqk5gevoU xHiIM9l8AwjrU0ws5tuNHMm/EhKifp2xTsTvmmmZ5eF9/RUzMKPD98IaOt6J6NyGHnJL u62mKzkqkELcDgrWQ2TeGF0kFAoAxevegNzwVz6QJEo6B1qj+3RHWHUSGKAyCvI01rpR HfJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2Mr1hMTKAVHSp+1+fFbCrU+PJak2NolRngH+OIX33gs=; b=Ol+LIyIUrTW8yY0l3m2ry8Py5/NnyFLu7epZP7GJ+a7+wS96+L0IdxLM9+1bCFD5dO rncGfFMi1HXSCNWistqTQ1ducfSN/tNck2z+ByvV2qP5ZAcPiy+4aQvSZPau3Hbf5j7j vcfrxsbCNUKPMA7Ko2Z8krN3TKEGzEap4d3CHpvEUBDDcKXxKv3sVCJdq3B2OMVRVcE/ mYNKTfQCuKZTL69RFMIFSfNq1AxsNfGtK0azvPKOP7EP+0cb28KtJM23mRpjnmhpIhyM ux4WiSkAdta9sTvf3ODSySfJpWjaHHG0N3qN59GQ1ui0G0XwuxkODL7HAJsFq/7qjghz 786Q== X-Gm-Message-State: APf1xPDWH8l3AZQcYBaI+D/5W0GGn6Rge44qwB/+00wcT6w2dOvGMQ0B TL75g1E58Z7yPFvuTefIR0qQMyEpW6jDCdnwvhN1TA== X-Google-Smtp-Source: AH8x224EdNKbazt1A3ljwRYm9oeR2HMmv5SWls07H8ehtY9lvP0XWtbVLXvZuTW+Kj2Wbdj00vpEDA+/1FJQsMmRcss= X-Received: by 10.107.88.12 with SMTP id m12mr3619239iob.136.1518196394335; Fri, 09 Feb 2018 09:13:14 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Fri, 9 Feb 2018 09:13:13 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <1518195361.5829.2.camel@twc.com> References: <1518195361.5829.2.camel@twc.com> From: Warner Losh Date: Fri, 9 Feb 2018 10:13:13 -0700 X-Google-Sender-Auth: BbM3jA8KZRgupYJhqJS9P8V-rRc Message-ID: Subject: Re: 12.0-CURRENT missing timezones To: David Boyd Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 17:13:15 -0000 On Fri, Feb 9, 2018 at 9:56 AM, David Boyd wrote: > In the most recent images for 12.0-CURRENT > > FreeBSD-12.0-CURRENT-amd64-20180208-r329009.vmdk.xz > > FreeBSD-12.0-CURRENT-amd64-20180208-r329009-disc1.iso > > FreeBSD-12.0-CURRENT-amd64-20180131-r328637-memstick.img > > the /usr/share/zoneinfo directory is sparsely populated with > directories. The only file present is "zone.tab". > I think that may be my fault for changing find -s to find | sort, but I think I neglected to add sort to ITOOLS to fix it. Building a test now. Warner From owner-freebsd-current@freebsd.org Fri Feb 9 17:16:53 2018 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 52C32F144F6 for ; Fri, 9 Feb 2018 17:16:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D294A6DFEA for ; Fri, 9 Feb 2018 17:16:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id l17so10422403ioc.3 for ; Fri, 09 Feb 2018 09:16:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3c6NYgCxIypDeOFTy89vXcJ7pYEwHjA2dYbtgiBcp/8=; b=m96ca9xuesKWQA8nAtL2fGFvKPURMkElEFja+4on83tL/u01pa/CBRvW48GyuCxLbQ V5RqEFsM16omfjlkYW52jMUiUIqayz63G57f2nIwHURDMY7EkOV/y9/QjaGXFMGEkRv8 +jmkUBt0H+HezHgXSJLpnz1q+Iparj5Btv2Pqv/zSm4yATaK5ixZoTIzbxFJ3+EJ3NTn IuwJxAu5/qRD8N7gwSWRzKzxHJJHsX3wkQ3gQh9SiZloAqwPdDpR3v1feOGmBcWaUq6v um/MrEQgB/AgL53ktg/5AtcLUOAoFMytu4wZRRCQENq7sOqJWYzJIts1YsKfG606YwAI Fvng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=3c6NYgCxIypDeOFTy89vXcJ7pYEwHjA2dYbtgiBcp/8=; b=KKmUUlKBorTNYIOLLHcK2ihqDhfw3vTlkVYECmGq3KMSXrv0nx71hAaU0eiQDzCS1d pM5C8CtCAeqUCCMCP3CXH4Ioa1uLSb0blrWn/U+yTTPae89xYf0EnRxAFQ5agbJLkb2/ PqvVRhltDy561oa8cs6Vjx2tejpOV6zLKqLw+8UHZUKY9lwEISy52Uo7lbsP55RD44p5 UlDFRtXagUNtkAp8Fb5g7KzZpIxpd81Fz20XLl+HVlSwIWNFNHSkFyzFfHEwE8vrvAWF zkSXk2r+JKYnccEPVaAoNp8xdlNg+qTac4aQUI9R7yugfGc/AffNnSb0TMyBut6clSP1 gZ1g== X-Gm-Message-State: APf1xPAKRp3Y6Dn9fV9Gz0p9M6Elmo0dR8SQS62Eb4AfCTjA7KfYDQ4D 9rrxUDHPVoXgmgrC4+i3fNlBmEQ0jnyFfiCX27jERA== X-Google-Smtp-Source: AH8x225H9dtDlKus1HjYsYGrq5BAInViWM3aEnwENziQh1uJqTv9RN5YuK/6T2NsC+O9MKhRE/C8meVrXwyrsicpt1o= X-Received: by 10.107.167.69 with SMTP id q66mr3744926ioe.130.1518196612166; Fri, 09 Feb 2018 09:16:52 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Fri, 9 Feb 2018 09:16:51 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <1518195361.5829.2.camel@twc.com> From: Warner Losh Date: Fri, 9 Feb 2018 10:16:51 -0700 X-Google-Sender-Auth: hmTXVIac5GbrcaKSTyml7BXdX_s Message-ID: Subject: Re: 12.0-CURRENT missing timezones To: David Boyd Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 17:16:53 -0000 On Fri, Feb 9, 2018 at 10:13 AM, Warner Losh wrote: > > > On Fri, Feb 9, 2018 at 9:56 AM, David Boyd wrote: > >> In the most recent images for 12.0-CURRENT >> >> FreeBSD-12.0-CURRENT-amd64-20180208-r329009.vmdk.xz >> >> FreeBSD-12.0-CURRENT-amd64-20180208-r329009-disc1.iso >> >> FreeBSD-12.0-CURRENT-amd64-20180131-r328637-memstick.img >> >> the /usr/share/zoneinfo directory is sparsely populated with >> directories. The only file present is "zone.tab". >> > > I think that may be my fault for changing find -s to find | sort, but I > think I neglected to add sort to ITOOLS to fix it. Building a test now. > I am surprised the 0131 is empty, though.... My change was after that. Warner From owner-freebsd-current@freebsd.org Fri Feb 9 17:31:11 2018 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 A1D13F1590B for ; Fri, 9 Feb 2018 17:31:11 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from dnvrco-cmomta01.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) (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 3C8516EF05 for ; Fri, 9 Feb 2018 17:31:10 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from bashful.bsd1.net ([74.138.140.144]) by cmsmtp with ESMTPA id kCTQe0oqRIEdXkCTSeqT3R; Fri, 09 Feb 2018 17:28:35 +0000 Message-ID: <1518197310.5829.4.camel@twc.com> Subject: Re: 12.0-CURRENT missing timezones From: David Boyd To: Warner Losh Cc: freebsd-current@freebsd.org Date: Fri, 09 Feb 2018 12:28:30 -0500 In-Reply-To: References: <1518195361.5829.2.camel@twc.com> X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 X-CMAE-Envelope: MS4wfCfRlw+pOXCxVXFlNLOjJl1CVMNWqZ8HtELVQUnsPLokwTHYjPAi7hNg0FX2PJ2pqDZz3lpJQtbwBmOnlkB6z2rW198US6WcYukWHrcm0J8FkfRsxTlA fmgUvNpQwPbmYMSzadKI0PbiiNKoP4q6tGtW6OfYVoRgkRFwuiCxd1qr2OFY/sEsC05x3DrW3Lf3PXjauEsDRs4yByrgEmK4jOxQk19Zo07QIKORwa/At08W Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 17:31:12 -0000 On Fri, 2018-02-09 at 10:16 -0700, Warner Losh wrote: > On Fri, Feb 9, 2018 at 10:13 AM, Warner Losh wrote: > > On Fri, Feb 9, 2018 at 9:56 AM, David Boyd > > wrote: > > > In the most recent images for 12.0-CURRENT > > > > > > > > > > > >         FreeBSD-12.0-CURRENT-amd64-20180208-r329009.vmdk.xz > > > > > > > > > > > >         FreeBSD-12.0-CURRENT-amd64-20180208-r329009-disc1.iso > > > > > > > > > > > >         FreeBSD-12.0-CURRENT-amd64-20180131-r328637-memstick.img > > > > > > > > > > > > the /usr/share/zoneinfo directory is sparsely populated with > > > > > > directories. The only file present is "zone.tab". > > > > I think that may be my fault for changing find -s to find | sort, > > but I think I neglected to add sort to ITOOLS to fix it. Building a > > test now. > > I am surprised the 0131 is empty, though.... My change was after > that. > > Warner Oops. My mistake (cut and paste error).  All dates should be 20180208. From owner-freebsd-current@freebsd.org Fri Feb 9 18:48:32 2018 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 1ECFEF1ADD2 for ; Fri, 9 Feb 2018 18:48:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0B8472763 for ; Fri, 9 Feb 2018 18:48:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id c80so11829015itb.4 for ; Fri, 09 Feb 2018 10:48:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rrSdgHE5Optotw07iMwreci3tuAeNLxvOTTou0fKbDA=; b=C4EPAk9s21AfXngipUDGjAN5+CtX3c8hBTAoT0d2RSMAFmhjOhyQUSZZPFdBYhQToV lpENjmZUpHuyhqv/OWf2M4pEuGH5XE7Tql/iNaIxkF5yEZL6aq31aQ7isn4XuL8js8SC NUBP3SlBR7tigt7bJp2hfhlT2z0NImr44vEolcW3PL4YtcR1XMCMBdAoe3q5znqKcaNI qUD6DfUHyZkv1T/5ShY0U42+GUJwYiW/nN0Gi0uVloUH9nL1VAqOG24PaB3rHwqI7dw5 vnnOm40ZOOW9BGUKqnHuv5ySDhd6+kKPiinkzYFP49ROyTnfPTxbhw/Buw6oIgjDDC+E Z7bA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rrSdgHE5Optotw07iMwreci3tuAeNLxvOTTou0fKbDA=; b=CNAaVPdE830l3iE3TlkaTVKtZFGhKdXdd5ZMvlVmFh6q1iKecJ8CvtBkJg5W33k20w Aiyq3z6A6Mz/CdhaKMqcNvdjKLjV7DZnmV3i8Verp2ohpySX/BsLRCYKyfsWyRUgBXUk lWZznDoEr7F1Y+G8JEjWC82YT9X0gTkA1FV5nlsKKummCS1Eah3vBct6JStLlTgjPjjK SwydMskpBgSwR+y9Lzbo2RTv8pcltzJVGgT3LKV8EpTUIn8UTS+DktE9iB5sSlb606Vo ZfeQrnprNdg+ybSCZKvpE0Zj3ia4b1XfVp34BbfGr6IYFGfX8y1jBPqo4QBXIFIkmbNu t9Cw== X-Gm-Message-State: APf1xPDgGnP9PBPU8jZPbkKErE5t+CvF6mgSSTHrfCsuKXtSEbA3EBL1 IAG2B9vG1ICocHbL/pbkEi11REyqzoaP9BslVYeYZP7T X-Google-Smtp-Source: AH8x224EjF4mZg2yOJ2mcf+IRijazCKQG9RnNYjPSoXrHYiWz4fSUOlHA5wMm/UL9lqReQpNUDJX747MmG6LzTZ8yGM= X-Received: by 10.36.82.71 with SMTP id d68mr4743842itb.50.1518202110951; Fri, 09 Feb 2018 10:48:30 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Fri, 9 Feb 2018 10:48:30 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <1518197310.5829.4.camel@twc.com> References: <1518195361.5829.2.camel@twc.com> <1518197310.5829.4.camel@twc.com> From: Warner Losh Date: Fri, 9 Feb 2018 11:48:30 -0700 X-Google-Sender-Auth: u0woAqok6Tb8wnfR1djVxekMFtA Message-ID: Subject: Re: 12.0-CURRENT missing timezones To: David Boyd Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 18:48:32 -0000 OK. That makes sense again. I've pushed two changes (r329064 and r329075) which should correct this. Warner On Fri, Feb 9, 2018 at 10:28 AM, David Boyd wrote: > On Fri, 2018-02-09 at 10:16 -0700, Warner Losh wrote: > > > > On Fri, Feb 9, 2018 at 10:13 AM, Warner Losh wrote: > > > > On Fri, Feb 9, 2018 at 9:56 AM, David Boyd wrote: > > In the most recent images for 12.0-CURRENT > > FreeBSD-12.0-CURRENT-amd64-20180208-r329009.vmdk.xz > > FreeBSD-12.0-CURRENT-amd64-20180208-r329009-disc1.iso > > FreeBSD-12.0-CURRENT-amd64-20180131-r328637-memstick.img > > the /usr/share/zoneinfo directory is sparsely populated with > directories. The only file present is "zone.tab". > > > I think that may be my fault for changing find -s to find | sort, but I > think I neglected to add sort to ITOOLS to fix it. Building a test now. > > > I am surprised the 0131 is empty, though.... My change was after that. > > Warner > > > Oops. My mistake (cut and paste error). All dates should be 20180208. > From owner-freebsd-current@freebsd.org Fri Feb 9 22:47:20 2018 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 BABE4F08AA9 for ; Fri, 9 Feb 2018 22:47:20 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63B1B7D93C; Fri, 9 Feb 2018 22:47:20 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 387E7A681; Fri, 9 Feb 2018 22:47:20 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 0D6388CDE; Fri, 9 Feb 2018 22:47:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 0B0hrENeCm8P; Fri, 9 Feb 2018 22:47:12 +0000 (UTC) Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 6012C8CD7 To: Vladimir Zakharov , freebsd-current@freebsd.org References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> Date: Fri, 9 Feb 2018 14:47:10 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180201091030.qmq4boyzvvvqkug6@vzakharov> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 09 Feb 2018 22:47:21 -0000 On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: > Hello! > > For some time (about a week) building and installing kernel fails with > the error "Variable OBJTOP is recursive." when going to build/install > module from ports. > > Last successful build was at r328426. Next build at r328527 failed and > still broken at r328649. > > Without PORTS_MODULES building and installing kernel succeeds. Another > workaround: ignore error and build/install module directly from ports. > > # cat /etc/make.conf > MALLOC_PRODUCTION=yes > KERNCONF=GENERIC-NODEBUG GENERIC > #KERNCONF= GENERIC-NODEBUG > CPUTYPE?=native > #PORTS_MODULES = graphics/drm-next-kmod emulators/virtualbox-ose-kmod > PORTS_MODULES = graphics/drm-next-kmod > > DOC_LANG = en_US.ISO8859-1 ru_RU.KOI8-R > > WITH_DEBUG_PORTS = mail/neomutt > > WITH_CCACHE_BUILD=yes > CCACHE_DIR=/home/ccache > > #DEVELOPER=yes > > ... > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.full > --- kernel.full --- > linking kernel.full > ctfmerge -L VERSION -g -o kernel.full ... > text data bss dec hex filename > 22584632 1376209 4748888 28709729 0x1b61361 kernel.full > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.debug > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel > --- all --- > ===> Ports module graphics/drm-next-kmod (all) > cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX > -u CPP -u MAKESYSPATH MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D > NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64 > TARGET_ARCH=amd64" SYSDIR=/usr/src/sys > PATH= > SRC_BASE=/usr/src OSVERSION=1200056 > WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B > clean build > ===> Cleaning for drm-next-kmod-g20180117 > ===> License BSD2CLAUSE MIT GPLv2 accepted by the user > ===> drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by drm-next-kmod-g20180117 for building > ===> Extracting for drm-next-kmod-g20180117 > => SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz. > ===> Patching for drm-next-kmod-g20180117 > ===> drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found > ===> Configuring for drm-next-kmod-g20180117 > ===> Building for drm-next-kmod-g20180117 > ===> drm (all) > Variable OBJTOP is recursive. For some reason I cannot recreate this issue. -- Regards, Bryan Drewery From owner-freebsd-current@freebsd.org Sat Feb 10 00:00:04 2018 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 7602AF0D504 for ; Sat, 10 Feb 2018 00:00:04 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 222DA8017C; Sat, 10 Feb 2018 00:00:04 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id EE732B369; Sat, 10 Feb 2018 00:00:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id C01F78E11; Sat, 10 Feb 2018 00:00:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id B1PE8RGGzS3n; Sat, 10 Feb 2018 00:00:00 +0000 (UTC) Subject: Re: Makefile and nested variables question DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com BCBA68E0C To: Johannes Lundberg , freebsd-current References: From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <02523ce9-4771-e63f-1c0e-735998bf1f67@FreeBSD.org> Date: Fri, 9 Feb 2018 15:59:50 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u7gU0EWK11oMDi0hOfUxRXlnax214FBqe" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 00:00:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --u7gU0EWK11oMDi0hOfUxRXlnax214FBqe Content-Type: multipart/mixed; boundary="yXZa17jINsNpo3iw2uTYFjBvRdHsXBvwe"; protected-headers="v1" From: Bryan Drewery To: Johannes Lundberg , freebsd-current Message-ID: <02523ce9-4771-e63f-1c0e-735998bf1f67@FreeBSD.org> Subject: Re: Makefile and nested variables question References: In-Reply-To: --yXZa17jINsNpo3iw2uTYFjBvRdHsXBvwe Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2/9/2018 9:02 AM, Johannes Lundberg wrote: > Hi >=20 > Is there some way to use nested variables in the dependency line like s= o: >=20 > ${OBJS}: ${${.TARGET:S/$/_DEPS/}} >=20 > In my case I get nothing.. >=20 I think I need more details. That line won't work. ${.TARGET} is only defined *in a running target*, not while declaring dependencies. If these OBJS are C files then this syntax may be enough to only declare the dependencies when really needed. OBJS_DEPEND_GUESS.foo.o +=3D bar.h bar.c Rather than what I think you tried: foo.o_DEPS +=3D bar.h bar.c If you want them declared always (ignoring .depend files) then just: foo.o: bar.h bar.c --=20 Regards, Bryan Drewery --yXZa17jINsNpo3iw2uTYFjBvRdHsXBvwe-- --u7gU0EWK11oMDi0hOfUxRXlnax214FBqe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJafjX8AAoJEDXXcbtuRpfPgLMIAJSKSt3PLp7Bv8p+yLo7XqL3 VuvwBN6tsCk6srYbFXdsydXMRjOkjf71+GWjDU/T1OtYc0miFenudH6L+wYI7STB 6OccjbD4DrUWq+rfvid9//GNJK5EWw37phNqxPItMI9Ixo2adhRkOHy50vZxEVci YiMkrVnA8XJFLvM+zIJog1Gr7aIsajMdxyxRnTz9HXqBr18tPZBGWKDZklpjqjTG dqr2O6t9RMztL0Vgu3kTNNCJUqDlU2Zz+/wXsLADdNsJSeIvUirDQU8ceeJyvFQK Y9MKG2tQuwKZYttghQ9ljbTPrlWQZpZUxFbSlCKEFc5Riea7qdP/vn299TeccPg= =TNwa -----END PGP SIGNATURE----- --u7gU0EWK11oMDi0hOfUxRXlnax214FBqe-- From owner-freebsd-current@freebsd.org Sat Feb 10 07:53:05 2018 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 175BBF04D3D; Sat, 10 Feb 2018 07:53:05 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E8B271833; Sat, 10 Feb 2018 07:53:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.129.41]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0La3c1-1f7cmA1LDx-00lpQC; Sat, 10 Feb 2018 08:52:55 +0100 Date: Sat, 10 Feb 2018 08:52:21 +0100 From: "O. Hartmann" To: "Bjoern A. Zeeb" Cc: "O. Hartmann" , freebsd-jail@freebsd.org, freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> In-Reply-To: <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/iZ3C2Do29sYhN8rpa4JmBL/"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:vEgHj1sxHwePDeyJjnZM50fzClp8+HZzt122w1gU1aNx8FJy2Pz FecjtkqUzU5MS/RnuMJzXrcjbzSLj09mbcHPTk9ZgRVM8L5kaq5aqXq1+aqSXp5y2F8/MYh yK/xpUC1MgZfu7dE9244gjvxbTABW2iz6gl+5bgb99GBXLiuHkTov4oSqas43GRkQxJYzxM EC9Qt/Ss08/3kY/h9g0Jg== X-UI-Out-Filterresults: notjunk:1;V01:K0:MY4N0F7pXmk=:ufCY0ULHzRRMTXgrKOi+i8 sXAYSdia46wkS3hLw9yvhVGea/oQTpx+opja5VwuUbURsKFXHoTYUvhxeYOczZAz/QHjFmga/ 4kiJkMvF0QXRik6pf+cZS1NvvXHmj3QPupoWVDRp31bBTRbCusze9DzfKutoHBomsQNc71UGa xxIt72DVoamCPCXbKoFSbSZd/OCDgQPFgvA9wGRiTMujLpk3t5oJVsRbBgZj/g5mLdzVYTRUj gB3LM2WIm4ryiI1RBbgvhVBii+17T2tVgf4Vu3FUgh8da48kS0RmpKCDC9yyyEe8QaxeknY+E +Zf2BvW3VO7mFSI6TIfASKMVtLohxVHVXh5f6Q/KXjjX6XfXE65spV3TDaJxeHOq8U0Pe614U VP8njaYf4LjLdaHZVFL8fKaPcW/FsDCv2j0ZyupO50+R1Z9C9L1aIRpTm7HuFwSVH0wiCzOsc 3F/5I+Fxm/Tsq6R3r9dZH8UVnLP1pU2ykFe9U0Lu8h9KRBFp63xQU9BEcgZkpnEVgao1ydNuI jrOI/OyzhaPW7rbpErSPxQO5x5erBq0iTYnrEcMOqATLRuwiBFCk6Y3RQLAup/0gHOQpXydwn NXNBJZAFe7WhXej6aI05KIW57TMvknktx0J5oIWbTiOIXIxfNxHi2nmROrmwyPUspGwlV1P3F 9HdgPZqyMaw8GI+VvKOUJXc0wzZkO2F6SJOHYcjIz/x2jP6uhwC7b2Smyn6HqC/KGAGDo0cwq sR/ZrMCdAUI+MmsThECUDoLFKUyzbhw7zHhr2RCUKY/f9rgQHJ/rW+LzReOXsivntmIgPb5g0 Rxfem9Ykn6bIQBUtIDYYt29TyZZ5w== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 07:53:05 -0000 --Sig_/iZ3C2Do29sYhN8rpa4JmBL/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 09 Feb 2018 16:43:17 +0000 "Bjoern A. Zeeb" schrieb: > On 9 Feb 2018, at 16:22, O. Hartmann wrote: >=20 > > Am Thu, 8 Feb 2018 09:31:15 +0100 > > "O. Hartmann" schrieb: > > > > Is this problem to trivial? =20 >=20 > I read through it yesterday and found myself in the position that I need= =20 > a whiteboard or paper and pencil or an ASCII art of your situation. But= =20 > by the time I made it to the question I was basically lost. Could you=20 > massively simplify this and maybe produce the ASCII art? >=20 > /bz > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" All right. I'm not much of an artist and at this very moment, I haven't much experienc= e with neat ASCII art tools. But I'll provide a sketch later, but I also will simplify = the situation. Consider three "vswitches", basically based on the creation of bridges, bri= dge0, bridge1, bridge2. Create at least three individual vnet-jails attached to each vbrid= ge. Those jails have epair pseudo devices. The jail itself owns the "a-part" of the e= pair and the b-part is "member of the bridge". Each jail's epairXXXa has an IP assigned = of the network the vswitch is part of. I mention a- and b-part of the epair here, because = I thought it could matter, but I think for symmetry reasons it doesn't. Now consider a further, special jail. This jail is supposed to have three e= pair devices, each one is reaching into one of the vbridges. This jail is the router/rout= ing jail. Later, this jail should filter via IPFW the traffic between the three vbrid= ges according to rules, but this doesn't matter here, beacuase the basics are not working= as expected. Now the problems. It doesn't matter on which jail of the three vswitches I = login, the moment a vbridge has more than two member epairs (one is alway member of t= he routing jail, now consider a database jail and a webserver jail), pinging each jail= or the routing jail fails. It works sometimes for a couple of ICMP packets and the= n stops. If each vbridge has only one member jail, I have NO PROBLEMS traversing acc= ordingly to the static routing rules from one vbridge to any other, say from vbridge1 t= o vbridge0 or vbridge2 and any permutation of that. The moment any of the bridges gets an additional member epair interface (so= the bridge has at least three members including the on reaching into the virtual route= r jail) the vbridge seems to operate unpredictable (to me). Pinging jails memeber of th= at vbridge are unreachable. Technical information: The kernel has options IPFIREWALL, VIMAGE. The host's ipfw (kernel) decline= s packets by default. Each jail is configured to have ipfw "open". Thanks for the patience. Kind regards, O. Hartmann --Sig_/iZ3C2Do29sYhN8rpa4JmBL/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWn6k0AAKCRDS528fyFhY lNE+AgCbqIMTxE2O3ejPWmxVBxfd3Kh5NSZ+NPpHkuJ7Gh/U6yuZLbJWsbgpccGR degqacPcwWakbJAnqdQ9uXurJXSnAf9e76H89cTGqs9KCrWTKrUWUrH5fKFcLhO/ dN47cv6ZUn7xKCcqeudC2NKQA1C18DG+W6DqD22LL50xLIGHzDlm =ZIqA -----END PGP SIGNATURE----- --Sig_/iZ3C2Do29sYhN8rpa4JmBL/-- From owner-freebsd-current@freebsd.org Sat Feb 10 08:55:57 2018 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 7573CF09084; Sat, 10 Feb 2018 08:55:57 +0000 (UTC) (envelope-from zec@fer.hr) Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.fer.hr", Issuer "TERENA SSL CA 3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9DDE73C32; Sat, 10 Feb 2018 08:55:56 +0000 (UTC) (envelope-from zec@fer.hr) Received: from x23 (31.147.122.18) by MAIL.fer.hr (161.53.72.233) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sat, 10 Feb 2018 09:54:43 +0100 Date: Sat, 10 Feb 2018 09:54:49 +0100 From: Marko Zec To: "O. Hartmann" CC: "Bjoern A. Zeeb" , , freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180210095449.3117e6d9@x23> In-Reply-To: <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [31.147.122.18] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 08:55:57 -0000 On Sat, 10 Feb 2018 08:52:21 +0100 "O. Hartmann" wrote: > Am Fri, 09 Feb 2018 16:43:17 +0000 > "Bjoern A. Zeeb" schrieb: > > > On 9 Feb 2018, at 16:22, O. Hartmann wrote: > > > > > Am Thu, 8 Feb 2018 09:31:15 +0100 > > > "O. Hartmann" schrieb: > > > > > > Is this problem to trivial? > > > > I read through it yesterday and found myself in the position that I > > need a whiteboard or paper and pencil or an ASCII art of your > > situation. But by the time I made it to the question I was > > basically lost. Could you massively simplify this and maybe > > produce the ASCII art? > > > > /bz > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > > All right. > > I'm not much of an artist and at this very moment, I haven't much > experience with neat ASCII art tools. But I'll provide a sketch > later, but I also will simplify the situation. > > Consider three "vswitches", basically based on the creation of > bridges, bridge0, bridge1, bridge2. Create at least three individual > vnet-jails attached to each vbridge. Those jails have epair pseudo > devices. The jail itself owns the "a-part" of the epair and the > b-part is "member of the bridge". Each jail's epairXXXa has an IP > assigned of the network the vswitch is part of. I mention a- and > b-part of the epair here, because I thought it could matter, but I > think for symmetry reasons it doesn't. > > Now consider a further, special jail. This jail is supposed to have > three epair devices, each one is reaching into one of the vbridges. > This jail is the router/routing jail. Later, this jail should filter > via IPFW the traffic between the three vbridges according to rules, > but this doesn't matter here, beacuase the basics are not working as > expected. > > Now the problems. It doesn't matter on which jail of the three > vswitches I login, the moment a vbridge has more than two member > epairs (one is alway member of the routing jail, now consider a > database jail and a webserver jail), pinging each jail or the routing > jail fails. It works sometimes for a couple of ICMP packets and then > stops. > > If each vbridge has only one member jail, I have NO PROBLEMS > traversing accordingly to the static routing rules from one vbridge > to any other, say from vbridge1 to vbridge0 or vbridge2 and any > permutation of that. > > The moment any of the bridges gets an additional member epair > interface (so the bridge has at least three members including the on > reaching into the virtual router jail) the vbridge seems to operate > unpredictable (to me). Pinging jails memeber of that vbridge are > unreachable. > > Technical information: > > The kernel has options IPFIREWALL, VIMAGE. The host's ipfw (kernel) > declines packets by default. Each jail is configured to have ipfw > "open". > > Thanks for the patience. If you could provide a script which sets up the topology you described in two lengthy posts then others could reproduce this, and your chances of getting useful feedback would certainly increase. We also have a graphical tool (https://github.com/imunes/imunes) which can set up a topology like you described in a few clicks of a mouse, albeit using netgraph and ng_eiface instead of epairs, but I assume this is irellevant as long as you are not aiming for maximum packet throughputs. If you attempt to use this tool, note that selecting "stpswitch" will create if_bridge instances, whereas "lanswitch" creates ng_bridge instances. Good luck, Marko > > Kind regards, > > O. Hartmann From owner-freebsd-current@freebsd.org Sat Feb 10 09:36:45 2018 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 2EE94F0BFF3 for ; Sat, 10 Feb 2018 09:36:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B50F27557F for ; Sat, 10 Feb 2018 09:36:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id l17so12401247ioc.3 for ; Sat, 10 Feb 2018 01:36:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=c7pvXEdYum4RfoeXxB8uITV9WpGlEYMhuNAAD9bpiP8=; b=dja3dGPh8NdCY+7rtUocgZMkBiI54QYTz1XlijRpVEFxgyCZgYeD4NeG6lpXPCgftL hlCZ8Oo9dIjLEZQkg0/NvmhdjRIn5pM+53hzK5dvVV1eUOt4jMySZt1x6nwOkuRabYU8 DmhZo+nv55eMBruVPgSxTdoahsaNxtdCaQvMXJx7n9nO1B9AMNi+gH+bLYNGJCK2RnSG 2u3cH7IHUP1GoS/jlsU2WmZcmC3sKv54Qy8FtyvURjXJIwwD829NGAM9K8X0cWP0/GPc 7HpwR89yDDBnW+dQ5YYC6kGqAi34rU//pDhWSFs8qytCp20sgKiqJeXgR0FrEhCCmkti XalQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=c7pvXEdYum4RfoeXxB8uITV9WpGlEYMhuNAAD9bpiP8=; b=ntMFHAUrFeiHHsFso5WbceTXblBxYA/sNmmZ3sb2nzvx9SlycZ7t8Uw8+yyJivsyJi 4/z+TzNT77ZT9CiVJzpFlT3H9uOC5HiYemNA0aD5+uY0rILrsS7JTd8ZgDPomiMMuMBJ YE5wEp5rieUsrKfPnOwwklWH38AyZgyRQZrxAjX3ZTIeFo4LXV+V/dzGFCi0GkP/tM5z VQAdS8Ex9v+11RBeFW6ys/3ENzN2z0EHYwctspfm6hznUS/JTDDMPyfdcDV1u766YERi CylC+1WllU7vuUs+C8GDfv8/8v5IBLihP4PTbrHWkeA0Gl4Uai5c8h/Zg5fZT/QUywY+ 28NQ== X-Gm-Message-State: APf1xPAKf277Fv1odFLezXNDyCpKuzWQi3VFWavbeWD888pB0dxnkZmx kmFA/lAfBbE9vFuGovuraY3lf0hcWYPkGQDvzvseCg== X-Google-Smtp-Source: AH8x225PaIkTietnozGop5QhkGJ40NzfKdl/rFOLr7ODWDkHh3UW0/mjp+uuEzavJDhsOC/BpMEfOyusTYOhBwjR3c0= X-Received: by 10.107.107.1 with SMTP id g1mr6107939ioc.63.1518255403198; Sat, 10 Feb 2018 01:36:43 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Sat, 10 Feb 2018 01:36:42 -0800 (PST) X-Originating-IP: [50.253.99.174] From: Warner Losh Date: Sat, 10 Feb 2018 02:36:42 -0700 X-Google-Sender-Auth: pcUM35GIi8k-hJR3AYTAbMPg98E Message-ID: Subject: Lua Loader changes posted To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 09:36:45 -0000 I'm at a good point in the lua loader, so I've posted changed to https://reviews.freebsd.org/D14295 for review. It works great in the userboot.so loader test harness, but I've not booted this on real hardware yet, so anyone wanting to take it for a spin be sure you have an old-working loader or some other way to recover your machine / VM. It's purely opt-in right now. You must build WITHOUT_FORTH=yes and WITH_LOADER_LUA=yes. The good news is you don't need a full buildworld. You can just build stand (but don't forget the above options on both the build and the install). It's getting close. But there's no man page (it will be committed without one unless someone else writes it). I've done a lot of cleanup of the original GSoC code that was then cleaned up a bit by Rui, etc (all the names of the contributors are in the review and will be in the commit message). However, I'm sure the lua code could use some more cleanup. The menu code is especially inefficient at drawing boxes and could likely use some additional cleanup. Despite the slight roughness around the edges, I'm grateful to Zakary Nafziger's menu changes from this past fall. They look a lot better than the final GSoC state. I arbitrarily decided to follow the same conventions we do with style(9) for the lua code. The loader and os module code (the C code in lutil.c) could also use some close scrutiny. I've cleaned up the LUA code to match the new lua modules stuff, but haven't done this code at all and it likely could benefit from a final pass there. The original code was written before you could have integers, so there may be a couple of stray places that still use numbers. If anyone with a lot of Lua embedding experience could look, that would be great. Please let me know what you think. It's been a long road to get /stand into decent enough shape to allow us to build lua w/o changes to lua (OK, only 1 change to lua since there was a format that was forced to be floating point that couldn't change with a #define). It's also quite a bit different than either the final GSoC code, or the Rui branch, or the cleaned up, forward ported Rui branch. Most of my changes have been to the C glue code, though I did some tweaks to the lua code. Warner From owner-freebsd-current@freebsd.org Sat Feb 10 11:17:47 2018 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 D5551F135CE; Sat, 10 Feb 2018 11:17:46 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AC1479C3A; Sat, 10 Feb 2018 11:17:45 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-io0-f180.google.com with SMTP id x188so5993322iod.1; Sat, 10 Feb 2018 03:17:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iGOCw4brYEQX1TrCaApbFMjc8ZWo3Afcfcm44WwTXMc=; b=o3yZZRwSsEWxZZu50llE2WUltaIJme0I3/gFqdI279mBUkkhOo8d0rCgCeO/2/qOC/ uNoI/rbWMtQvYfpLSS5c3NKPQNc9ijnl5IyXmRr1cWk6f5y1fUiGMgjBtSMJBa0DQ8fw Ibhq7GtUHT2lVjAkbT4IcEgzORavG1Y82h8NYxS5nkKzQ63YThA1FhgeqevNgOSS8cW1 jQNry/T5nGMNYfpq4Qnm+9SbDQZMbF3qTptyIgZhLm8Htzpl2BAfKxeTl/5oQkcu2crc 1GQYZNo5T2wFdu7w0h7QH+Xt9aRpS+vpeaOTkfMgiAaUP0+NZZmEVAxxITlbO3y2e5j4 O6Xw== X-Gm-Message-State: APf1xPAcyQKmIEO6SrIUAZYaWl5MOaG1xiQUCHHvhW/zLelWNOKGtEHE 9DLvZ811ETsrtylS7ZLbHqtN4QIy X-Google-Smtp-Source: AH8x227CC8wEJDY/FBYIW6nDtrFqQxUu5Y3ntKX70lya7iumoeHlT8oeZz6Pku62Vgxe6PAt8FqrCg== X-Received: by 10.107.173.12 with SMTP id w12mr1020500ioe.282.1518259960180; Sat, 10 Feb 2018 02:52:40 -0800 (PST) Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com. [209.85.192.182]) by smtp.gmail.com with ESMTPSA id y81sm1817003ita.40.2018.02.10.02.52.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Feb 2018 02:52:39 -0800 (PST) Received: by mail-pf0-f182.google.com with SMTP id p1so2312469pfh.4; Sat, 10 Feb 2018 02:52:39 -0800 (PST) X-Received: by 10.99.168.76 with SMTP id i12mr4798000pgp.420.1518259958879; Sat, 10 Feb 2018 02:52:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.179.149 with HTTP; Sat, 10 Feb 2018 02:52:18 -0800 (PST) In-Reply-To: <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Sat, 10 Feb 2018 11:52:18 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing To: "O. Hartmann" Cc: freebsd-jail@freebsd.org, freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 11:17:47 -0000 On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann wrote= : > > The moment any of the bridges gets an additional member epair interface > (so the bridge > has at least three members including the on reaching into the virtual > router jail) the > vbridge seems to operate unpredictable (to me). Pinging jails memeber of > that vbridge > are unreachable. > > =E2=80=8BFirst idea: Did you try with a more simple setup, like with just 3 jails members of one bridge ? =3D> I've tried it on a -head, and all 4 members (3 jails and the host) reach to communicate. Second idea: Can you check that all epairs have different MAC address each ?=E2=80=8B I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 Regards, Olivier From owner-freebsd-current@freebsd.org Sat Feb 10 17:28:18 2018 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 C3484F0D77E for ; Sat, 10 Feb 2018 17:28:18 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 62611687CC for ; Sat, 10 Feb 2018 17:28:18 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 9D2822EBD7; Sat, 10 Feb 2018 18:28:15 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZfBONAyhHLF; Sat, 10 Feb 2018 18:28:15 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 2E2252EBD5 for ; Sat, 10 Feb 2018 18:28:15 +0100 (CET) To: freebsd current From: Willem Jan Withagen Subject: posix_fallocate on ZFS Message-ID: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> Date: Sat, 10 Feb 2018 18:28:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 17:28:18 -0000 Hi, This has been disabled on ZFS since last November. And I do understand the rationale on this. BUT I've now upgraded some of my HEAD Ceph test systems and they now fail, since Ceph uses posix_fallocate() to allocate space for the FileStore-journal. Is there any expectation that this is going to fixed in any near future? --WjW From owner-freebsd-current@freebsd.org Sat Feb 10 18:24:34 2018 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 C8154F119B8 for ; Sat, 10 Feb 2018 18:24:34 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27E996ACB1 for ; Sat, 10 Feb 2018 18:24:34 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id h78so8257976lfg.6 for ; Sat, 10 Feb 2018 10:24:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ifRRi3xCwmYMttZH3HzPeYMd+pnEJHSCkiKYZ7mxjGk=; b=o0MSSj5gvyG8PhuBU+9XItakYjyId9SPNYg3MbXaUDnvm7f2ZSLUVgvVHjM0coCLA/ 50sJOMVhvQzcLYNS9kTOwpPUNp0R1ChE+Xocd5qSHwSAxQjoGBinBKhhjQh83h9yw4ro aC2Tj/f54OWGp7oWeTHcvJ93VBTmOUN7AT44M7OvptQKxntTMx26ocHd6UWQ4gVUyemq kI/SL25HThsPRQqjAjeUHlJzdZ4fkgwCHup1UoeOCEBC7ZhMHQXRGNStwN8jlYvy2QsL 3RaptHVzSPFC3a/AL1Bh1ZCyyRDsnH52a1E1t8RPDpdt/a/8VmCrAKck/oK6hVrWnTbW oxKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ifRRi3xCwmYMttZH3HzPeYMd+pnEJHSCkiKYZ7mxjGk=; b=F/8GKczG8szu3y2RE9BhOfyT5+fcC21zpmuBtozx3pHJrTUWtKQfyXO8rNhWqNJRY8 IsdyJNDayh2C3zUnQvPuEGNk6hsr5Ql99qtX0Kz805o3THGIaLYkrwbIgYl9U/elnfUo NM+cBFZXfvnWO2NGA/lFAim+ACFAa6wAniwyvvrwyTu0DtZvD4W1J44OFGFSC5V28bHA WHSY46kAufYRmDbfsiFSHfje52PwdCChBQN6iPHANrqxwiazOvD1VUyFor/QHCKgWdhY ltp4mF3bzai2wU4V0BA2f66afTc6IvgZEA43GJO3Eov3QXwlpC5ez+UlNMNtY5uIzoVK 9ouw== X-Gm-Message-State: APf1xPA8MNKYBhSijJO/0EOxrTPQD7ItcXay0CPbFtKhN5YEU4HyZIg+ 2rBbxXlJlc+xfFWIN7izAEZJuUwqR1hGAs/kt+g= X-Google-Smtp-Source: AH8x226a3ZW71gdKJPZmuyeIYdHUpH15RYJ+A3f05VrgX4YTHYyW82sgtzpFWXSgYnhI9bybdq8xXLlBS8Kxy814p3c= X-Received: by 10.25.151.209 with SMTP id z200mr4356190lfd.41.1518287072212; Sat, 10 Feb 2018 10:24:32 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Sat, 10 Feb 2018 10:24:31 -0800 (PST) In-Reply-To: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> From: Alan Somers Date: Sat, 10 Feb 2018 11:24:31 -0700 X-Google-Sender-Auth: QeX4uIVCo7oJNfZyRVgFcW4lfWQ Message-ID: Subject: Re: posix_fallocate on ZFS To: Willem Jan Withagen Cc: freebsd current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 18:24:35 -0000 On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen wrote: > Hi, > > This has been disabled on ZFS since last November. > And I do understand the rationale on this. > > BUT > > I've now upgraded some of my HEAD Ceph test systems and they now fail, > since Ceph uses posix_fallocate() to allocate space for the > FileStore-journal. > > Is there any expectation that this is going to fixed in any near future? > > --WjW > No. It's fundamentally impossible to support posix_fallocate on a COW filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, since the system call is merely advisory. -Alan From owner-freebsd-current@freebsd.org Sat Feb 10 18:50:37 2018 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 86E1FF13932 for ; Sat, 10 Feb 2018 18:50:37 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 287616BBD9; Sat, 10 Feb 2018 18:50:37 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 7BCF72E001; Sat, 10 Feb 2018 19:50:28 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9U_E4vEmQ9W; Sat, 10 Feb 2018 19:50:27 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id BE2D32F000; Sat, 10 Feb 2018 19:50:27 +0100 (CET) Subject: Re: posix_fallocate on ZFS To: Alan Somers Cc: freebsd current References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> From: Willem Jan Withagen Message-ID: <985b6d77-9f27-f6f4-ea0e-165951d91048@digiware.nl> Date: Sat, 10 Feb 2018 19:50:28 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 18:50:37 -0000 On 10/02/2018 19:24, Alan Somers wrote: > On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > wrote: > > Hi, > > This has been disabled on ZFS since last November. > And I do understand the rationale on this. > > BUT > > I've now upgraded some of my HEAD Ceph test systems and they now > fail, since Ceph uses posix_fallocate() to allocate space for the > FileStore-journal. > > Is there any expectation that this is going to fixed in any near future? > > --WjW > > > No.  It's fundamentally impossible to support posix_fallocate on a COW > filesystem like ZFS.  Ceph should be taught to ignore an EINVAL result, > since the system call is merely advisory. Yup, that was what I'm going to do. But then I would like to know how to annotate it. And I guess that I'd get reactions submitting code to fix this, since the journal could run out of space. So I'd beter know what is going on. I seem to remember that on a pool level is is possible to reserve space whilest creating a filesystem? And then it could/should be fixed when building the disk-infra for an OSD. --WjW From owner-freebsd-current@freebsd.org Sat Feb 10 18:46:38 2018 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 2792FF133EB for ; Sat, 10 Feb 2018 18:46:38 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::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 C4E1F6B9B2; Sat, 10 Feb 2018 18:46:37 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id w1AIkYbb000169; Sat, 10 Feb 2018 13:46:35 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id w1AIkX4Y000167; Sat, 10 Feb 2018 13:46:33 -0500 (EST) (envelope-from wollman) Date: Sat, 10 Feb 2018 13:46:33 -0500 (EST) From: Garrett Wollman Message-Id: <201802101846.w1AIkX4Y000167@hergotha.csail.mit.edu> To: asomers@freebsd.org Subject: Re: posix_fallocate on ZFS X-Newsgroups: mit.lcs.mail.freebsd-current References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> Organization: none Cc: freebsd-current@freebsd.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (hergotha.csail.mit.edu [127.0.0.1]); Sat, 10 Feb 2018 13:46:35 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hergotha.csail.mit.edu X-Mailman-Approved-At: Sat, 10 Feb 2018 19:10:47 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 18:46:38 -0000 In article , asomers@freebsd.org writes: >On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen >wrote: >> Is there any expectation that this is going to fixed in any near future? >No. It's fundamentally impossible to support posix_fallocate on a COW >filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, >since the system call is merely advisory. I don't think it's true that this is _fundamentally_ impossible. What the standard requires would in essence be a per-object refreservation. ZFS supports refreservation, obviously, but not on a per-object basis. Furthermore, there are mechanisms to preallocate blocks for things like dumps. So it *could* be done (as in, the concept is there), but it may not be practical. (And ultimately, there are ways in which the administrator might manage the system that would defeat the desired effect, but that's out of the standard's scope.) Given the semantic mismatch, though, I suspect it's unreasonable to expect anyone to prioritize implementation of such a feature. -GAWollman From owner-freebsd-current@freebsd.org Sat Feb 10 19:21:54 2018 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 219B1F15E08 for ; Sat, 10 Feb 2018 19:21:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 789576D134 for ; Sat, 10 Feb 2018 19:21:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id a204so15531466lfa.2 for ; Sat, 10 Feb 2018 11:21:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9qaQDr685zUJ24ISz4SmEC8SLh+qNWOt0leXU3BLF9w=; b=IgMd4HGgtCasMB1IaMaYJMj8Pmrv0AVO5EXFFWfD601CTptG16Jk3Yxfe4TA9gB2ML Ug1wiKJ6ELdljW2OQphIa/wYTcdFy2olEU7trf8yl6zYPxKJOgHaHCowMdBZ2WKVyP0c g+D9LaIyjgVvIDPTPuUDLCjpi+5uBlH81FNTd0frkcbsQIXI/XFuxA4qJ2HqGpyz0OEf 2Jo7zsgzA1VLmjIv+o+0JJtNagiIiYPz+ytuprH8HzycyUN1oxhjqDw/gQbdNxZvERKg zPDCvg7c4ItT1AnVwhOPMO6GIVY/x9PaKGweK2wHQid8XZQVMm+J7QcfmZozv0ulIqSL brRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9qaQDr685zUJ24ISz4SmEC8SLh+qNWOt0leXU3BLF9w=; b=JqmLwJpJPRVenVfDT0RFZikwfnkPJcfLWGoFOKlwOV0wGdb5P8pr2l+bbeq3NP3DAF DMovhCUtI0DscX4+oRRUUJDE1Y52InJKmMbmHp18tJ2q5riHrz62jvbC6boyqqX0IM2d +/HHny9id1o/JOZmlmwo8qOqE/Vkyyw56cj5xcTOMGsFoPf3nUtXnhL2VSFWY/JVaMpW D/2KBWq6SpMQd04u1yaofSBfYM88tQ775AIPExkS84+JyrDWdec8iMadhFQed5a+CihI Xs2beyDtZ7NWpiSsaUwWFI7x33OBOQZZ71SNUVEvjd6OJNKyv4FbRhJBXLXJx/qvsNQX 2J/Q== X-Gm-Message-State: APf1xPCB5VrbIYjeksgDOetpZONsSeS6B5ZCOksW0cw69p8RV9vEUyrg g35CC9Y3K4clzxol+LWBu0xXQRN/RMTimuXsYjc= X-Google-Smtp-Source: AH8x2254XmBoI8KNDg0dBr2mohfuQI1M/saVOGfLmTQOBjaLHAjDLp5X3VKWNrY4M1Z7AVzBoX+ZTV5G0Jg/r0TPND4= X-Received: by 10.46.16.1 with SMTP id j1mr4214369lje.139.1518290511926; Sat, 10 Feb 2018 11:21:51 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Sat, 10 Feb 2018 11:21:50 -0800 (PST) In-Reply-To: <985b6d77-9f27-f6f4-ea0e-165951d91048@digiware.nl> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <985b6d77-9f27-f6f4-ea0e-165951d91048@digiware.nl> From: Alan Somers Date: Sat, 10 Feb 2018 12:21:50 -0700 X-Google-Sender-Auth: AU7nRwCQ-eMHhX5wJiGPenFa764 Message-ID: Subject: Re: posix_fallocate on ZFS To: Willem Jan Withagen Cc: freebsd current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 19:21:54 -0000 On Sat, Feb 10, 2018 at 11:50 AM, Willem Jan Withagen wrote: > On 10/02/2018 19:24, Alan Somers wrote: > >> On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > > wrote: >> >> Hi, >> >> This has been disabled on ZFS since last November. >> And I do understand the rationale on this. >> >> BUT >> >> I've now upgraded some of my HEAD Ceph test systems and they now >> fail, since Ceph uses posix_fallocate() to allocate space for the >> FileStore-journal. >> >> Is there any expectation that this is going to fixed in any near >> future? >> >> --WjW >> >> >> No. It's fundamentally impossible to support posix_fallocate on a COW >> filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, >> since the system call is merely advisory. >> > > Yup, that was what I'm going to do. > But then I would like to know how to annotate it. > > And I guess that I'd get reactions submitting code to fix this, since the > journal could run out of space. > So I'd beter know what is going on. > > I seem to remember that on a pool level is is possible to reserve space > whilest creating a filesystem? And then it could/should be fixed when > building the disk-infra for an OSD. > Yes, you can easily reserve space for an entire filesystem. Just do for example "zfs create -o reservation=64GB mypool/myfs" . From owner-freebsd-current@freebsd.org Sat Feb 10 19:43:31 2018 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 93960F180A4 for ; Sat, 10 Feb 2018 19:43:31 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1EF3A6E7E0 for ; Sat, 10 Feb 2018 19:43:30 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: a61cd9d8-0e9a-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id a61cd9d8-0e9a-11e8-91c6-33ffc249f3e8; Sat, 10 Feb 2018 19:43:22 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1AJhJtc029993; Sat, 10 Feb 2018 12:43:19 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518291799.32585.228.camel@freebsd.org> Subject: Re: posix_fallocate on ZFS From: Ian Lepore To: Alan Somers , Willem Jan Withagen Cc: freebsd current Date: Sat, 10 Feb 2018 12:43:19 -0700 In-Reply-To: References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 19:43:31 -0000 On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: > On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > wrote: > > > > > Hi, > > > > This has been disabled on ZFS since last November. > > And I do understand the rationale on this. > > > > BUT > > > > I've now upgraded some of my HEAD Ceph test systems and they now fail, > > since Ceph uses posix_fallocate() to allocate space for the > > FileStore-journal. > > > > Is there any expectation that this is going to fixed in any near future? > > > > --WjW > > > No.  It's fundamentally impossible to support posix_fallocate on a COW > filesystem like ZFS.  Ceph should be taught to ignore an EINVAL result, > since the system call is merely advisory. > > -Alan Unfortunately, posix documents that the function returns EINVAL only due to bad input parameters, so ignoring that seems like a bad idea. Wouldn't it be better if we returned EOPNOTSUP if that's the actual situation?  That could be safely ignored. -- Ian From owner-freebsd-current@freebsd.org Sat Feb 10 19:45:27 2018 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 C9E1EF1830B for ; Sat, 10 Feb 2018 19:45:27 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 367E96EA8D; Sat, 10 Feb 2018 19:45:27 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id f137so15589670lfe.4; Sat, 10 Feb 2018 11:45:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ib1LkZ6SGdzWOee3q/uy4HBEYEpC3F3HSG1q8alkBzg=; b=t2Eyck9nUpQ7cowD+ljuK7a5KoH5W3+Fm0RdVdyDeYnlVyiCKXgMW8TChsAgAsD+gr oIKJ3iml9SEZPudjV8npO6tatlmSOJBrQxRCYH1BhqfT7cHQRIsdYPfytobON/8QZzf/ EFmMeelIHnIKIN8JpWuk1KmqNGmaBm0BEtLzIKkVk1YXn2YKgEkPdxReXMGFjRjPCRPr rs6Xnjx3z/vt+WAUNPIqZhVPTbWRlK00YZYROnT8mqU00B00dpHhwy/FjzxsxfvSwWLV IElvGGDhWAZwlJIEbW1rWJwyGQRqv2uOG8R8xOELBjeDIJUTp52lT4M8FTaKTQ0iigBx ckaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ib1LkZ6SGdzWOee3q/uy4HBEYEpC3F3HSG1q8alkBzg=; b=GI8VQtMLOYNJl7zJhzyiQjKBccqmpsIXpInmKzh4x1tHIAg77wSXksq5UrMPGpud1X kNro+cUWixL2+NSziSBOCYJgakPUQJnjMOJyR9RD+3sZr5q7s8zF28AxuYoRPNvZ9mQI dXLDWPNCFBA1iqcnCX4QZwiYoc7Zzg826UOl8rFjtPiK9+gMOU/idTAIbq688xuPO8YY 5sy6RiYuYagw8f7cwBgWpsIcv8rJVzavQFgBFbEw5a+Er9xNu3gnvfRa8sN/T5OgvPzO GG1c2ffqGL04fA1xCbBmcAbCVuC+1WlWYuFJSciyO5mgud0GdZJWCvo9qKuXF230lwXy 8F6A== X-Gm-Message-State: APf1xPALxuhErPbhBXwQtbOcFRatloxS5OftXKHrXDoeUbcDscqsSjpj OZCdwvr7bEDLV2txJ7DL99Oi19ooI7HS4DxRf9sjjQ== X-Google-Smtp-Source: AH8x224DIAtTHHQijfWJePGK4eb0FPp+eQQEWJfGMcGleztUe8DwRCCgV9yaPiQCUxdS1FAcKq7jl5bHLU2QDJeB6kg= X-Received: by 10.46.125.5 with SMTP id y5mr4629608ljc.89.1518291925117; Sat, 10 Feb 2018 11:45:25 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Sat, 10 Feb 2018 11:45:24 -0800 (PST) In-Reply-To: <1518291799.32585.228.camel@freebsd.org> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <1518291799.32585.228.camel@freebsd.org> From: Alan Somers Date: Sat, 10 Feb 2018 12:45:24 -0700 X-Google-Sender-Auth: fqUhsRMGCSoregwtiAmtLYlUb7s Message-ID: Subject: Re: posix_fallocate on ZFS To: Ian Lepore Cc: Willem Jan Withagen , freebsd current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 19:45:28 -0000 On Sat, Feb 10, 2018 at 12:43 PM, Ian Lepore wrote: > On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: > > On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > > wrote: > > > > > > > > Hi, > > > > > > This has been disabled on ZFS since last November. > > > And I do understand the rationale on this. > > > > > > BUT > > > > > > I've now upgraded some of my HEAD Ceph test systems and they now fail, > > > since Ceph uses posix_fallocate() to allocate space for the > > > FileStore-journal. > > > > > > Is there any expectation that this is going to fixed in any near > future? > > > > > > --WjW > > > > > No. It's fundamentally impossible to support posix_fallocate on a COW > > filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, > > since the system call is merely advisory. > > > > -Alan > > Unfortunately, posix documents that the function returns EINVAL only > due to bad input parameters, so ignoring that seems like a bad idea. > > Wouldn't it be better if we returned EOPNOTSUP if that's the actual > situation? That could be safely ignored. > I'm afraid you are mistaken. Posix _should've_ required EOPNOTSUP in this, but it actually requires EINVAL. http://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_fallocate.html From owner-freebsd-current@freebsd.org Sat Feb 10 19:47:55 2018 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 391C7F186D8 for ; Sat, 10 Feb 2018 19:47:55 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD93A6EC8D for ; Sat, 10 Feb 2018 19:47:54 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 4671ad4b-0e9b-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 4671ad4b-0e9b-11e8-91c6-33ffc249f3e8; Sat, 10 Feb 2018 19:47:51 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1AJlm4i030026; Sat, 10 Feb 2018 12:47:48 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518292068.32585.230.camel@freebsd.org> Subject: Re: posix_fallocate on ZFS From: Ian Lepore To: Alan Somers Cc: Willem Jan Withagen , freebsd current Date: Sat, 10 Feb 2018 12:47:48 -0700 In-Reply-To: References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <1518291799.32585.228.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 19:47:55 -0000 On Sat, 2018-02-10 at 12:45 -0700, Alan Somers wrote: > On Sat, Feb 10, 2018 at 12:43 PM, Ian Lepore wrote: > > > > > On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: > > > > > > On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > This has been disabled on ZFS since last November. > > > > And I do understand the rationale on this. > > > > > > > > BUT > > > > > > > > I've now upgraded some of my HEAD Ceph test systems and they now fail, > > > > since Ceph uses posix_fallocate() to allocate space for the > > > > FileStore-journal. > > > > > > > > Is there any expectation that this is going to fixed in any near > > future? > > > > > > > > > > > > > > > --WjW > > > > > > > No.  It's fundamentally impossible to support posix_fallocate on a COW > > > filesystem like ZFS.  Ceph should be taught to ignore an EINVAL result, > > > since the system call is merely advisory. > > > > > > -Alan > > Unfortunately, posix documents that the function returns EINVAL only > > due to bad input parameters, so ignoring that seems like a bad idea. > > > > Wouldn't it be better if we returned EOPNOTSUP if that's the actual > > situation?  That could be safely ignored. > > > I'm afraid you are mistaken.  Posix _should've_ required EOPNOTSUP in this, > but it actually requires EINVAL. > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_fallocate.html Oops, I apparently was looking at the prior version of the spec.  Nevermind. :) -- Ian From owner-freebsd-current@freebsd.org Sat Feb 10 22:50:03 2018 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 DE08DF03A4C for ; Sat, 10 Feb 2018 22:50:03 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 7B6A176EE7; Sat, 10 Feb 2018 22:50:03 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 607A32E860; Sat, 10 Feb 2018 23:50:01 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyQqeP5WnX3k; Sat, 10 Feb 2018 23:50:00 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id B108C2E85E; Sat, 10 Feb 2018 23:50:00 +0100 (CET) Subject: Re: posix_fallocate on ZFS To: Ian Lepore , Alan Somers Cc: freebsd current References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <1518291799.32585.228.camel@freebsd.org> From: Willem Jan Withagen Message-ID: <4fa8de06-c7a0-5585-4fa7-5bf59b99d627@digiware.nl> Date: Sat, 10 Feb 2018 23:50:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1518291799.32585.228.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 22:50:04 -0000 On 10/02/2018 20:43, Ian Lepore wrote: > On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: >> On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen >> wrote: >> >>> >>> Hi, >>> >>> This has been disabled on ZFS since last November. >>> And I do understand the rationale on this. >>> >>> BUT >>> >>> I've now upgraded some of my HEAD Ceph test systems and they now fail, >>> since Ceph uses posix_fallocate() to allocate space for the >>> FileStore-journal. >>> >>> Is there any expectation that this is going to fixed in any near future? >>> >>> --WjW >>> >> No.  It's fundamentally impossible to support posix_fallocate on a COW >> filesystem like ZFS.  Ceph should be taught to ignore an EINVAL result, >> since the system call is merely advisory. >> >> -Alan > > Unfortunately, posix documents that the function returns EINVAL only > due to bad input parameters, so ignoring that seems like a bad idea. > > Wouldn't it be better if we returned EOPNOTSUP if that's the actual > situation?  That could be safely ignored. I would probably help in my situation.... And I've been looking at the manpage, but cannot seem to find any indication that EINVAL is returned on running it on FreeBSD. --WjW From owner-freebsd-current@freebsd.org Sat Feb 10 23:10:48 2018 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 DB84DF0523E for ; Sat, 10 Feb 2018 23:10:47 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E03A77D49; Sat, 10 Feb 2018 23:10:47 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id h78so8717329lfg.6; Sat, 10 Feb 2018 15:10:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6WjHk9gKH4eEXlhf/G4HJ2zeTsk67kDgnNTOLGH2bDQ=; b=rk3hU66uZxzH8FO1dLdH0MXUncNlsT/7XC8KzUQgbqiKPAba/BJMryAvByNZ9fH1Mu jUsulo0ZyUSIY+rVBdU+vXhtvVAXb4ba8RpFVke6KHmKmSPSgKArTP0aT0uobbofVQjR 26SWQ0sZyHCzKy1TsA4KQ/g7CDpCjYz7WmijKfhWFYhHejUj9gRkMLoTXsHnLWHkedT7 mGokO9cBl9zT5egGaKyv/qCVTezLfHECTaKN1RYzlvsc4zWRyiefmxjWO6I/W6PSOYLH Hp2sozDbKl0lOnsZ1uH38HzOkz7ygdg3Lo3TjlNtSE74vbHcn91NANkLHpKAV64xTS5d ZW+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6WjHk9gKH4eEXlhf/G4HJ2zeTsk67kDgnNTOLGH2bDQ=; b=RrAl5NLIMHhJ47uKhyJ1SgQzrHr15oO7m6FGvnEQiS6kh+3LhobWtrChXcHHHajSrY g8Pb6hnr1DHWelBiB030eEycZ05PMgy8glSRN8IVrQR6MGN+BwkavRfHOYbSNz0hIooX b2zY3NhYRlA7FwKKGfwSTMl7gjxNc8eUSihaz3xhK3Az3iHmmFBnZWBwDartDcx2e4Of fGWxH3SjGd6QgQW7Ubv5hrTObV4m3yp7Zk6x9li/bLEVjIU4HKglA7w+U6CzyiW054GL KVM9hBmtdcUYoLmUrN34zPTRYs1qg+BJaaOSlzUbroHKyfko0czGq1xpST8qvL6P/VN2 Pq7Q== X-Gm-Message-State: APf1xPAyfAPQJ7UcOaNdN7l6yJxoypEL3jwxa++OEnsGuCqTs0idKEbF gCYL8peKVEDTpXgq/eZiOcnxUTzxVNvQmsYiZ/exCQ== X-Google-Smtp-Source: AH8x227iQFn152RHW9G9db5m6Qs5AE4qEqbUXx96lx7lYqLGaVhnEkSUdmhjRyJIB4R1/o7E1P+jnR6AWTRAENRRCzA= X-Received: by 10.46.22.30 with SMTP id w30mr4391627ljd.91.1518304245529; Sat, 10 Feb 2018 15:10:45 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Sat, 10 Feb 2018 15:10:44 -0800 (PST) In-Reply-To: <4fa8de06-c7a0-5585-4fa7-5bf59b99d627@digiware.nl> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <1518291799.32585.228.camel@freebsd.org> <4fa8de06-c7a0-5585-4fa7-5bf59b99d627@digiware.nl> From: Alan Somers Date: Sat, 10 Feb 2018 16:10:44 -0700 X-Google-Sender-Auth: kEQv74y7qryye-snDCVd_E3D5p0 Message-ID: Subject: Re: posix_fallocate on ZFS To: Willem Jan Withagen Cc: Ian Lepore , freebsd current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 23:10:48 -0000 On Sat, Feb 10, 2018 at 3:50 PM, Willem Jan Withagen wrote: > On 10/02/2018 20:43, Ian Lepore wrote: > >> On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: >> >>> On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen >>> wrote: >>> >>> >>>> Hi, >>>> >>>> This has been disabled on ZFS since last November. >>>> And I do understand the rationale on this. >>>> >>>> BUT >>>> >>>> I've now upgraded some of my HEAD Ceph test systems and they now fail, >>>> since Ceph uses posix_fallocate() to allocate space for the >>>> FileStore-journal. >>>> >>>> Is there any expectation that this is going to fixed in any near future? >>>> >>>> --WjW >>>> >>>> No. It's fundamentally impossible to support posix_fallocate on a COW >>> filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, >>> since the system call is merely advisory. >>> >>> -Alan >>> >> >> Unfortunately, posix documents that the function returns EINVAL only >> due to bad input parameters, so ignoring that seems like a bad idea. >> >> Wouldn't it be better if we returned EOPNOTSUP if that's the actual >> situation? That could be safely ignored. >> > > I would probably help in my situation.... > > And I've been looking at the manpage, but cannot seem to find any > indication that EINVAL is returned on running it on FreeBSD. > It's in the manpage, but only on head. It hasn't been in any stable release yet. https://svnweb.freebsd.org/base/head/lib/libc/sys/posix_fallocate.2?revision=325422&view=markup#l112 From owner-freebsd-current@freebsd.org Sat Feb 10 23:20:23 2018 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 B32EDF05DE2 for ; Sat, 10 Feb 2018 23:20:23 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 51E977851C; Sat, 10 Feb 2018 23:20:23 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 2CD6E2EB80; Sun, 11 Feb 2018 00:20:21 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6cz0TGT_a3Yz; Sun, 11 Feb 2018 00:20:20 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 8FC9F2EB7F; Sun, 11 Feb 2018 00:20:20 +0100 (CET) Subject: Re: posix_fallocate on ZFS To: Alan Somers Cc: Ian Lepore , freebsd current References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <1518291799.32585.228.camel@freebsd.org> <4fa8de06-c7a0-5585-4fa7-5bf59b99d627@digiware.nl> From: Willem Jan Withagen Message-ID: Date: Sun, 11 Feb 2018 00:20:20 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 10 Feb 2018 23:20:23 -0000 On 11/02/2018 00:10, Alan Somers wrote: > On Sat, Feb 10, 2018 at 3:50 PM, Willem Jan Withagen > wrote: > > On 10/02/2018 20:43, Ian Lepore wrote: > > On Sat, 2018-02-10 at 11:24 -0700, Alan Somers wrote: > > On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > wrote: > > > Hi, > > This has been disabled on ZFS since last November. > And I do understand the rationale on this. > > BUT > > I've now upgraded some of my HEAD Ceph test systems and > they now fail, > since Ceph uses posix_fallocate() to allocate space for the > FileStore-journal. > > Is there any expectation that this is going to fixed in > any near future? > > --WjW > > No.  It's fundamentally impossible to support > posix_fallocate on a COW > filesystem like ZFS.  Ceph should be taught to ignore an > EINVAL result, > since the system call is merely advisory. > > -Alan > > > Unfortunately, posix documents that the function returns EINVAL only > due to bad input parameters, so ignoring that seems like a bad idea. > > Wouldn't it be better if we returned EOPNOTSUP if that's the actual > situation?  That could be safely ignored. > > > I would probably help in my situation.... > > And I've been looking at the manpage, but cannot seem to find any > indication that EINVAL is returned on running it on FreeBSD. > > > It's in the manpage, but only on head.  It hasn't been in any stable > release yet. > https://svnweb.freebsd.org/base/head/lib/libc/sys/posix_fallocate.2?revision=325422&view=markup#l112 Right, it is. And it is even in the man-page were I looked. :( Just plainly read over it. To be honest I would expect it to have a bit more proza in the header of the manpage. Because it is rather significant that it does not work on certain FSes. And not just hide this in a single line in the explanation of an error value... --WjW