From owner-freebsd-hackers@freebsd.org Sun Mar 14 00:02:03 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C876568152 for ; Sun, 14 Mar 2021 00:02:03 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DyfqZ1c0kz3rfM for ; Sun, 14 Mar 2021 00:02:01 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id 12E01px8014402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 14 Mar 2021 00:01:53 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: johannes@jo-t.de Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.16.1/8.16.1) with ESMTPS id 12E01ir1073348 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sun, 14 Mar 2021 07:01:44 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Kernel dump during boot To: Johannes Totz , freebsd-hackers@freebsd.org References: From: Eugene Grosbein Message-ID: Date: Sun, 14 Mar 2021 07:01:39 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, NICE_REPLY_A,SPF_HELO_NONE,T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 T_SPF_PERMERROR SPF: test of record failed (permerror) * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * 2.6 LOCAL_FROM From my domains * -0.0 NICE_REPLY_A Looks like a legit reply (A) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 4DyfqZ1c0kz3rfM X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=fail (mx1.freebsd.org: domain of eugen@grosbein.net does not designate 2a01:4f8:c2c:26d8::2 as permitted sender) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-2.10 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_FAIL(1.00)[-all]; FREEFALL_USER(0.00)[eugen]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grosbein.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:c2c:26d8::2:from]; SPAMHAUS_ZRD(0.00)[2a01:4f8:c2c:26d8::2:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2021 00:02:03 -0000 13.03.2021 23:35, Johannes Totz wrote: > Hey everyone, > > is there a way to dump the kernel from DDB? Try this: call doadump > I've got a panic during boot, before init is started but after geom and friends are up. So dumpdev hasnt been set yet. > Can I hardcode it somewhere? Setting kern.shutdown.dumpdevname in loader.conf doesn't seem to work. It should work. It worked for me in 11.4. For example: dumpdev="/dev/label/swap" Later, in multiuser: $ sysctl kern.shutdown.dumpdevname kern.shutdown.dumpdevname: label/swap From owner-freebsd-hackers@freebsd.org Sun Mar 14 00:41:05 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AB90456AE94 for ; Sun, 14 Mar 2021 00:41:05 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane-mx.org) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dyghc4Cxtz3vsj for ; Sun, 14 Mar 2021 00:41:04 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane-mx.org) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1lLEoX-0004Ek-Om for freebsd-hackers@freebsd.org; Sun, 14 Mar 2021 01:41:01 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Johannes Totz Subject: Re: Kernel dump during boot Date: Sun, 14 Mar 2021 00:40:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 In-Reply-To: Content-Language: en-GB X-Rspamd-Queue-Id: 4Dyghc4Cxtz3vsj X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=jo-t.de (policy=none); spf=pass (mx1.freebsd.org: domain of freebsd-hackers@m.gmane-mx.org designates 116.202.254.214 as permitted sender) smtp.mailfrom=freebsd-hackers@m.gmane-mx.org X-Spamd-Result: default: False [0.10 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[jo-t.de : SPF not aligned (relaxed), No valid DKIM,none]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[116.202.254.214:from]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[116.202.254.214:from:127.0.2.255]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[johannes@jo-t.de,freebsd-hackers@m.gmane-mx.org]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:116.202.0.0/16, country:DE]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; FROM_NEQ_ENVFROM(0.00)[johannes@jo-t.de,freebsd-hackers@m.gmane-mx.org]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2021 00:41:05 -0000 On 14/03/2021 00:01, Eugene Grosbein wrote: > 13.03.2021 23:35, Johannes Totz wrote: > >> Hey everyone, >> >> is there a way to dump the kernel from DDB? > > Try this: > > call doadump > >> I've got a panic during boot, before init is started but after geom and friends are up. So dumpdev hasnt been set yet. >> Can I hardcode it somewhere? Setting kern.shutdown.dumpdevname in loader.conf doesn't seem to work. > > It should work. It worked for me in 11.4. For example: > > dumpdev="/dev/label/swap" > > Later, in multiuser: > > $ sysctl kern.shutdown.dumpdevname > kern.shutdown.dumpdevname: label/swap Ah yes, a simple dumpdev did the trick... (how did I miss that...) Thanks Eugene and Jordan (who replied off-list)! From owner-freebsd-hackers@freebsd.org Sun Mar 14 01:48:20 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7398D56DE97 for ; Sun, 14 Mar 2021 01:48:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DyjBD2wd4z4VRd; Sun, 14 Mar 2021 01:48:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id E1E039BDF; Sun, 14 Mar 2021 01:48:19 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sat, 13 Mar 2021 17:48:18 -0800 (PST) From: Don Lewis Subject: Re: problems building a release To: Mark Millard cc: freebsd-hackers In-Reply-To: Message-ID: References: <8CE18E0A-8931-4C41-83B4-D30EEC049E6D@yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2021 01:48:20 -0000 On 13 Mar, Mark Millard wrote: >> On 2021-Mar-13, at 12:43, Don Lewis wrote: >> >> On 13 Mar, Mark Millard wrote: >>> . . . >> >> Thanks. All of this stuff is pretty confusing. >> >> If I specify MAKE_CONF in release.conf, it does affect the target build. >> In particular MODULES_OVERRIDE does the right thing. >> >> It seems like there should be a way to specify a make.conf and src.conf >> so that they get included in the release so that if the release is >> installed and then world and kernel are built it reproduces itself. >> >> I did manage to unmute release.sh and make so that the build is verbose, >> but the error I get when I specify TARGET and TARGET_ARCH in the >> make.conf is still a mystery. There doesn't seem to be a line buffering >> problem hiding things, this was captured from the terminal window with >> no redirections involved. >> >> ===> etc (installconfig) >> mkdir -p bootonly/usr/freebsd-dist >> cp MANIFEST bootonly/usr/freebsd-dist >> ln -fs /tmp/bsdinstall_etc/resolv.conf bootonly/etc/resolv.conf >> echo sendmail_enable=\"NONE\" > bootonly/etc/rc.conf >> echo hostid_enable=\"NO\" >> bootonly/etc/rc.conf >> echo debug.witness.trace=0 >> bootonly/etc/sysctl.conf >> echo vfs.mountroot.timeout=\"10\" >> bootonly/boot/loader.conf >> echo kernels_autodetect=\"NO\" >> bootonly/boot/loader.conf >> cp /usr/src/release/rc.local bootonly/etc >> sh /usr/src/release/i386/mkisoimages.sh -b 14_0_CURRENT_i386_BO bootonly.iso bootonly >> sh /usr/src/release/i386/make-memstick.sh disc1 memstick.img >> Calculated size of `memstick.img.part': 624754688 bytes, 13074 inodes >> Extent size set to 32768 >> memstick.img.part: 595.8MB (1220224 sectors) block size 32768, fragment size 4096 >> using 1 cylinder groups of 595.81MB, 19066 blks, 13952 inodes. >> super-block backups (for fsck -b #) at: >> 192, >> Populating `memstick.img.part' >> Image `memstick.img.part' complete >> sh /usr/src/release/i386/make-memstick.sh bootonly mini-memstick.img >> Calculated size of `mini-memstick.img.part': 237436928 bytes, 13069 inodes >> Extent size set to 32768 >> mini-memstick.img.part: 226.4MB (463744 sectors) block size 32768, fragment size 4096 >> using 1 cylinder groups of 226.44MB, 7246 blks, 14592 inodes. >> super-block backups (for fsck -b #) at: >> 192, >> Populating `mini-memstick.img.part' >> Image `mini-memstick.img.part' complete > > The below notes are about what starts here: > >> make -C /usr/src/release release-done >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >> Abort trap >> touch release >> true > > That is interesting as this turns out to be a fairly > simple context by the time that "make . . . release-done" > is echoed: > > QUOTE > release: real-release vm-release cloudware-release > ${MAKE} -C ${.CURDIR} ${.MAKEFLAGS} release-done > true > > release-done: > touch release > END QUOTE > > but by then "real-release vm-release cloudware-release" > completed and we see the touch and true after the messages. > > So it looks like the 6 "not found" messages are from > make's internal activities. > > It would be interesting to get a truss -f log (or some such) > of that "${MAKE} . . . release-done" out into to a file. > There should not be much other activity in the file generated. > That might expose the activity producing the "not found" > messages. > > Also interesting might be adding a "file /libexec/ld-elf.so.1" > command line to release: or adding other such context reporting > there, such as "uname -apKU" . scratch/libexec/ld-elf.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, for FreeBSD 14.0 (1400005), stripped Mystery solved. I ran "make -C /usr/src/release release-done" under the chroot with a bunch of debug flags. All of the errors were associated with references to GIT* make variables. Those are defined as as: Makefile.inc1:GITBRANCH!= ${GIT_CMD} -C ${.CURDIR} rev-parse --abbrev-ref HEAD 2>/dev/null | sed -e 's/\^\///' Makefile.inc1:GITREV!= ${GIT_CMD} -C ${.CURDIR} rev-parse --verify --short HEAD 2>/dev/null || true Makefile.inc1:GITCOUNT!= ${GIT_CMD} -C ${.CURDIR} rev-list --count HEAD 2>/dev/null || true so every reference would try to run git because of make's lazy variable evaluation. The installed version of git is an amd64 executable left over from earlier experiments. From owner-freebsd-hackers@freebsd.org Sun Mar 14 04:31:56 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 86E1B570AC7 for ; Sun, 14 Mar 2021 04:31:56 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dymq03Wq3z4dMS; Sun, 14 Mar 2021 04:31:56 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id E3B3AAD4A; Sun, 14 Mar 2021 04:23:08 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sat, 13 Mar 2021 20:23:06 -0800 (PST) From: Don Lewis Subject: Re: problems building a release To: Mark Millard cc: freebsd-hackers In-Reply-To: Message-ID: References: <8CE18E0A-8931-4C41-83B4-D30EEC049E6D@yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2021 04:31:56 -0000 On 13 Mar, Don Lewis wrote: > On 13 Mar, Mark Millard wrote: >>> On 2021-Mar-13, at 12:43, Don Lewis wrote: >>> >>> On 13 Mar, Mark Millard wrote: >>>> . . . >>> >>> Thanks. All of this stuff is pretty confusing. >>> >>> If I specify MAKE_CONF in release.conf, it does affect the target build. >>> In particular MODULES_OVERRIDE does the right thing. >>> >>> It seems like there should be a way to specify a make.conf and src.conf >>> so that they get included in the release so that if the release is >>> installed and then world and kernel are built it reproduces itself. >>> >>> I did manage to unmute release.sh and make so that the build is verbose, >>> but the error I get when I specify TARGET and TARGET_ARCH in the >>> make.conf is still a mystery. There doesn't seem to be a line buffering >>> problem hiding things, this was captured from the terminal window with >>> no redirections involved. >>> >>> ===> etc (installconfig) >>> mkdir -p bootonly/usr/freebsd-dist >>> cp MANIFEST bootonly/usr/freebsd-dist >>> ln -fs /tmp/bsdinstall_etc/resolv.conf bootonly/etc/resolv.conf >>> echo sendmail_enable=\"NONE\" > bootonly/etc/rc.conf >>> echo hostid_enable=\"NO\" >> bootonly/etc/rc.conf >>> echo debug.witness.trace=0 >> bootonly/etc/sysctl.conf >>> echo vfs.mountroot.timeout=\"10\" >> bootonly/boot/loader.conf >>> echo kernels_autodetect=\"NO\" >> bootonly/boot/loader.conf >>> cp /usr/src/release/rc.local bootonly/etc >>> sh /usr/src/release/i386/mkisoimages.sh -b 14_0_CURRENT_i386_BO bootonly.iso bootonly >>> sh /usr/src/release/i386/make-memstick.sh disc1 memstick.img >>> Calculated size of `memstick.img.part': 624754688 bytes, 13074 inodes >>> Extent size set to 32768 >>> memstick.img.part: 595.8MB (1220224 sectors) block size 32768, fragment size 4096 >>> using 1 cylinder groups of 595.81MB, 19066 blks, 13952 inodes. >>> super-block backups (for fsck -b #) at: >>> 192, >>> Populating `memstick.img.part' >>> Image `memstick.img.part' complete >>> sh /usr/src/release/i386/make-memstick.sh bootonly mini-memstick.img >>> Calculated size of `mini-memstick.img.part': 237436928 bytes, 13069 inodes >>> Extent size set to 32768 >>> mini-memstick.img.part: 226.4MB (463744 sectors) block size 32768, fragment size 4096 >>> using 1 cylinder groups of 226.44MB, 7246 blks, 14592 inodes. >>> super-block backups (for fsck -b #) at: >>> 192, >>> Populating `mini-memstick.img.part' >>> Image `mini-memstick.img.part' complete >> >> The below notes are about what starts here: >> >>> make -C /usr/src/release release-done >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> ELF interpreter /libexec/ld-elf.so.1 not found, error 8 >>> Abort trap >>> touch release >>> true >> >> That is interesting as this turns out to be a fairly >> simple context by the time that "make . . . release-done" >> is echoed: >> >> QUOTE >> release: real-release vm-release cloudware-release >> ${MAKE} -C ${.CURDIR} ${.MAKEFLAGS} release-done >> true >> >> release-done: >> touch release >> END QUOTE >> >> but by then "real-release vm-release cloudware-release" >> completed and we see the touch and true after the messages. >> >> So it looks like the 6 "not found" messages are from >> make's internal activities. >> >> It would be interesting to get a truss -f log (or some such) >> of that "${MAKE} . . . release-done" out into to a file. >> There should not be much other activity in the file generated. >> That might expose the activity producing the "not found" >> messages. >> >> Also interesting might be adding a "file /libexec/ld-elf.so.1" >> command line to release: or adding other such context reporting >> there, such as "uname -apKU" . > > scratch/libexec/ld-elf.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, for FreeBSD 14.0 (1400005), stripped > > > Mystery solved. I ran "make -C /usr/src/release release-done" under > the chroot with a bunch of debug flags. All of the errors were > associated with references to GIT* make variables. Those are defined as > as: > > Makefile.inc1:GITBRANCH!= ${GIT_CMD} -C ${.CURDIR} rev-parse --abbrev-ref HEAD 2>/dev/null | sed -e 's/\^\///' > Makefile.inc1:GITREV!= ${GIT_CMD} -C ${.CURDIR} rev-parse --verify --short HEAD 2>/dev/null || true > Makefile.inc1:GITCOUNT!= ${GIT_CMD} -C ${.CURDIR} rev-list --count HEAD 2>/dev/null || true > > so every reference would try to run git because of make's lazy variable > evaluation. The installed version of git is an amd64 executable left > over from earlier experiments. When I cleaned out all the packages installed under /scratch, did a 'pkg-static bootstrap -f' and installed an i386 version of git, the errors went away. It doesn't look like I want to play with CHROOT_MAKEENV since I don't want to muck with the chroot. RELEASE(7) says: MAKE_CONF The make.conf(5) to use for the release build. Defaults to /dev/null to prevent polluting the release with local system changes. but it is clear that the TARGET and TARGET_ARCH settings there affect the chroot build. The settings of MAKE_CONF and SRC_CONF are stored in ${CONF_FILES}, which is included in CHROOT_*MAKEFLAGS as well as RELEASE_*MAKEFLAGS. The former should probably use the default /dev/null values. From owner-freebsd-hackers@freebsd.org Sun Mar 14 09:44:35 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4991F579F68 for ; Sun, 14 Mar 2021 09:44:35 +0000 (UTC) (envelope-from alx.manpages@gmail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dyvlk3t2Dz3KfD; Sun, 14 Mar 2021 09:44:34 +0000 (UTC) (envelope-from alx.manpages@gmail.com) Received: by mail-wm1-x330.google.com with SMTP id g20so6313838wmk.3; Sun, 14 Mar 2021 01:44:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=dewlM8ok+0vz7euretSLFHwtIdlMmbD+BlGNP+6IS3A=; b=Dctv70yT5IspbMlgPcSUSZBZdIg3Ff+d78kMStA4irU9eu6j4aGsTo4vlGUp1kAxTV BIfCGjZQ3eMohZY/aVBlBCf+xQbI8GHSYaTZkuW20OxjMnfTFBzmZBYCIC3Oy7nkYSLr 4vHkkVyidfyVPkf+w51tUYXcAMM26P09/N2a14AnW2mN9TUyWAk2tw0tY0nrJxpGl+pE jAhBL5VbWH+bL87CTrJS0YTWeEcxOU9J0t5C+U91FoWzRTM3lqzLTu6uctYrajswhXzf b0wrE0lXMRYWkq1nGhiy2mh5VdgxlbqX4EfxZXZuNPsBsdRSh2nBf2SuP4i86lVFMXHl w5tQ== 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=dewlM8ok+0vz7euretSLFHwtIdlMmbD+BlGNP+6IS3A=; b=Y0+Zz2hv4Qf67DThZLbCwMnOSC7YDwQIS7OKglUMXthY7aiVFY9Dy3G35pNWZukv5w JIsPxvp+wBSNrMnSv8BlEQgRUE0iVYk40a/u44QFPhlfrAL1WTh41luRIJnLmfyhP623 vAGC+iyoNQAoQDlfIz8iErd+tF9WvGBWKnR6mUZyBQnjqlfOBX/ZuSBFOG8b8Nrxzwat 4FgAsMnY7Qt4UkC9vxYMFCA6Fwsp8Yb38vfjS0AdfqiCpaKeA8Qc5v+//L6P3b4lJsuB qsSdbZRp0y+HxTueMeSTvL+BHtGjhrTumpHxFTTtTketDh8T23UxagxfydLVpUvXT3F8 fyyA== X-Gm-Message-State: AOAM532Na3fQ5RpcXVxVdPnS/sPZ6p5NEFlJ0avSKTYdRqgzmzwcZd0c TPccsJUctWeCs0BUVe6xckM= X-Google-Smtp-Source: ABdhPJztDiLeA2/pJWeUA3+1rM1hwn99ImO53gx4iN99arHbQ+NYYmrlCodepyJwF1tV5F6Sf6J/nQ== X-Received: by 2002:a05:600c:3515:: with SMTP id h21mr1615812wmq.9.1615715072721; Sun, 14 Mar 2021 01:44:32 -0800 (PST) Received: from [192.168.1.143] ([170.253.51.130]) by smtp.gmail.com with ESMTPSA id s18sm16830739wrr.27.2021.03.14.01.44.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 14 Mar 2021 01:44:32 -0800 (PST) Subject: Re: [PATCH v3 (resend)] tee: Add -q, --quiet, --silent option to not write to stdout To: Bernhard Voelker , Alex Henrie , Otto Moerbeek , Coreutils Cc: Fabrice BAUZAC , juli@clockworksquid.com, Jeffrey Walton , freebsd-hackers@freebsd.org, William Ahern , Roman Czyborra , oshogbo@freebsd.org, tech@openbsd.org, Christian Groessler , linux-api@vger.kernel.org, Michael Kerrisk , ed@nuxi.nl, Eric Pruitt References: <1f8ce444-35e2-56a7-dbd1-34e885372b11@gmail.com> <20210124121845.38293-1-alx.manpages@gmail.com> From: "Alejandro Colomar (man-pages)" Message-ID: <48228481-c1b0-dcce-8598-4c88aedb2ef9@gmail.com> Date: Sun, 14 Mar 2021 10:44:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dyvlk3t2Dz3KfD X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Dctv70yT; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of alxmanpages@gmail.com designates 2a00:1450:4864:20::330 as permitted sender) smtp.mailfrom=alxmanpages@gmail.com X-Spamd-Result: default: False [-2.05 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.55)[-0.549]; FREEMAIL_TO(0.00)[bernhard-voelker.de,gmail.com,drijf.net,gnu.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::330:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[170.253.51.130:received]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::330:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWELVE(0.00)[17]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::330:from]; FREEMAIL_CC(0.00)[mykolab.com,clockworksquid.com,gmail.com,freebsd.org,25thandclement.com,czyborra.com,openbsd.org,groessler.org,vger.kernel.org,nuxi.nl]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; MAILMAN_DEST(0.00)[freebsd-hackers] X-Mailman-Approved-At: Sun, 14 Mar 2021 15:30:23 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2021 09:44:35 -0000 On 1/25/21 5:03 AM, Bernhard Voelker wrote: > OTOH I understand that there's a little gap in the tool landscape. > Astonishingly, there doesn't seem to exist a trivial tool to redirect > from standard input (or any other input file descriptor) to a file. > I wrote such a little tool in the attached: > > $ src/sink --help > Usage: src/sink [OPTION]... FILE > Copy input stream to FILE. > > Mandatory arguments to long options are mandatory for short options too. > > -a, --append append to the given FILE, do not overwrite > -c, --create ensure to create FILE, error if exists > -i, --input-stream=FD read from stream FD instead of standard input > > The default input stream number FD is 0, representing the standard input. > > This allows not only to copy data from standard input, but from any > file descriptor open for reading. It also allows control over > how the output file will be opened (e.g. with O_CREAT|E_EXCL). > > The OPs case would look like: > > echo 'foo' | sudo sink /etc/foo > or > echo 'foo' | sudo sink -a /etc/foo # append. > or > echo 'foo' | sudo sink -c /etc/foo # ensure creation of the file. > > I'm not sure if this will ever be considered for inclusion - > I just did it "for fun". ;-) > > Have a nice day, > Berny > By chance, I just found out that there is a tool very similar to 'sink' in moreutils [1]. It's called 'sponge'. [1]: So this feature already exists, and therefore I drop my patches. Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/ From owner-freebsd-hackers@freebsd.org Mon Mar 15 04:58:39 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D6C556F903 for ; Mon, 15 Mar 2021 04:58:39 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from mail.zx2c4.com (mail.zx2c4.com [104.131.123.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.zx2c4.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DzPML47Hlz3nZt for ; Mon, 15 Mar 2021 04:58:38 +0000 (UTC) (envelope-from Jason@zx2c4.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1615784315; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=gAcNUMSIfhqK6vHb1OSjRqLf1topuhqERhG9H/affLc=; b=o5oH+b9Ots45D95EubXqHyw0z1k6B6Yvz7v8B8nuzVoS8Ze+yWJIhP2yGudt0Rn4wlJAHL zoXp28JnUXGrlPAizh8CwJH2z/zdbDmApFr9TX5nM8rMyCTeHN/g/5PMEjpcZ1F2XUV9Bh eFs8Eza4pSfDem2UQFdw0Gtib3xV6/M= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 37f24670 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Mon, 15 Mar 2021 04:58:35 +0000 (UTC) Date: Sun, 14 Mar 2021 22:58:33 -0600 From: "Jason A. Donenfeld" To: freebsd-hackers@freebsd.org Subject: if_wg simd chapoly needs some love Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DzPML47Hlz3nZt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zx2c4.com header.s=20210105 header.b=o5oH+b9O; dmarc=pass (policy=none) header.from=zx2c4.com; spf=pass (mx1.freebsd.org: domain of Jason@zx2c4.com designates 104.131.123.232 as permitted sender) smtp.mailfrom=Jason@zx2c4.com X-Spamd-Result: default: False [-4.70 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zx2c4.com:s=20210105]; FREEFALL_USER(0.00)[Jason]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; ARC_NA(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[104.131.123.232:from]; DKIM_TRACE(0.00)[zx2c4.com:+]; DMARC_POLICY_ALLOW(-0.50)[zx2c4.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:104.131.64.0/18, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 04:58:39 -0000 Hi, Kyle, MattD, and I have just finished an excursion reworking if_wg (hopefully in time for 13.0, or maybe 13.1). I was shocked at how rough the code was that had been committed to the tree – things left unimplemented, cryptographic mistakes, security flaws, ominous comments. It was as though the thing was never finished and was committed to the tree in half-baked form. Oh well. We spent some time getting it into shape and now we’re in a (somewhat) better situation. One casualty in the process, however, was SIMD crypto. I removed 40,000 lines of hacked up code from Linux that wasn’t really wired up correctly and had a maze of insane Linux ifdefs, and I replaced those with 1,800 lines of boring C code in a file called “crypto.c”, whose safety and correctness I’m a whole lot more sure of. But the downside is that there’s no longer an AVX{,2,512} ChaCha20Poly1305 implementation hooked up to WireGuard. It’s still pretty fast, but it’s definitely not _as fast_. So this email is a call for help in wiring up some SIMD crypto properly. There are already a few implementations in the tree – in OpenSSL, in libsodium, and in BearSSL. The OpenSSL that’s inside /sys seems to have Andy Polyakov’s super fast implementations [3], which I like. It seems like just a little bit of plumbing is necessary to do this. Now, there are two categories of fixups that can be done. The first category is “two obvious places that will lead to massive measurable performance increases.” The second category is “other subtle places that are hard to get right, and won’t really make much of a difference.” The two obvious places that will lead to massive measurable performance increases are at [1] and [2]. These calls to chacha20poly1305_{encrypt,decrypt} are where the actual IP packets get encrypted and decrypted. If you change those calls instead to be to extrafast_chacha20poly1305_{encrypt,decrypt}, and maybe twiddle some FPU bits on the task where those run, then you’ll have scored a massive performance gain. The other subtle places that are hard to get right, and won’t really make much of a difference, would still be nice to replace with code properly in the crypto/ module, rather than in my crypto.c stopgap, but this work is *much less* urgent, and harder to get right. If you’re also interested in doing this, please at least shoot me an email or message on IRC so I can point to various pitfalls and weird things that might not be obvious when porting that code elsewhere. However, if you want to work on [1] and [2] today, I don’t think that will require much coordination or headscratching, and it’d make a big difference. There are really only a few small requirements for extrafast_chacha20poly1305_{encrypt,decrypt}: a) they shouldn’t need to allocate memory; b) they should be synchronous; c) there should be no overhead associated with changing the {en,de}cryption key used; d) they should handle 64-bit nonces. These requirements match what you can build out of the existing OpenSSL code I saw in the tree. It’s also possible you’ll want to bring in new code from elsewhere. Or maybe you have other ideas. But anyway, [1] and [2] should be easy functions to swap out. If you’re interested and have questions, let me know. I don’t (yet!) know a whole lot about the various facilities in the FreeBSD tree, but I know crypto implementation stuff and WireGuard stuff pretty decently, so I’m happy to jump in where you need. Regards, Jason [1] noise_remote_encrypt: https://cgit.freebsd.org/src/tree/sys/dev/if_wg/wg_noise.c?id=74ae3f3e33b810248da19004c58b3581cd367843#n582 [2] noise_remote_decrypt: https://cgit.freebsd.org/src/tree/sys/dev/if_wg/wg_noise.c?id=74ae3f3e33b810248da19004c58b3581cd367843#n638 [3] openssl avx implementations: https://cgit.freebsd.org/src/tree/sys/crypto/openssl/amd64?id=74ae3f3e33b810248da19004c58b3581cd367843 From owner-freebsd-hackers@freebsd.org Mon Mar 15 00:00:21 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4C7E05B732A; Mon, 15 Mar 2021 00:00:21 +0000 (UTC) (envelope-from owner-freebsd-quarterly-calls@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DzGl91145z3CST; Mon, 15 Mar 2021 00:00:21 +0000 (UTC) (envelope-from owner-freebsd-quarterly-calls@freebsd.org) Delivered-To: freebsd-quarterly-calls@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D5545B6D76; Mon, 15 Mar 2021 00:00:01 +0000 (UTC) (envelope-from debdrup@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DzGkn28Whz3CRm; Mon, 15 Mar 2021 00:00:01 +0000 (UTC) (envelope-from debdrup@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1615766401; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=A3jGHHAGVyHJpd5/OFlhsW61SGOXDeSRL15wvIQuh6s=; b=uPlNRqG/i03k3NirJXrUZQcg1E2skdZHUzKjOlkLXb+MhG4gEwUvv4j8yWGmlkbBxQXT4R lZwCScpHOqKlHit6Ue+rh5JF/7ywq4lZh/aRK3YDIkJXmQHf8a8W1Xl4v0TW4nMLJznzbx GkY0bfirrjYlxf+jqfk6xQMSeDLtfqu5DOVv48sWiut15vUQdpH4LL51s0Kpz8lypKS+Xd 1fbpVT5lMDq1d7RWjYIol0nref1rYytst2pkQoyvhjsYsB7Y6tWj4i/Unqp2pIDgUoR8pV SPH0jrYPgSPXiKcCqrHJ1Zd6rHLnrQKpZI42stBiCy7Ptg67+fqGsA6+zUyAlA== Received: by freefall.freebsd.org (Postfix, from userid 1471) id 3028B15C70; Mon, 15 Mar 2021 00:00:01 +0000 (UTC) To: freebsd-quarterly-calls@FreeBSD.org Subject: [2 WEEKS LEFT REMINDER] Call for 2021Q1 quarterly status reports Message-Id: <20210315000001.3028B15C70@freefall.freebsd.org> Date: Mon, 15 Mar 2021 00:00:01 +0000 (UTC) From: Daniel Ebdrup Jensen ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1615766401; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=A3jGHHAGVyHJpd5/OFlhsW61SGOXDeSRL15wvIQuh6s=; b=uz5PidQQV36VAapueAgyqvLYKxxx8qxQYSj8fxUd8WZ3ECNdQVPTyBGgCJvF8HX4Q1/Paf siC+S1aho487uhwQU0VBwk2J4HUqVT2KqZ9SUNTegawRsmCUQUVUEteM3Ui0KsiSDElJyE glDYNcc2aqoqlc2AYCjNeWvbxANuP+4fZvEbCHCdC9HGATcd7zqpDr4i9UgxQFtGso5UIB DGmESeX2PXdmQQ3rE22EGI1vxi2RnTkWtoKUj4BXN3IOjScgcbZpxZbPVOmVg1WCjCH4bV tDd0L2NQNF2uwDhzD9QbgqAV5caE8tKquub/nS0Knn9Ln35bXRIgpVyCpVdtNw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1615766401; a=rsa-sha256; cv=none; b=WdIY78i2duZRcWAHMrzXd2IOYKdxwO0Xjmo1Kt3SBxBZfBEsuyxo6fNrTD+l08H38idIg1 vCpAhkz3ll7AZFysXJ9C695o59dXb4P69vTPST1SjpNUV1195UZexFcAcncd6H7scQ+5U9 NGWPnehAdwaH6cIk2voIjJZorJO0mC0wd2WRTCC7XXxnVx2nKxekAcIzxPiog9OyRQwJ64 uruAUFhyKKA7AyjMW5CBvK5tFF1sLW/Nx9vn4+cbJYV2i43hZ+ZBms7bW8/a9hTlTl68px eM6KixZsbnnkPnRs/NGrTM8pOyIUhi+CQN/No7tUKmEPY6vIS15dvhjHc8/neA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: freebsd-quarterly-calls@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: owner-freebsd-quarterly-calls@freebsd.org Sender: owner-freebsd-quarterly-calls@freebsd.org X-Mailman-Approved-At: Mon, 15 Mar 2021 21:50:09 +0000 X-BeenThere: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 00:00:21 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is March, 30th 2021 for work done since the last round of Quarterly Reports: January 2021 - March 2021. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissions@FreeBSD.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2021Q1 reports! Thanks, Daniel Ebdrup Jensen (on behalf of quarterly@) _______________________________________________ freebsd-quarterly-calls@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls To unsubscribe, send any mail to "freebsd-quarterly-calls-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Mon Mar 15 17:42:50 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5EF1D5AA886 for ; Mon, 15 Mar 2021 17:42:50 +0000 (UTC) (envelope-from alexhenrie24@gmail.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DzkK54XXbz3h1K; Mon, 15 Mar 2021 17:42:49 +0000 (UTC) (envelope-from alexhenrie24@gmail.com) Received: by mail-lf1-x129.google.com with SMTP id u4so58248459lfs.0; Mon, 15 Mar 2021 10:42:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t9br/rn+NQflaMLsYItA6lA+2r86TI92WxzRjOD18sA=; b=pu/uaYHl6nqaImhbz35F0IwdgLow1IqdUyUz+5SAh3JCmkSkdzqMe+IRRB/5+PmYSM B+XS6RJvYd+lb9QeKYYYe0sZsLQntudB/eG3V+ybQK7xviWm+QIgwgO5rQlrG1Z94poT dQoOqtUqKsQhjTBejliC5gtZ9ucrIr4uGVucGvbZwGtDEGZhasLA/l3hRdQlqAjSai80 fJabJWfZXf7Spo+6IRVOBXQsJ080JyAN/c5UAjhl/xZ3Fz9OdKaSBWFrRmuurnYr7hn8 06RU/X2F5/pbwIQ7wm5rbVLK5JhbvBSogjMT3xRvH+iFreJbsZj1wSz2qL/M9zytEyDt +FaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t9br/rn+NQflaMLsYItA6lA+2r86TI92WxzRjOD18sA=; b=VodyZo1Z+Ez0d2ZsWqaIn9PUwv+lToS+d8TKoYmOR6iXiFHh9pVe3Jt3xoc/EJSpwQ PSRi3LKNgASRUagmS+RmA24ncHnMlsMNTbLohQPbNyfIC31W8g3Q5RgottKq51wfO5MA suIca/36M10Z6CVMxamc2eyljXP/3dlMYBpDZ0nVlUQ4+5b9STGrn+M3sr6IbNyPJkht cEOPKyTepRuDaY+/V97AlMWBd7onhcsG8UpZ6VR+H+Umt+tgBis2GU7B3TWWitXRgIib jAAVG2HqCa+9BXTiFb99EPozje6w+rDexWQ1Kftog93Jw0ckhCTAXTcTEp0/2MEWlXQK 4wdQ== X-Gm-Message-State: AOAM53083YbDdUxAf1Qrh9IT7LHbCxW1AOCWxh6yUgrbETv2esentArt UgwaTQueenWJHpA4P3WwSZkDdz4FEOj8LGG6Rio= X-Google-Smtp-Source: ABdhPJxyCU9tS9e6kUOOcX4DN0PBEqaLeBoAXzQRK5Ms3eGHZZKk77CITmiuG/PI9dhsqetxZEvHrbQ1Ql+hMqewk+A= X-Received: by 2002:a19:520b:: with SMTP id m11mr8446632lfb.42.1615830167987; Mon, 15 Mar 2021 10:42:47 -0700 (PDT) MIME-Version: 1.0 References: <1f8ce444-35e2-56a7-dbd1-34e885372b11@gmail.com> <20210124121845.38293-1-alx.manpages@gmail.com> <48228481-c1b0-dcce-8598-4c88aedb2ef9@gmail.com> In-Reply-To: <48228481-c1b0-dcce-8598-4c88aedb2ef9@gmail.com> From: Alex Henrie Date: Mon, 15 Mar 2021 11:42:36 -0600 Message-ID: Subject: Re: [PATCH v3 (resend)] tee: Add -q, --quiet, --silent option to not write to stdout To: "Alejandro Colomar (man-pages)" Cc: Bernhard Voelker , Otto Moerbeek , Coreutils , Fabrice BAUZAC , Juli Mallett , Jeffrey Walton , freebsd-hackers@freebsd.org, William Ahern , Roman Czyborra , oshogbo@freebsd.org, tech@openbsd.org, Christian Groessler , linux-api@vger.kernel.org, Michael Kerrisk , Ed Schouten , Eric Pruitt Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4DzkK54XXbz3h1K X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=pu/uaYHl; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of alexhenrie24@gmail.com designates 2a00:1450:4864:20::129 as permitted sender) smtp.mailfrom=alexhenrie24@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; MAILMAN_DEST(0.00)[freebsd-hackers]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::129:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::129:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWELVE(0.00)[17]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::129:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; FREEMAIL_CC(0.00)[bernhard-voelker.de, drijf.net, gnu.org, mykolab.com, clockworksquid.com, gmail.com, freebsd.org, 25thandclement.com, czyborra.com, openbsd.org, groessler.org, vger.kernel.org, nuxi.nl] X-Mailman-Approved-At: Tue, 16 Mar 2021 06:18:30 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 17:42:50 -0000 On Sun, Mar 14, 2021 at 3:44 AM Alejandro Colomar (man-pages) wrote: > > On 1/25/21 5:03 AM, Bernhard Voelker wrote: > > OTOH I understand that there's a little gap in the tool landscape. > > Astonishingly, there doesn't seem to exist a trivial tool to redirect > > from standard input (or any other input file descriptor) to a file. > > I wrote such a little tool in the attached: > > > > $ src/sink --help > > Usage: src/sink [OPTION]... FILE > > Copy input stream to FILE. > > > > Mandatory arguments to long options are mandatory for short options too. > > > > -a, --append append to the given FILE, do not overwrite > > -c, --create ensure to create FILE, error if exists > > -i, --input-stream=FD read from stream FD instead of standard input > > > > The default input stream number FD is 0, representing the standard input. > > > > This allows not only to copy data from standard input, but from any > > file descriptor open for reading. It also allows control over > > how the output file will be opened (e.g. with O_CREAT|E_EXCL). > > > > The OPs case would look like: > > > > echo 'foo' | sudo sink /etc/foo > > or > > echo 'foo' | sudo sink -a /etc/foo # append. > > or > > echo 'foo' | sudo sink -c /etc/foo # ensure creation of the file. > > > > I'm not sure if this will ever be considered for inclusion - > > I just did it "for fun". ;-) > > > > Have a nice day, > > Berny > > > > By chance, I just found out that there is a tool very similar to 'sink' > in moreutils [1]. It's called 'sponge'. > > [1]: > > So this feature already exists, and therefore I drop my patches. > > Cheers, > > Alex Interesting, thanks for sharing. There's still no `sponge -q` option though--it always writes either to a file or to standard output. -Alex From owner-freebsd-hackers@freebsd.org Mon Mar 15 20:20:55 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 38A3F5AE336 for ; Mon, 15 Mar 2021 20:20:55 +0000 (UTC) (envelope-from alexhenrie24@gmail.com) Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DznqV2xp9z3tHk; Mon, 15 Mar 2021 20:20:54 +0000 (UTC) (envelope-from alexhenrie24@gmail.com) Received: by mail-lf1-x12c.google.com with SMTP id v2so45875162lft.9; Mon, 15 Mar 2021 13:20:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5o+tdW+BV7Wm+7chs7B/caIMYJ3/SLZxEpYQvO4IUTw=; b=H9/XcVOnqaB+05V4nFAe/DIRo555bUX6rHMiUSrBpeFHqnIxjdztmQn8zbasu1KIfa /sVMt73yWhBLCK5XaOV7eIJAb7DiozjNFHfYwIm0DxTtT8ZL8diy4tNPVVF3UnBT9BbS 0lAbbGXQBGT5u/3lA7rSV8RD2zK5ui6tcA/zhS0I2/s7MMuLaw0Hp1xo6ObEvV5HI5I+ sgt0RoUUlzXr/HGBexmwX9YcnUWVzJDSSfAgFdW8A9SUuzJ1dj0lKR1r4iXObS+FQACX KSTDhDXaJGv0sqHMiwTSDuRmUqifUXPgBHyY5U/12dX8A9xE30xcNYWpF/7tOh+A8RCr szTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5o+tdW+BV7Wm+7chs7B/caIMYJ3/SLZxEpYQvO4IUTw=; b=CnsT39TfxP4wajvFZG4ZMnbqhUr2JIRBg3xRYNL8OStEfey1XSnjyTAQPCnEp3pTRS 2rqpXBtWDkqqE9RTYi+o6/6cAggKUGU0q2RjYo7dc+7ibljCp79f5L/RRlix9pdn7mCo o+hpMl/9N9XL0B6dXj4NCVhrmF8Tssk4C53Injqn4kBRhTFV3a3Y2e1XiP3Pi7y56id9 wEFocMGwRUl3QDcfaYuTQC69AWQcB/XI7J1ACc7DATc96l5pQYUULDqiSpEKQIp8LeuE OLCW9+BhVHDYhVGC2qplpqro3IbUAqUDA7PmdulNiHHmSTVQFow1BHRfueUa74xTtS96 yyWQ== X-Gm-Message-State: AOAM531si8IZUgJSyxl3Dl0O9iOdpXZnBW5WgsQxmRPPAZkRPc2OyAcL yRCg+eM/Y7Egt4Dg9VC3PfE79YYISof/d4YEYJA= X-Google-Smtp-Source: ABdhPJwvGVF19aniHTtSRwoAzpZgDayRD56HV3hWLx5di0gQKHCAoaGF5qNB4u1qHrAUpU3Fe5kmmxzFscM9V9bsgbA= X-Received: by 2002:a19:5213:: with SMTP id m19mr8835236lfb.203.1615839652612; Mon, 15 Mar 2021 13:20:52 -0700 (PDT) MIME-Version: 1.0 References: <1f8ce444-35e2-56a7-dbd1-34e885372b11@gmail.com> <20210124121845.38293-1-alx.manpages@gmail.com> <48228481-c1b0-dcce-8598-4c88aedb2ef9@gmail.com> In-Reply-To: From: Alex Henrie Date: Mon, 15 Mar 2021 14:20:40 -0600 Message-ID: Subject: Re: [PATCH v3 (resend)] tee: Add -q, --quiet, --silent option to not write to stdout To: "Alejandro Colomar (man-pages)" Cc: Bernhard Voelker , Otto Moerbeek , Coreutils , Fabrice BAUZAC , Juli Mallett , Jeffrey Walton , freebsd-hackers@freebsd.org, William Ahern , Roman Czyborra , oshogbo@freebsd.org, tech@openbsd.org, Christian Groessler , linux-api@vger.kernel.org, Michael Kerrisk , Ed Schouten , Eric Pruitt Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4DznqV2xp9z3tHk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=H9/XcVOn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of alexhenrie24@gmail.com designates 2a00:1450:4864:20::12c as permitted sender) smtp.mailfrom=alexhenrie24@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; MAILMAN_DEST(0.00)[freebsd-hackers]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::12c:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::12c:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWELVE(0.00)[17]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::12c:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; FREEMAIL_CC(0.00)[bernhard-voelker.de, drijf.net, gnu.org, mykolab.com, clockworksquid.com, gmail.com, freebsd.org, 25thandclement.com, czyborra.com, openbsd.org, groessler.org, vger.kernel.org, nuxi.nl] X-Mailman-Approved-At: Tue, 16 Mar 2021 06:19:11 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 20:20:55 -0000 On Mon, Mar 15, 2021 at 11:42 AM Alex Henrie wrote: > > On Sun, Mar 14, 2021 at 3:44 AM Alejandro Colomar (man-pages) > wrote: > > > > On 1/25/21 5:03 AM, Bernhard Voelker wrote: > > > OTOH I understand that there's a little gap in the tool landscape. > > > Astonishingly, there doesn't seem to exist a trivial tool to redirect > > > from standard input (or any other input file descriptor) to a file. > > > I wrote such a little tool in the attached: > > > > > > $ src/sink --help > > > Usage: src/sink [OPTION]... FILE > > > Copy input stream to FILE. > > > > > > Mandatory arguments to long options are mandatory for short options too. > > > > > > -a, --append append to the given FILE, do not overwrite > > > -c, --create ensure to create FILE, error if exists > > > -i, --input-stream=FD read from stream FD instead of standard input > > > > > > The default input stream number FD is 0, representing the standard input. > > > > > > This allows not only to copy data from standard input, but from any > > > file descriptor open for reading. It also allows control over > > > how the output file will be opened (e.g. with O_CREAT|E_EXCL). > > > > > > The OPs case would look like: > > > > > > echo 'foo' | sudo sink /etc/foo > > > or > > > echo 'foo' | sudo sink -a /etc/foo # append. > > > or > > > echo 'foo' | sudo sink -c /etc/foo # ensure creation of the file. > > > > > > I'm not sure if this will ever be considered for inclusion - > > > I just did it "for fun". ;-) > > > > > > Have a nice day, > > > Berny > > > > > > > By chance, I just found out that there is a tool very similar to 'sink' > > in moreutils [1]. It's called 'sponge'. > > > > [1]: > > > > So this feature already exists, and therefore I drop my patches. > > > > Cheers, > > > > Alex > > Interesting, thanks for sharing. There's still no `sponge -q` option > though--it always writes either to a file or to standard output. > > -Alex Actually, it looks like `pee` (also from moreutils) can be used for throwing input into the void. So between `sponge` and `pee`, I think all the use cases are covered! -Alex From owner-freebsd-hackers@freebsd.org Tue Mar 16 09:03:59 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DB19657D072 for ; Tue, 16 Mar 2021 09:03:59 +0000 (UTC) (envelope-from ionut.mihalache1506@gmail.com) Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F06lz1Lltz3m8d for ; Tue, 16 Mar 2021 09:03:59 +0000 (UTC) (envelope-from ionut.mihalache1506@gmail.com) Received: by mail-il1-x12c.google.com with SMTP id g9so12004550ilc.3 for ; Tue, 16 Mar 2021 02:03:58 -0700 (PDT) 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=UOtvqQAgHFK2Dyle7HtCTfo7/luqlmZtXkY/r+oif0g=; b=FdQvrE77OkcJ+FnEEKyxaGuMHsVfPT/CJjKzbujhTIxDr2GZm2IROIOh1RbqK5mdm3 HQyIQHFKIUZuWz3rChJAQYkaaa6M86Z5ky/n/QtjGzaCisr30dZ6ibsw+2wE1+FxUDXc 8cWs96mu9hdVlBo7VGwQg85Xyfol1CZ+1hrsYj4CRDbH+xdj/mniv1zusfGUTT2dCPkl p7GO8Y/ElSY9MZrjnTVaM3ytPBbkDotfT4u79u5NRIgHZzvlGD5FHqJYXIj4ouGaYbvu mu1xsZxg4QLFJSdI0tT3He9lK+gVjsESXf/D+t62rCGAmFMdBF2QBWzEXFEZnW5jRxmH 3Jaw== 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=UOtvqQAgHFK2Dyle7HtCTfo7/luqlmZtXkY/r+oif0g=; b=SpeIdnLPqKwVQVaMHHBfz2I5vPA8T+ILgJXa2x86KRR2qqcHKmtLFH4clZ368Q8rF/ zWZcJGXZS+pGX5GNJxNa3+woSV5jHsMpgZHqlSVq5rIMKgAx0VkGFHuZFniNLVupfv2z doJNDSOJikFS6P75V3iODImsuChnckETAHeFVj3o2DxU2oR2vGflxg1Ixr+C4E4ZlF1D 12DlQvfW+zzP5smZV+T3iD9RadOHxs7aAEdMK6FzVWj3yr1DIRAmC4bIfVB3k2FZQPfu PBX4pd/mY5vANTpsZv53p46E7KVnVZbRY21XT6aJ+elRZq0MSaI54o6pbDhlLR31zakZ dLfw== X-Gm-Message-State: AOAM531t1zXZtEMHrbETiL/Da4Us4W1UJwQMFPlw6tpDd4W2yXQmUCLd beMn1sjsAU9ahUl9ypFQKjBbPMpJyZ5Z65ckl1EcS84NpAY= X-Google-Smtp-Source: ABdhPJyNy1KbeF8ldl+cmZRWNsavR77GtLuqxbqNRnXNcJlIKwAYRYS96VtJwGyJcHVTE23lIyRrgfkOHwl8nRLrywk= X-Received: by 2002:a05:6e02:dce:: with SMTP id l14mr2944148ilj.102.1615885437997; Tue, 16 Mar 2021 02:03:57 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?Q?Ionu=C8=9B_Mihalache?= Date: Tue, 16 Mar 2021 07:03:47 -0200 Message-ID: Subject: UCL library bug To: freebsd-hackers@freebsd.org X-Rspamd-Queue-Id: 4F06lz1Lltz3m8d X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=FdQvrE77; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ionutmihalache1506@gmail.com designates 2607:f8b0:4864:20::12c as permitted sender) smtp.mailfrom=ionutmihalache1506@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_MIXED_CHARSET(1.00)[subject]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::12c:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::12c:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::12c:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 09:03:59 -0000 Hello, I am using the ucl library to write in a file 64bit values. The data type is uint64_t or int64_t; on write I use %lu or %ld regarding the type and everything works, on read on the other hand something weird seems to happen: I read using %ld only and for small value it works, for values like 18,374,686,479,671,672,848 the ucl type type is recognized as UCL_STRING instead of UCL_INT and I don't know why this is happening. Is there a bug in the library? Thank you, Ionut From owner-freebsd-hackers@freebsd.org Tue Mar 16 11:22:20 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 046BB5A92BF for ; Tue, 16 Mar 2021 11:22:20 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F09qZ3YSGz3wS8 for ; Tue, 16 Mar 2021 11:22:18 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id 12GBM4bY037273 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 16 Mar 2021 11:22:05 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: ionut.mihalache1506@gmail.com Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.16.1/8.16.1) with ESMTPS id 12GABEgw032097 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 16 Mar 2021 17:11:14 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: UCL library bug To: =?UTF-8?Q?Ionu=c8=9b_Mihalache?= , freebsd-hackers@freebsd.org References: From: Eugene Grosbein Message-ID: <2b96997e-40fb-f337-d94b-60c4f1a2f31e@grosbein.net> Date: Tue, 16 Mar 2021 17:11:07 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,CTE_8BIT_MISMATCH, LOCAL_FROM,NICE_REPLY_A,SPF_FAIL,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_FAIL SPF: sender does not match SPF record (fail) * [SPF failed: Please see http://www.openspf.org/Why?s=mfrom; id=eugen%40grosbein.net; ip=2a03%3A3100%3Ac%3A13%3A%3A5; r=hz.grosbein.net] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * 2.6 LOCAL_FROM From my domains * 1.0 CTE_8BIT_MISMATCH Header says 7bits but body disagrees * -0.0 NICE_REPLY_A Looks like a legit reply (A) X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 4F09qZ3YSGz3wS8 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=fail (mx1.freebsd.org: domain of eugen@grosbein.net does not designate 2a01:4f8:c2c:26d8::2 as permitted sender) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-1.05 / 15.00]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:c2c:26d8::2:from]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_SPF_FAIL(1.00)[-all]; FREEFALL_USER(0.00)[eugen]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_BAD_CTE_7BIT(1.05)[7bit,utf8]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grosbein.net]; SPAMHAUS_ZRD(0.00)[2a01:4f8:c2c:26d8::2:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 11:22:20 -0000 16.03.2021 16:03, Ionuț Mihalache wrote: > Hello, > > I am using the ucl library to write in a file 64bit values. The data type > is uint64_t or int64_t; on write I use %lu or %ld regarding the type and > everything works, on read on the other hand something weird seems to happen: > > I read using %ld only and for small value it works, for values like > 18,374,686,479,671,672,848 > the ucl type type is recognized as UCL_STRING instead of UCL_INT and I > don't know why this is happening. Is there a bug in the library? Does it help if you use %lld instead? Or maybe %jd ? From owner-freebsd-hackers@freebsd.org Tue Mar 16 16:49:10 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2EB2E5B4AE5; Tue, 16 Mar 2021 16:49:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0K4k0v0Yz4nbQ; Tue, 16 Mar 2021 16:49:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f52.google.com (mail-qv1-f52.google.com [209.85.219.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 0CD3E76DE; Tue, 16 Mar 2021 16:49:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f52.google.com with SMTP id l15so9844785qvl.4; Tue, 16 Mar 2021 09:49:10 -0700 (PDT) X-Gm-Message-State: AOAM5336BUCy+ANTqn3eYq34bB2695SlBERXsBJl201bh50jE1MQiFW8 4ezh3gOGtXQIsxeonttLR8Lx1TRKnMv43K4stDA= X-Google-Smtp-Source: ABdhPJzi34QeuuOVEse/PFA41MQ0sLEBCfcjPCZtF6MJIU4MAD2F43d8XcxVIJylISCEjKpVOi7ZU5MBwDx/aFIZSqM= X-Received: by 2002:ad4:51c1:: with SMTP id p1mr582860qvq.39.1615913349559; Tue, 16 Mar 2021 09:49:09 -0700 (PDT) MIME-Version: 1.0 From: Kyle Evans Date: Tue, 16 Mar 2021 11:48:56 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Removing WireGuard Support From FreeBSD Base To: freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 16:49:10 -0000 Hi, You may have recently noticed some chatter around the internet about FreeBSD's in-kernel WireGuard implementation, and the work we've done on it in the last week. You may have also noticed additional chatter afterwards with regards to the original implementation. I'd like to give some context and information with regards to the current situation, as well as provide some insight into the future as one of the developers involved. With regard to the original implementation, this will be my only commentary on the matter. I'm a developer, and I'm passionate about the work that I do- often to a fault. I've said some things that I regret; the accusations that Scott Long alluded to in an e-mail on FreeBSD mailing lists were indeed made by me, and his phrasing of what I said was much kinder than it could have been. These were mistakes, and I'm going to own that. However, my personal belief is that neither Netgate, pfSense, nor the original developer deserved the level of scorn and criticism that they've received in the past days from both the press and the community at large. In the next day or so, I will be committing a removal of all WireGuard related bits from our 'main' branch, including the work that I recently committed. It will be followed up by a removal of the implementation from stable/13, and we will seek appropriate approval to remove it from releng/13.0 as well. Please, do not be concerned by any of this; this is being done with mutual support from all parties. Did the original implementation have issues? Yes, it did. Are we certain that our new version -doesn't- have issues? I believe it doesn't, but it hasn't been through thorough enough review. We hacked on this for a week, and we all reviewed each others' work in the process. The problem is that this work, in particular, is a driver with fairly severe security implications. Review by "three developers working and beating on it" is not the higher bar that we should be holding this to. While I believed I was doing what's right for the community, it's become clear that what's right for the community is to take a step back and do this the right way. Note that we're not dropping this effort. We will continue iterating on this out-of-tree, and we will go through the proper review channels. Folks will be unhappy in the interim because we're removing it right now, but in the end we will have a better FreeBSD because of it. There will be a kernel module available in ports at some point, but not before it's ready. Moving forward, myself, members of Netgate, and members of the larger community *are* working together on strictly technical details. I urge anyone with an interest in reviewing the driver to also get in touch with me. Please, let's move forward as a community on this. Thank you, Kyle Evans From owner-freebsd-hackers@freebsd.org Tue Mar 16 17:30:27 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CB36D5B6616; Tue, 16 Mar 2021 17:30:27 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from mail.zx2c4.com (mail.zx2c4.com [104.131.123.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.zx2c4.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0L0M5Jxyz4rnt; Tue, 16 Mar 2021 17:30:27 +0000 (UTC) (envelope-from Jason@zx2c4.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1615915825; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8Wql75Z38d6yNM6r69wKmE/MYWRMTbeRnNhGgBKT7nM=; b=A6Eb3I+/qXEu/jpCGkI4PTjZFnGw2KGdlbf0sZ9kHFvz9D+kwFjJcSUDKPl6bDHFgv3IIh zFvFGTu69uMdnT13l2+0M/RLW/DTGF+CirBiuQGkrANd9LO7Ri8zjW0HQO+2WZEk67gZbE pM9NlFOmC3nH6GM/o6IWe8amyYCI6bE= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id c993a653 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Tue, 16 Mar 2021 17:30:25 +0000 (UTC) Received: by mail-yb1-f177.google.com with SMTP id h82so37596744ybc.13; Tue, 16 Mar 2021 10:30:25 -0700 (PDT) X-Gm-Message-State: AOAM533H8mvBxleCT29it9TyxcuxWx1hvS8t0JBAxc4tdd5mvGCI/RuF TmA/IAIwJyke3sGLFeRuhilCOz7otuaut+l+/BM= X-Google-Smtp-Source: ABdhPJwN7MNuNHax0zFW1DWekEcylejoa77+qtpE8iuS9EQjfWrdbqCePH/cC5IzdVuU02rBjvP6STFdhowug1s8yT0= X-Received: by 2002:a25:4d02:: with SMTP id a2mr7623914ybb.49.1615915824259; Tue, 16 Mar 2021 10:30:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Jason A. Donenfeld" Date: Tue, 16 Mar 2021 11:30:13 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: Kyle Evans Cc: freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4F0L0M5Jxyz4rnt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 17:30:27 -0000 Hi Kyle, I think what you describe is a great plan. I think everybody realizes at this point that the original code base from the original author never should have been merged. We went head first in trying to fix it in a week because we thought that was our only choice. But knowing now that we can simply remove it, and get back to coding it carefully and deliberately, is just a huge relief. So that's great. And while it's under development, we can have an out-of-tree repo for folks to test out intermediate snapshots and provide feedback, just like the WireGuard project has always done. In other words, we'll follow the tried and true formulation of: slow, careful coding + regular snapshots to receive testing and feedback. So, I'm quite happy there. And when it is ready, I'm confident it'll get a thorough review from FreeBSD core developers, which is terrific. More review ==> better code. I also want to thank you for your words about Netgate and the various parties involved. I think nobody wants animosity and tension, and I imagine your email has helped to calm the tone quite a bit. That's just the type of reset we need, so that we can get back to what we do best: writing and refining code. To others reading, with regards to actual project logistics, I think what I wrote in the original announcement still stands: we'll have instructions for module building and such online and we'll announce it here. And for developers interested, Kyle, MattD, and I have been coordinating code writing on IRC; if you'd like to join in, ping one of us there and we'll get you up to speed on repos and ssh keys whatnot. Regards, Jason From owner-freebsd-hackers@freebsd.org Tue Mar 16 17:38:14 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 44C145B67C5; Tue, 16 Mar 2021 17:38:14 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from mail.zx2c4.com (mail.zx2c4.com [104.131.123.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.zx2c4.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0L9L1NZ3z4sB4; Tue, 16 Mar 2021 17:38:14 +0000 (UTC) (envelope-from Jason@zx2c4.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1615916291; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0oGACFIL8J9SZamsqvs/X4H69lOZwPL2+iMeFK6MhcE=; b=U3OaT/czT4X0h5JSLTEeA5233hCkKp/L81RA06SAksefFKwouujUwmgm49X/j0npJ72idh nF71cIOzgE/24EIk93U7b9/Vu9cOe3mOQT2dYXt9DnxXYdHNxQdfFG6v7Tc3aB1+hSIV/k NlRQICD37KEVksvolRO/p/4ijUwLOx4= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id aa3de340 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Tue, 16 Mar 2021 17:38:11 +0000 (UTC) Received: by mail-yb1-f176.google.com with SMTP id 133so37700501ybd.5; Tue, 16 Mar 2021 10:38:11 -0700 (PDT) X-Gm-Message-State: AOAM532IDmvqj+eIrL2X3NPwGasnGAxXf0b4+qPjMohZNLEejH/fvd2S 0kV5uPfRvGFP2nBVF1tnHq7UMnIIQ2DB1HFFpaM= X-Google-Smtp-Source: ABdhPJxi6Gau0FW2aWBjmPa2EXeZj1hs6B3t0fqJoDRxJLyS+8ZCrqyEFQdLeEpMKWsTelmANlJarC3SMiZ/7Zs/l1Y= X-Received: by 2002:a25:1442:: with SMTP id 63mr13125ybu.123.1615916290654; Tue, 16 Mar 2021 10:38:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Jason A. Donenfeld" Date: Tue, 16 Mar 2021 11:37:59 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: Jeffrey Walton Cc: Kyle Evans , freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4F0L9L1NZ3z4sB4 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 17:38:14 -0000 Hi Jeffrey, On Tue, Mar 16, 2021 at 11:16 AM Jeffrey Walton wrote: > > In the next day or so, I will be committing a removal of all WireGuard > > related bits from our 'main' branch, including the work that I recently > > committed. It will be followed up by a removal of the implementation > > from stable/13, and we will seek appropriate approval to remove it > > from releng/13.0 as well. Please, do not be concerned by any of this; > > this is being done with mutual support from all parties. > > The thing I find unusual is, the move appears to lack technical > justification. The best I can tell, the reasons seem to be political. > But like I said, maybe my feeds are missing something... > > As a naive outsider, if you are going to yank it, then the technical > reasons for the action should be clearly enumerated. Everything else > is just chatter or noise. The move just looks like a bunch of bruised > egos and sour grapes. I'd just like to chime in and point out that although this is happening in a political context as you've pointed out, this is in my opinion the *best possible technical situation*, and the one I would have preferred in the beginning anyway if it were presented as a choice. Here's the technical background you asked for: - We found tons of issues with the original code base. - We spent a week rewriting that codebase. So here's the rationale: - Merging a week-old codebase into an operating system kernel is a bad idea. It's really not more complicated than that. I'm *sure* we'll find more things to fix. That's just the nature of it. And from a practical perspective, it's a lot easier for me, anyway, to casually push fixes as I code to a normal repo on git.zx2c4.com. When there's a lot of potential code churn, sometimes it's easiest to be able to move fast at first. When we get it to a place where we feel extra good about it, then we can do the full review process on what we've got, which has the added benefit of even more eyeballs and ways of looking at things. I think the code will benefit from this type of process. > Maybe a good middle ground would be to take the existing code and put > it in a Wireguard branch. Those who wish to keep Wireguard out of > FreeBSD mainline have done so. FreeBSD users who wish to use Wireguard > can build the Wireguard branch. And those who wish to improve > Wireguard have a working branch for patches. Later, the branch can be > re-merged back to master. We're actually going to do something like that already. We'll have it as an out-of-tree module, since it's fairly standalone anyway. And then when it's ready, we'll send that for merging back into the FreeBSD main branch. Also, from a technical perspective, dealing with out of tree modules on FreeBSD seems way, way easier than on Linux. There's not nearly as much API churn, as far as I can see. We probably can even offer prebuilts at some point for people who want to test out snapshots. So I'm really not very worried (at least at the moment; I'm still new to FreeBSD kernel development). Jason From owner-freebsd-hackers@freebsd.org Tue Mar 16 17:13:49 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7CA205B5F32; Tue, 16 Mar 2021 17:13:49 +0000 (UTC) (envelope-from noloader@gmail.com) Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0Kd92zJzz4qTr; Tue, 16 Mar 2021 17:13:49 +0000 (UTC) (envelope-from noloader@gmail.com) Received: by mail-io1-xd32.google.com with SMTP id k2so38028522ioh.5; Tue, 16 Mar 2021 10:13:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=LdTU8JNN19De/6YG0m9exoj67s4UkjHWivqTBVMyxSY=; b=lzupkKG+FvaRp0PjWDQE//WskdEXBwWGqjcfk0s3qNm0UhClL6rVvkKbYnbLuxwXbd gDhgWWnxI4uVg5n8zu6/s1wIen+WkfDRi7lOvwHuYFsVHtRw+KRv3cURfwdleRQ83Bhx 2TKY6MWBMA9WJg/OxsHWWwg4TRtSM19KAD/tYsvN159YiEtQex3UrpAAl8E0K19O+rVg XhGrHTNbF8dMfILdUwqqcHEDUD3/UoNG+fkzH1b9utonmDzBBehfXCzoUdD3MbVy1nxM ASvQLQfXvBd7Qs5LSU/5ZheMUcm6UPj8c6vmNxT+JgN1FNc2Vk7my1vW+/3/MnaWxAhN D8ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=LdTU8JNN19De/6YG0m9exoj67s4UkjHWivqTBVMyxSY=; b=AEzpK4atKHaU+zbederG490Wa0bO1/jn9g22xqopqyi4zRUXw7oOTBUbjgkt4QMV3Q VY81878N0tdV7Van0lvv7Ab/BC1+ESHpL1xV4eeT0EX3ExN+1J2/F2pk9184nnr2IUFa 7kMCiQi69Np/UzNHhAHXV7PHKpkzvlzFM+dcGu3jVqAEG8AKnGyh+IZaUW0wxrHRf6/r BadijlgDR7MA0+GCca8MUSQRBAR4c+E104iF63O6P6P8Khzj/IXJaOtZmE+ER6vhN81W WfuVpUaADmAmmCY0TEX22BcsRYMg3u0Rit+vASDDY8YrcZwz4JCfKyKYsd2i5IrNbumv wfgQ== X-Gm-Message-State: AOAM533WWmTyE3HRMF7fLOZOnvIcUAFCRfxo0VJrbnESnRxYi06suhA6 3lUEDzMQl388sirJRz53JdMU94bKnDIJWzPPuLlnHaIu3fxg6w== X-Google-Smtp-Source: ABdhPJxgZRgSO4zUBdqu3fymybt0U9uYN1cRmYhzSIgpDyYUk/THlqMVFC+AkJMlND6puMJWfIfum+GKTxRS9BPmCZY= X-Received: by 2002:a5d:8552:: with SMTP id b18mr4169939ios.124.1615914827889; Tue, 16 Mar 2021 10:13:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: noloader@gmail.com From: Jeffrey Walton Date: Tue, 16 Mar 2021 13:13:36 -0400 Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: Kyle Evans Cc: freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4F0Kd92zJzz4qTr X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Mailman-Approved-At: Tue, 16 Mar 2021 20:35:52 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 17:13:49 -0000 Hi Kyle, I'm going to top post because there's only two points to raise. Sorry about that. I don't have a dog in this fight, so take this with a grain of salt... > Netgate, pfSense, nor the original developer deserved the level of > scorn and criticism that they've received in the past days from both the > press and the community at large. I have not really seen any scorn or criticism by the press or community. But maybe my feeds are missing something... > In the next day or so, I will be committing a removal of all WireGuard > related bits from our 'main' branch, including the work that I recently > committed. It will be followed up by a removal of the implementation > from stable/13, and we will seek appropriate approval to remove it > from releng/13.0 as well. Please, do not be concerned by any of this; > this is being done with mutual support from all parties. The thing I find unusual is, the move appears to lack technical justification. The best I can tell, the reasons seem to be political. But like I said, maybe my feeds are missing something... As a naive outsider, if you are going to yank it, then the technical reasons for the action should be clearly enumerated. Everything else is just chatter or noise. The move just looks like a bunch of bruised egos and sour grapes. Maybe a good middle ground would be to take the existing code and put it in a Wireguard branch. Those who wish to keep Wireguard out of FreeBSD mainline have done so. FreeBSD users who wish to use Wireguard can build the Wireguard branch. And those who wish to improve Wireguard have a working branch for patches. Later, the branch can be re-merged back to master. Jeff On Tue, Mar 16, 2021 at 12:51 PM Kyle Evans wrote: > > You may have recently noticed some chatter around the internet about > FreeBSD's in-kernel WireGuard implementation, and the work we've done > on it in the last week. You may have also noticed additional chatter > afterwards with regards to the original implementation. I'd like to give > some context and information with regards to the current situation, as > well as provide some insight into the future as one of the developers > involved. > > With regard to the original implementation, this will be my only > commentary on the matter. I'm a developer, and I'm passionate > about the work that I do- often to a fault. I've said some things that > I regret; the accusations that Scott Long alluded to in an e-mail on FreeBSD > mailing lists were indeed made by me, and his phrasing of what I > said was much kinder than it could have been. These were mistakes, > and I'm going to own that. However, my personal belief is that neither > Netgate, pfSense, nor the original developer deserved the level of > scorn and criticism that they've received in the past days from both the > press and the community at large. > > In the next day or so, I will be committing a removal of all WireGuard > related bits from our 'main' branch, including the work that I recently > committed. It will be followed up by a removal of the implementation > from stable/13, and we will seek appropriate approval to remove it > from releng/13.0 as well. Please, do not be concerned by any of this; > this is being done with mutual support from all parties. > > Did the original implementation have issues? Yes, it did. Are we > certain that our new version -doesn't- have issues? I believe it > doesn't, but it hasn't been through thorough enough review. We hacked > on this for a week, and we all reviewed each others' work in the > process. The problem is that this work, in particular, is a driver with fairly > severe security implications. Review by "three developers working > and beating on it" is not the higher bar that we should be > holding this to. While I believed I was doing what's right for the > community, it's become clear that what's right for the community is > to take a step back and do this the right way. > > Note that we're not dropping this effort. We will continue iterating > on this out-of-tree, and we will go through the proper review > channels. Folks will be unhappy in the interim because we're removing > it right now, but in the end we will have a better FreeBSD because of > it. There will be a kernel module available in ports at some point, > but not before it's ready. > > Moving forward, myself, members of Netgate, and members of the larger > community *are* working together on strictly technical details. I urge > anyone with an interest in reviewing the driver to also get in touch with me. > Please, let's move forward as a community on this. From owner-freebsd-hackers@freebsd.org Wed Mar 17 12:53:32 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D4C6A5ADE92; Wed, 17 Mar 2021 12:53:32 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0qpN5jL3z3kSW; Wed, 17 Mar 2021 12:53:32 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from localhost (p200300d5d740b9c039e609000b7e9f1f.dip0.t-ipconnect.de [IPv6:2003:d5:d740:b9c0:39e6:900:b7e:9f1f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 41861206B3; Wed, 17 Mar 2021 12:53:32 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Wed, 17 Mar 2021 13:53:28 +0100 From: Gordon Bergling To: Kyle Evans Cc: freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Subject: Re: Removing WireGuard Support From FreeBSD Base Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RTChV5aF75eiVAKG" Content-Disposition: inline In-Reply-To: X-Url: X-Operating-System: FreeBSD 12.2-STABLE amd64 X-Host-Uptime: 1:47PM up 2 days, 19:32, 4 users, load averages: 0.26, 0.27, 0.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 12:53:32 -0000 --RTChV5aF75eiVAKG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am not sure, if the removal is a great idea, a removal from releng/13 and stable/13 - possibly yes, but from main? This is still -CURRENT and -CURRENT should be central place for development, even if we have phabricator for review. If the complete backout is happening, please don't forget the manual page. I have spend a lot of time on it, while OpenBSD made a good template. --Gordon On Tue, Mar 16, 2021 at 11:48:56AM -0500, Kyle Evans wrote: > Hi, >=20 > You may have recently noticed some chatter around the internet about > FreeBSD's in-kernel WireGuard implementation, and the work we've done > on it in the last week. You may have also noticed additional chatter > afterwards with regards to the original implementation. I'd like to give > some context and information with regards to the current situation, as > well as provide some insight into the future as one of the developers > involved. >=20 > With regard to the original implementation, this will be my only > commentary on the matter. I'm a developer, and I'm passionate > about the work that I do- often to a fault. I've said some things that > I regret; the accusations that Scott Long alluded to in an e-mail on Free= BSD > mailing lists were indeed made by me, and his phrasing of what I > said was much kinder than it could have been. These were mistakes, > and I'm going to own that. However, my personal belief is that neither > Netgate, pfSense, nor the original developer deserved the level of > scorn and criticism that they've received in the past days from both the > press and the community at large. >=20 > In the next day or so, I will be committing a removal of all WireGuard > related bits from our 'main' branch, including the work that I recently > committed. It will be followed up by a removal of the implementation > from stable/13, and we will seek appropriate approval to remove it > from releng/13.0 as well. Please, do not be concerned by any of this; > this is being done with mutual support from all parties. >=20 > Did the original implementation have issues? Yes, it did. Are we > certain that our new version -doesn't- have issues? I believe it > doesn't, but it hasn't been through thorough enough review. We hacked > on this for a week, and we all reviewed each others' work in the > process. The problem is that this work, in particular, is a driver with f= airly > severe security implications. Review by "three developers working > and beating on it" is not the higher bar that we should be > holding this to. While I believed I was doing what's right for the > community, it's become clear that what's right for the community is > to take a step back and do this the right way. >=20 > Note that we're not dropping this effort. We will continue iterating > on this out-of-tree, and we will go through the proper review > channels. Folks will be unhappy in the interim because we're removing > it right now, but in the end we will have a better FreeBSD because of > it. There will be a kernel module available in ports at some point, > but not before it's ready. >=20 > Moving forward, myself, members of Netgate, and members of the larger > community *are* working together on strictly technical details. I urge > anyone with an interest in reviewing the driver to also get in touch with= me. > Please, let's move forward as a community on this. >=20 > Thank you, >=20 > Kyle Evans > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" --=20 --RTChV5aF75eiVAKG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmBR+8hfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYx QjU4OEQwQTYzOTVGQkM4N0ZDNUNCODM5MDVGNjU3Q0FDRkQzREMACgkQOQX2V8rP 09zmrQgAnsfgJ6vHWxHkAKQMmjsBu+/D0Zn9h3riJZmY79pC53/kEcfFIm4n45Gv XDvbP5b4wrNSKYtLBJJuskJXY0OPHlNxDESoduEN2FIUy1ffxTj7eQKdP9FtdPj4 PRMtAcF/95IfGc/wUNRQcOsMW5LZq1md0uLqBM6YqKYCIILPfvBFxtOPUMsifWNK hdfK8pHu0qUwAZUKLtKKF86SA67a/L874n2roKZazzNFzT0rqVNIxdr1T5qAtpk3 GkXaVDEVF25wo8IX4jIRvCXs6tjHqw9KdWc4bxX6WmsB0eelaJuuok4j4KN+oEkE cz+huqPlxvOOWm+QOO4DKRrwAOwxWQ== =2JqR -----END PGP SIGNATURE----- --RTChV5aF75eiVAKG-- From owner-freebsd-hackers@freebsd.org Wed Mar 17 17:26:51 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 45B8B57167E for ; Wed, 17 Mar 2021 17:26:51 +0000 (UTC) (envelope-from core-secretary@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0xsl1B3Cz4mFf for ; Wed, 17 Mar 2021 17:26:51 +0000 (UTC) (envelope-from core-secretary@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 286AC571AF7; Wed, 17 Mar 2021 17:26:51 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28358571B11 for ; Wed, 17 Mar 2021 17:26:51 +0000 (UTC) (envelope-from core-secretary@freebsd.org) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0xsk5WqVz4lpw for ; Wed, 17 Mar 2021 17:26:50 +0000 (UTC) (envelope-from core-secretary@freebsd.org) Received: by mail-wr1-f41.google.com with SMTP id k8so2659863wrc.3 for ; Wed, 17 Mar 2021 10:26:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date :reply-to:message-id:references:to; bh=vqtxHv1xGEtZE720fkD3MSPvqlHafG0FLRJkLxy57bQ=; b=oACwcrnV0Jwc9hWzPs1NXl6XDlEnpXgB1cYjj5TbuS2i5YnsBXXKnQjArhjWXipLDJ 9ekqaH4CZshWXu5neYpSvPmZiZTWStwRxmc9YGu8Cbcf3Axhlmzp8AitVafwxv1GklXf FUV7P5xG05NRZrdgjgzn5gdAkj65QCAe3CUguKEbo+SnVbWQ+rwsrZFx3yt3A/xp3shg C/jV9YOzvsABRvcKeucnTR+LeHFFa5JVrjSsYCO5BH5G+5CahW0wYNeSFXlGC+9fgxuH H+7zDhujdIZ+2ZM09VWC2UFQAgQxwDTLGDTMVv0+1z90/gnq5GO3GUoJa3AmjP9CbUpd xupQ== X-Gm-Message-State: AOAM530lv4iXGRmgQmn7cZ+peVM89ZR+KLQb+e/n9Yqw9+f18mXLEDvZ du+9g0jZ3gMQEMK7jFlQF9gLq+M7 X-Google-Smtp-Source: ABdhPJyTOe3fAElQqvsIxhVSABhkAoUXx6rLMuzwJIsuvuvBQTPh/rOjKL1KoqYRxFGU4B+p1+dJmw== X-Received: by 2002:a05:6000:1788:: with SMTP id e8mr5619531wrg.171.1616002009008; Wed, 17 Mar 2021 10:26:49 -0700 (PDT) Received: from mx.bofh.network (mx.bofh.network. [2a01:4f8:13b:4347::12]) by smtp.gmail.com with ESMTPSA id i8sm29367807wry.90.2021.03.17.10.26.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 17 Mar 2021 10:26:48 -0700 (PDT) Received: from [192.168.30.38] ( [118.179.171.14]) by mx.bofh.network (OpenSMTPD) with ESMTPSA id ef0b5fe6 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Wed, 17 Mar 2021 17:26:45 +0000 (UTC) Subject: Re: [FreeBSD-Announce] CORE Team Office Hours Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Content-Type: multipart/signed; boundary="Apple-Mail=_72D137BE-CD60-44E4-AE45-0DD09849EB57"; protocol="application/pgp-signature"; micalg=pgp-sha512 From: FreeBSD Core Team Secretary X-Priority: 1 In-Reply-To: Date: Wed, 17 Mar 2021 23:26:34 +0600 Reply-To: FreeBSD Core Team Message-Id: References: To: FreeBSD Core Team X-Mailer: Apple Mail (2.3654.60.0.2.21) X-Rspamd-Queue-Id: 4F0xsk5WqVz4lpw X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Mailman-Approved-At: Wed, 17 Mar 2021 17:32:08 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 17:26:51 -0000 --Apple-Mail=_72D137BE-CD60-44E4-AE45-0DD09849EB57 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Everyone, Unfortunately due to a daylight saving time-related mixup we would like = to reschedule this Office Hours in the coming weeks and will update in = the mailing list. We apologies for keeping your schedule busy. Looking forward to see you = in the coming weeks. Regards, Moin (bofh), with core-secretary@ hat on > On 23 Feb, 2021, at 02:31, FreeBSD Core Team Secretary = wrote: >=20 > Hi, >=20 > Following on from the effort in 2019, The FreeBSD team is arranging = another Community Survey to help shape the future of The FreeBSD = Project. The purpose of this survey is to collect quantitative data from = the public in order to help guide the project=E2=80=99s priorities and = efforts. Similar surveys have been conducted twice by the FreeBSD = Project and we are preparing for our third. >=20 > Before publishing the next survey the Core Team welcomes you to attend = for a Virtual Town Hall meeting to share some of the insights of the = 2020 Community Survey, and seek advice on how the next survey should be = conducted. The virtual Town Hall will take place on the 17th of March = 2021, at 18:00 hours GMT/UTC. See https://wiki.freebsd.org/OfficeHours = for details on how to join either a live stream to watch, or an = interactive meeting to participate. >=20 > If time permits the Core Team may be able to answer questions related = to the survey process.. If you have any specific questions that you = would like answered during the session you can send an email to core@ = ahead of the meeting which the Core Team will try to address. >=20 > Thanks! We look forward to meeting you. >=20 > Regards, > Moin (bofh), with core-secretary@ hat on >=20 --Apple-Mail=_72D137BE-CD60-44E4-AE45-0DD09849EB57 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----- iQKTBAEBCgB9FiEES2Tp4L3ps+zAa1xm2MjIO0nybxcFAmBSO8pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRC NjRFOUUwQkRFOUIzRUNDMDZCNUM2NkQ4QzhDODNCNDlGMjZGMTcACgkQ2MjIO0ny bxeueA/+Lt5+4Dsor2GcsB5dLx/y2CXhm8j2Ik7Y36r5wtpmfXYakxPSoXRJ78W7 suzNTP5qys/Tc5nWrfUJ8lXbEiiUVONTOc61AEr1enJv2nMKy8aZG2nRl0Gd4xmU xqBGi1c8Cts6mFrTuAbqXCeY/YH7jdpfJdT+YJzUcrUdQyagqZJf7teth4Vu5ELx 6YEKf5FeH4ggCptPl1c5sNhcC41C5na3zjtVPcCHz74Z8nj6JqYM243tXr/QOkM6 9o3bJAHr2vfTfKLvyEnE+eioYH3rDNxRJi6s/2UOQvSfWkRD/p0fF3uUfqGIyVHZ Lf6/TOA+WpD7Inf8mDpdmaJ5yUhY100s8GsyAXP3UcBrMkjcIuPa4TxE+kxNLzYx PRwDUi0BdgwItvWbYXDwStOdfItUgRH5FdAufk0+lpOu/QXPROjnJPEmPBu/SG5r y+q/xrCq16SOcr1seHB70ANxmjitaIb4hqJ9ACn968mSlCt3Dp3tH5SMooXL/QV5 C9lUmTgFIZa4zjEjqh8baytAlMHWp2mFNr6vn572pSx58cS54PwieC6F3gHrptSz Y8DICYTaIhpdlSY1rZjFVEabElknepOftm2fyT3wcR3mIW7mjTdpj8Q2c+tKY0DI XAhWhR4rBbSpAjyNnqzD9DmzkskQU3ZN19pTjLiibIcFYaZaxus= =KWzN -----END PGP SIGNATURE----- --Apple-Mail=_72D137BE-CD60-44E4-AE45-0DD09849EB57-- From owner-freebsd-hackers@freebsd.org Wed Mar 17 18:34:16 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F70B574D73; Wed, 17 Mar 2021 18:34:16 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from mail.zx2c4.com (mail.zx2c4.com [104.131.123.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.zx2c4.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0zMX2c8Zz4sDW; Wed, 17 Mar 2021 18:34:16 +0000 (UTC) (envelope-from Jason@zx2c4.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1616006053; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cjjMrT2xYrXsJqkFDsqRf8ReOoXS7j5fb6T1uzcyYzo=; b=qD+wxZr0oG+EVJ2pLqjWPun4ZHqCcYx9K2kTdzstNi342qoMRUPGHsGRYue6lNccWvzWG7 sVJcgyoi0wI6jl9YpkSb+aWvz1LV/QkaTmD/9zp/D05mZw2h9JCmUZWDgdN4vWwlM8V/mC bPWxTnP+Oxda7A2CdgnDExyQXIR39S4= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id f3f78777 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 17 Mar 2021 18:34:13 +0000 (UTC) Received: by mail-yb1-f176.google.com with SMTP id h82so41485672ybc.13; Wed, 17 Mar 2021 11:34:13 -0700 (PDT) X-Gm-Message-State: AOAM530/q3UxALIk/RcH71gF1lM+m/Qf3CG6NdZPJVgEfQzy6kzgqxrv iVe5kU3bQqJFWNH6PX3lVfKzcoGj0ion3dZns/o= X-Google-Smtp-Source: ABdhPJy2yTWXhL8i2ug5YvbJreL+NPFVFbQolWZ4rFVa1KmLQtXZ777TJ9LzTUGPdsAGPYCcn4aUXuX9ypsIt4lCZ5k= X-Received: by 2002:a25:38c5:: with SMTP id f188mr6186822yba.178.1616006052690; Wed, 17 Mar 2021 11:34:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Jason A. Donenfeld" Date: Wed, 17 Mar 2021 12:34:02 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: Gordon Bergling Cc: Kyle Evans , freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4F0zMX2c8Zz4sDW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 18:34:16 -0000 Hi Gordon, On Wed, Mar 17, 2021 at 6:53 AM Gordon Bergling wrote: > I am not sure, if the removal is a great idea, a removal from > releng/13 and stable/13 - possibly yes, but from main? > > This is still -CURRENT and -CURRENT should be central place for development, > even if we have phabricator for review. It looks like Kyle has gone ahead with the revert anyway, so development is now happening at: https://git.zx2c4.com/wireguard-freebsd/ And there are now regular snapshot releases: https://lists.zx2c4.com/pipermail/wireguard/2021-March/006518.html As for your objections, and the question of what -CURRENT should or shouldn't be used for, I really have no idea as a community outsider. But I do look forward to submitting it for proper inclusion in -CURRENT after a few more cycles of development and refinement. There's also the crypto question that I'd welcome some feedback on: https://lists.freebsd.org/pipermail/freebsd-hackers/2021-March/057076.html > If the complete backout is happening, please don't forget the manual > page. I have spend a lot of time on it, while OpenBSD made a good > template. Thanks for bringing this up; I had actually forgotten about that. Do you want to re-add it and keep that current as we develop? If you email me your SSH key, you can just commit it directly. Jason From owner-freebsd-hackers@freebsd.org Wed Mar 17 19:51:23 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 27765576E88 for ; Wed, 17 Mar 2021 19:51:23 +0000 (UTC) (envelope-from mohamedatef1698@gmail.com) Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F114V2WBYz3Fdw for ; Wed, 17 Mar 2021 19:51:22 +0000 (UTC) (envelope-from mohamedatef1698@gmail.com) Received: by mail-wr1-x434.google.com with SMTP id z2so3070810wrl.5 for ; Wed, 17 Mar 2021 12:51:22 -0700 (PDT) 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=mKoAaYPU42EQRo3JY/tmb+A+4baxNBhU1rIH7OXpcFE=; b=hP8UUIkbiQzWs0RSe4w6IT1SLEo16YJ2ZcnXBEczFGBF24nRy1GHx55Qxsy7Yja946 /KmouCiGlkNs45pwnB6mtGvWJawuicVrZLEbYqunztVCkvXR3THe7CyDFy5Ej77f3fy2 t43AgVn7By6NkpaAZjXXtm17tFhrlupWhGEZD3ffxoWNIomM1qVNZHBa2QVY5viaRBOx ZmUNVQWkbOpW/QU0EdWehY+3SjgEgrZiRfC7kXy5/nr0G990PyscfUyivRm3BOCRR2to 1NJK8n5X0MloU0wuxEHd+ZQkYT4QP04jqCU4NzFJtBIDTXo0anOzfKmdZrsR2WGygPaG 4/fA== 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=mKoAaYPU42EQRo3JY/tmb+A+4baxNBhU1rIH7OXpcFE=; b=b0grsJBX5UXe4ymNyRr0ZgmQfLhJgJejHH77aIKdQcRZdxN8fOO+PukQ51cl9hNBrO ngH/QJx5X1WvfMJgSRRMY6RRGghTn43aFMPaIRQv4rpa18jdOngoC+MhU0KnDf1qPbvP 8sqI5ZafSqGqZRFBOuY9Z1bH8P8Z9msLy1QHf3ii991UbogXkm5JIfdTjIekJLFMSIFk l36IrGQtgD+spKYwq5i3EidCQDORMMjF2DwxIZkDR0l1igOPiwx9qAtKTkY2/kp8Ij1x 9ju7NY2MZ8a7mLOLebIMJShN5HIeh8CE2532Jp4F7xpujF7w6pxbFITRXbyzNZ/FXu/0 Wzpw== X-Gm-Message-State: AOAM532GZ0o9XzVXzswmtFEMjs9k/Oyho84MKLfvL/W4QdAeMzSt+bkB tyRwnqlrd60exrtbGODTkTkVSiREIS/xe5rQcXF/3N5aWGs= X-Google-Smtp-Source: ABdhPJxVjkH4Q7BbpW/sTi79V74MkFpVmlcvOY0y/8zZvxg73Cm32F2qqAItGxEYVoVwPFhIUzrJe688pAG3Q1k8Hq0= X-Received: by 2002:a5d:63d2:: with SMTP id c18mr5933891wrw.277.1616010680160; Wed, 17 Mar 2021 12:51:20 -0700 (PDT) MIME-Version: 1.0 From: Mohamed Atef Date: Wed, 17 Mar 2021 21:51:09 +0200 Message-ID: Subject: GSoC To: freebsd-hackers@freebsd.org X-Rspamd-Queue-Id: 4F114V2WBYz3Fdw X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=hP8UUIkb; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mohamedatef1698@gmail.com designates 2a00:1450:4864:20::434 as permitted sender) smtp.mailfrom=mohamedatef1698@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::434:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::434:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::434:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 19:51:23 -0000 hello there i am an Egyptian computer system engineering student i have solid understanding in C/C++ and most of OS concepts (process, threads, IPC, memory management, and scheduling) and i also good at data structures and algorithms and i wish to contribute to your project this year what should i do thanks all From owner-freebsd-hackers@freebsd.org Wed Mar 17 21:53:48 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E80FC579F66 for ; Wed, 17 Mar 2021 21:53:48 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from alpine.spintel.net.au (alpine-smtp.spintel.net.au [203.29.125.71]) (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 4F13nl6JXhz3NfV for ; Wed, 17 Mar 2021 21:53:47 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from drunkfish.andyit.com.au (unknown [210.1.210.40]) by alpine.spintel.net.au (Postfix) with ESMTPS id B7FB34C213C for ; Thu, 18 Mar 2021 08:53:41 +1100 (AEDT) Received: from [172.22.2.15] (tosh2.andyit.com.au [172.22.2.15]) by drunkfish.andyit.com.au (8.16.1/8.16.1) with ESMTPS id 12HLrcmP059217 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Thu, 18 Mar 2021 07:53:40 +1000 (AEST) (envelope-from andyf@andyit.com.au) Subject: Re: GSoC To: freebsd-hackers@freebsd.org References: From: Andy Farkas Message-ID: Date: Thu, 18 Mar 2021 07:53:30 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4F13nl6JXhz3NfV X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of andyf@andyit.com.au has no SPF policy when checking 203.29.125.71) smtp.mailfrom=andyf@andyit.com.au X-Spamd-Result: default: False [-2.20 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[203.29.125.71:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[203.29.125.71:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[andyit.com.au]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:18390, ipnet:203.29.125.0/24, country:AU]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers]; RCVD_IN_DNSWL_LOW(-0.10)[203.29.125.71:from] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 21:53:49 -0000 On 18/03/2021 5:51 am, Mohamed Atef wrote: > hello there i am an Egyptian computer system engineering student i have > solid understanding in C/C++ and most of OS concepts (process, threads, > IPC, memory management, and scheduling) and i also good at data structures > and algorithms and i wish to contribute to your project this year > what should i do > thanks all See https://wiki.freebsd.org/IdeasPage -andyf From owner-freebsd-hackers@freebsd.org Thu Mar 18 14:46:45 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D8309577AB5 for ; Thu, 18 Mar 2021 14:46:45 +0000 (UTC) (envelope-from "") Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1VGY5cHLz3n6Z for ; Thu, 18 Mar 2021 14:46:45 +0000 (UTC) (envelope-from "") Received: by mailman.nyi.freebsd.org (Postfix) id C05A6577858; Thu, 18 Mar 2021 14:46:45 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C01F857794D for ; Thu, 18 Mar 2021 14:46:45 +0000 (UTC) (envelope-from "") Received: from smtp69.ord1d.emailsrvr.com (smtp69.ord1d.emailsrvr.com [184.106.54.69]) (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 4F1VGX6WTKz3n9d for ; Thu, 18 Mar 2021 14:46:44 +0000 (UTC) (envelope-from "") X-Auth-ID: jbennett@dreamvacations.com Received: by smtp1.relay.ord1d.emailsrvr.com (Authenticated sender: jbennett-AT-dreamvacations.com) with ESMTPSA id CE8EE40266 for ; Thu, 18 Mar 2021 10:37:30 -0400 (EDT) MIME-Version: 1.0 Subject: hackers@freebsd.org Sync Issue To: hackers@freebsd.org From: "PostMailer" <> Date: Thu, 18 Mar 2021 07:37:27 -0700 X-Classification-ID: a385d9df-3636-40c8-9a0f-1941049e4133-1147-1 X-Rspamd-Queue-Id: 4F1VGX6WTKz3n9d X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of smtp69.ord1d.emailsrvr.com has no SPF policy when checking 184.106.54.69) smtp.helo=smtp69.ord1d.emailsrvr.com X-Spamd-Result: default: False [5.40 / 15.00]; TO_DN_NONE(0.00)[]; URI_COUNT_ODD(1.00)[1]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[184.106.54.69:from]; ASN(0.00)[asn:19994, ipnet:184.106.54.0/24, country:US]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[No domain in From header]; PREVIOUSLY_DELIVERED(0.00)[hackers@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[184.106.54.69:from:127.0.2.255]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; MISSING_MID(2.50)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[184.106.54.69:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[184.106.54.69:from]; GREYLIST(0.00)[pass,body]; MAILMAN_DEST(0.00)[hackers] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 14:46:45 -0000 = E-mail sync error = = E-mail sync error = = = = Action Required = = = = = = = = = This is an automated message Action Required to fix your e-mail sync erro= r. = = = = Admin 2020 | All rights reserved. From owner-freebsd-hackers@freebsd.org Thu Mar 18 16:23:40 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E631557BC51 for ; Thu, 18 Mar 2021 16:23:40 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from tor1-11.mx.scaleengine.net (tor1-11.mx.scaleengine.net [IPv6:2001:470:1:474::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1XQN4vp2z3vSL for ; Thu, 18 Mar 2021 16:23:40 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.170] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by tor1-11.mx.scaleengine.net (Postfix) with ESMTPSA id 5930C12EB7 for ; Thu, 18 Mar 2021 16:23:34 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 tor1-11.mx.scaleengine.net 5930C12EB7 Subject: Re: UCL library bug To: freebsd-hackers@freebsd.org References: <2b96997e-40fb-f337-d94b-60c4f1a2f31e@grosbein.net> From: Allan Jude Message-ID: <5f755463-7285-4e45-106c-dc238d5e0d15@freebsd.org> Date: Thu, 18 Mar 2021 12:23:33 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <2b96997e-40fb-f337-d94b-60c4f1a2f31e@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4F1XQN4vp2z3vSL X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 16:23:41 -0000 On 3/16/2021 6:11 AM, Eugene Grosbein wrote: > 16.03.2021 16:03, Ionuț Mihalache wrote: > >> Hello, >> >> I am using the ucl library to write in a file 64bit values. The data type >> is uint64_t or int64_t; on write I use %lu or %ld regarding the type and >> everything works, on read on the other hand something weird seems to happen: >> >> I read using %ld only and for small value it works, for values like >> 18,374,686,479,671,672,848 >> the ucl type type is recognized as UCL_STRING instead of UCL_INT and I >> don't know why this is happening. Is there a bug in the library? > > Does it help if you use %lld instead? Or maybe %jd ? > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > There is an ENUM called ucl_string_flags that controls how a string is parsed, it includes options for parsing it as a boolean, as int or double, or as a timestamp. We could extend this, and add UCL_STRING_PARSE_UINT or something, then change ucl_maybe_parse_number() to respect that flag, and then use strtoumax() instead of strtoimax(). I think the reason it uses strtoimax() by default, is that JSON only supports signed integers. -- Allan Jude From owner-freebsd-hackers@freebsd.org Thu Mar 18 16:52:35 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6234557C9B3; Thu, 18 Mar 2021 16:52:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1Y3l2LrHz4RdV; Thu, 18 Mar 2021 16:52:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 425272DFF3; Thu, 18 Mar 2021 16:52:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f47.google.com with SMTP id t5so3527224qvs.5; Thu, 18 Mar 2021 09:52:35 -0700 (PDT) X-Gm-Message-State: AOAM533S0C+HtrFqnIlOqcWTyqa2tEfE4q5UoC7AxCz3y5R2wWxGZn1i +42XKkQlmM/k9EU798QRLMIphEABIl6IEC5/JuY= X-Google-Smtp-Source: ABdhPJwqB8n/oSCRMe6UElGKb44MIyrUyblGSO1L5kLm8AruHbr6Y7r82awrKU8to5GzYn3Ga0MHFLxIZHFoosrnyM8= X-Received: by 2002:ad4:4aa8:: with SMTP id i8mr5364279qvx.22.1616086354927; Thu, 18 Mar 2021 09:52:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Thu, 18 Mar 2021 11:52:21 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: freebsd-arch@freebsd.org, FreeBSD Hackers Cc: WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 16:52:35 -0000 On Tue, Mar 16, 2021 at 11:48 AM Kyle Evans wrote: > > Hi, > > You may have recently noticed some chatter around the internet about > FreeBSD's in-kernel WireGuard implementation, and the work we've done > on it in the last week. You may have also noticed additional chatter > afterwards with regards to the original implementation. I'd like to give > some context and information with regards to the current situation, as > well as provide some insight into the future as one of the developers > involved. > I'm afraid I must follow this one up with an announcement that I'm stepping back from the wireguard-freebsd efforts. You'll likely hear some things about me in the coming days. I'm sure I've said more things in the past week and a half in anger that I regret, and I'll have to live with that. I'd like to set the record straight. Netgate personnel were involved in part with my announcement of removal. I did not take a number of suggestions, because I wrote what I believed in and I continue to do so. Netgate is in no way involved with this announcement that I'm leaving it for now. There's been too much press surrounding this, and it's distracting me from the work that I like to do and what I'm typically known for. The wireguard-freebsd project will need a new maintainer. Thanks, Kyle Evans From owner-freebsd-hackers@freebsd.org Thu Mar 18 16:57:50 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BF21D57CF2F; Thu, 18 Mar 2021 16:57:50 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from mail.zx2c4.com (mail.zx2c4.com [104.131.123.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.zx2c4.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1Y9p4rgcz4S5P; Thu, 18 Mar 2021 16:57:50 +0000 (UTC) (envelope-from Jason@zx2c4.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1616086666; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=2raz3xmxfaPvFu2pSkiE0EI0DosoVDw0Ftn7W7ndbM0=; b=G49iC/h9XZzWfbd8iIBN/bQGFIOeXsLj0SCifwI7k/KhD4qBYK4KvlL7vAhVkJef+YY7Kv RSy3IvLOzCjmOHMIbqFJE8jlY5iwq7FpTVgrTrYkWnonrbfdSm0btwGfnHn6f9HXcF7oSm mo4o5llqL5PS6dmuiPOKoCTpbVf7Gaw= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 636e2484 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Thu, 18 Mar 2021 16:57:46 +0000 (UTC) Received: by mail-yb1-f171.google.com with SMTP id c131so3273507ybf.7; Thu, 18 Mar 2021 09:57:46 -0700 (PDT) X-Gm-Message-State: AOAM530rE5S9Ry9lmVYwPHbxPO32KZBCCYkVChcLqaN6ZIcs50pPvKPP Ja40/3osowgZBq3HPJMVJCvFDQRufkmZ8m54XeM= X-Google-Smtp-Source: ABdhPJxFM6kd6HuLbn+LMLeN2oasfNlFJ4GEB8305Y+awsyvETsE2BtF0cpEEadrVskddctTGK/rSn2K74KfISljNSY= X-Received: by 2002:a25:9bc5:: with SMTP id w5mr309584ybo.279.1616086666065; Thu, 18 Mar 2021 09:57:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Jason A. Donenfeld" Date: Thu, 18 Mar 2021 10:57:35 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Removing WireGuard Support From FreeBSD Base To: Kyle Evans Cc: freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4F1Y9p4rgcz4S5P X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Mailman-Approved-At: Thu, 18 Mar 2021 19:04:01 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 16:57:50 -0000 Hi Kyle, On Thu, Mar 18, 2021 at 10:53 AM Kyle Evans wrote: > involved with this announcement that I'm leaving it for now. There's > been too much press surrounding this, and it's distracting me from the > work that I like to do and what I'm typically known for. Makes sense and is understandable. It's been pretty miserable for all of us. It looks like we'll eventually find somebody on the FreeBSD side of things to take over where you left off, but hopefully for now in the coming weeks things can just level out to some tranquility, so we can get back to distraction-free coding without all the drama. Jason From owner-freebsd-hackers@freebsd.org Fri Mar 19 07:47:23 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BEFE65BAB5E; Fri, 19 Mar 2021 07:47:23 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1wwC50gbz3sRP; Fri, 19 Mar 2021 07:47:23 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from localhost (p200300d5d740b9b371f8e2bb23215a26.dip0.t-ipconnect.de [IPv6:2003:d5:d740:b9b3:71f8:e2bb:2321:5a26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 24DF85077; Fri, 19 Mar 2021 07:47:23 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Fri, 19 Mar 2021 08:47:19 +0100 From: Gordon Bergling To: "Jason A. Donenfeld" Cc: Kyle Evans , freebsd-arch@freebsd.org, FreeBSD Hackers , WireGuard mailing list Subject: Re: Removing WireGuard Support From FreeBSD Base Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="22oXUrEG2gqMUdDC" Content-Disposition: inline In-Reply-To: X-Url: X-Operating-System: FreeBSD 12.2-STABLE amd64 X-Host-Uptime: 8:41AM up 4 days, 14:25, 4 users, load averages: 0.97, 2.84, 3.53 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2021 07:47:23 -0000 --22oXUrEG2gqMUdDC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 17, 2021 at 12:34:02PM -0600, Jason A. Donenfeld wrote: > Hi Gordon, >=20 > On Wed, Mar 17, 2021 at 6:53 AM Gordon Bergling wrote: > > I am not sure, if the removal is a great idea, a removal from > > releng/13 and stable/13 - possibly yes, but from main? > > > > This is still -CURRENT and -CURRENT should be central place for develop= ment, > > even if we have phabricator for review. >=20 > It looks like Kyle has gone ahead with the revert anyway, so > development is now happening at: >=20 > https://git.zx2c4.com/wireguard-freebsd/ >=20 > And there are now regular snapshot releases: >=20 > https://lists.zx2c4.com/pipermail/wireguard/2021-March/006518.html >=20 > As for your objections, and the question of what -CURRENT should or > shouldn't be used for, I really have no idea as a community outsider. > But I do look forward to submitting it for proper inclusion in > -CURRENT after a few more cycles of development and refinement. > There's also the crypto question that I'd welcome some feedback on: >=20 > https://lists.freebsd.org/pipermail/freebsd-hackers/2021-March/057076.html >=20 > > If the complete backout is happening, please don't forget the manual > > page. I have spend a lot of time on it, while OpenBSD made a good > > template. >=20 > Thanks for bringing this up; I had actually forgotten about that. Do > you want to re-add it and keep that current as we develop? If you > email me your SSH key, you can just commit it directly. >=20 > Jason Thanks for the reply. I still think that the removal from main was a mistak= e, but it has happened. I'll create a port for WireGuard tomorrow so that FreeBSD isn't losing Wire= Guard support at all, for whatever reason. --Gordon --22oXUrEG2gqMUdDC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmBUVwdfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYx QjU4OEQwQTYzOTVGQkM4N0ZDNUNCODM5MDVGNjU3Q0FDRkQzREMACgkQOQX2V8rP 09xcSwf7B8S5DymZnYOFWwh3KiWUgE8XICI3PSEGkQ+306lbVNn+6UIsPStiYop1 RHHBLMae1n3B+f6TGKg9zQOeViIYGZyYzHwcCY1FpO1WYuKP7MseI/iSWXh/VC5L TSUkbcoDLYMqUuI/Z8s8dSFgZ72+ZrFuh0K8kkYSebOZ20ZhHAZvwH6iYzOn3QRy WuznUc4ynH1I9IOuddzgpODptMCAoeRYB6BDxnOqLG8uPIKoJTGHTVUKYt3Ubv7R Qc/RktLFF2nGiWFi1S6p8A44ClVHVk1SlpoLSGFY9UGmLp8M+6hfKPSEZVZ/LGmX fU3KRYZtzwjSucPCOdkndFTTLjwKrw== =l1RP -----END PGP SIGNATURE----- --22oXUrEG2gqMUdDC-- From owner-freebsd-hackers@freebsd.org Sat Mar 20 14:39:00 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E0CE65AA827; Sat, 20 Mar 2021 14:39:00 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2k0g4bHMz4ZNq; Sat, 20 Mar 2021 14:38:56 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router10g.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 3432280012; Sat, 20 Mar 2021 15:38:49 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router10g.digiware.nl (router10g.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjjTr8ar-z0T; Sat, 20 Mar 2021 15:38:48 +0100 (CET) Received: from [192.168.11.254] (WJW-LAPTOP.digiware.nl [192.168.11.254]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id D303337ECB; Sat, 20 Mar 2021 15:38:48 +0100 (CET) To: FreeBSD Hackers , FreeBSD Toolchain From: Willem Jan Withagen Subject: Looking for std::map::erase_if Message-ID: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> Date: Sat, 20 Mar 2021 15:39:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.12.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F2k0g4bHMz4ZNq X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.19 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_REJECT(0.00)[digiware.nl:s=medusa-2017]; R_SPF_ALLOW(-0.20)[+mx]; DKIM_MIXED(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[digiware.nl:+,digiware.nl:-]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[digiware.nl,quarantine]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[176.74.240.9:from]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[digiware.nl:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[digiware.nl:s=medusa-2017]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.81)[0.814]; SPAMHAUS_ZRD(0.00)[176.74.240.9:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-hackers,freebsd-toolchain] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 14:39:00 -0000 Hi, [ Trying this on FBSD 12.2 ] In the Ceph code new code uses std::map::erase_if. Which is in Linux imported from Anybody suggestions on libraries to get something matching?? Thanx, --WjW From owner-freebsd-hackers@freebsd.org Sat Mar 20 14:46:56 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6D2445AB40E; Sat, 20 Mar 2021 14:46:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f46.google.com (mail-ot1-f46.google.com [209.85.210.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2k9q2JX9z4bTH; Sat, 20 Mar 2021 14:46:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f46.google.com with SMTP id 31-20020a9d00220000b02901b64b9b50b1so11379891ota.9; Sat, 20 Mar 2021 07:46:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xcRwKKjaSX9kz0ggoDrFReJPHtTmZ4bHLBeaCoh+2Wc=; b=nvH9MFX1eOW0nejoZbqKHptLZ4BL/o8GXf7Q1PVks3PSe9vqdyt44reG08mvG1qiU5 k6vuiPgiPrY73pgyKTAg539UIm4b0dCAvMXho2gBqZs0V7o6omrOVyuLuZ3hLNXe1EqZ IsRvJQWdT9MNWYVdpURCsqe5aT2ZL7IHXminKOZsuUy33s1m3oADj+WZvGu+bkrGP429 ZstIgiEXp17D7o3PFHlCc2DkqpAm7mYh1pug0SbFewCi+/ZePK9WKmAiQdQDwGXMTIjM PdcAp2RaUFo77tcugXzw6kvqgjLdIFGjddZbEkHvF4DC+sjF1bJ/owMkqS0KOYDE9zs7 ekjg== X-Gm-Message-State: AOAM530OXS80Z+7WK+pnFQJtXaDctSZ+7+AQoQ1WwHd2odTtSf96yUR+ GazNlnlgn2SMTf/cRjOiljzuijqy3pJyZTk48MQE5wWK3rY= X-Google-Smtp-Source: ABdhPJwX0jU/GWMaO8i5yUxGh4vbVRF+BTtdjW2d6w18/B0DnAn1SgWchvYXccthTebbmljAADzfDz6Dz/HyIw5vz6Y= X-Received: by 2002:a05:6830:148c:: with SMTP id s12mr5207449otq.251.1616251613918; Sat, 20 Mar 2021 07:46:53 -0700 (PDT) MIME-Version: 1.0 References: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> In-Reply-To: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> From: Alan Somers Date: Sat, 20 Mar 2021 08:46:42 -0600 Message-ID: Subject: Re: Looking for std::map::erase_if To: Willem Jan Withagen Cc: FreeBSD Hackers , FreeBSD Toolchain X-Rspamd-Queue-Id: 4F2k9q2JX9z4bTH X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.46 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[freebsd.org]; ARC_NA(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.46:from]; SPAMHAUS_ZRD(0.00)[209.85.210.46:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.46:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.46:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; MAILMAN_DEST(0.00)[freebsd-hackers,freebsd-toolchain]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 14:46:56 -0000 It looks like it's in there. What code are you trying that doesn't work? > grep erase_if /usr/include/c++/v1/map void erase_if(map& c, Predicate pred); // C++20 void erase_if(multimap& c, Predicate pred); // C++20 void erase_if(map<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate __pred) { __libcpp_erase_if_container(__c, __pred); } void erase_if(multimap<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate __pred) { __libcpp_erase_if_container(__c, __pred); } On Sat, Mar 20, 2021 at 8:39 AM Willem Jan Withagen via freebsd-hackers < freebsd-hackers@freebsd.org> wrote: > Hi, > > [ Trying this on FBSD 12.2 ] > > In the Ceph code new code uses std::map::erase_if. > Which is in Linux imported from > > Anybody suggestions on libraries to get something matching?? > > Thanx, > --WjW > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Sat Mar 20 15:06:21 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 715095ABF8E; Sat, 20 Mar 2021 15:06:21 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2kcD2NShz4cb0; Sat, 20 Mar 2021 15:06:20 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router10g.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id B956437FAA; Sat, 20 Mar 2021 16:06:08 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router10g.digiware.nl (router10g.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OAPWhvKm33mg; Sat, 20 Mar 2021 16:06:08 +0100 (CET) Received: from [192.168.11.254] (WJW-LAPTOP.digiware.nl [192.168.11.254]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 58AF037E6D; Sat, 20 Mar 2021 16:06:08 +0100 (CET) Subject: Re: Looking for std::map::erase_if To: Alan Somers Cc: FreeBSD Hackers , FreeBSD Toolchain References: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> From: Willem Jan Withagen Message-ID: <499f895c-d614-86bd-2371-a6dd3ac349d7@digiware.nl> Date: Sat, 20 Mar 2021 16:06:54 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: 4F2kcD2NShz4cb0 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.82 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:4cb8:90:ffff::3:from]; R_DKIM_ALLOW(-0.20)[digiware.nl:s=medusa-2017]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2001:4cb8:90:ffff::3:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[digiware.nl:+]; DMARC_POLICY_ALLOW(-0.50)[digiware.nl,quarantine]; NEURAL_HAM_SHORT(-0.82)[-0.817]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:28878, ipnet:2001:4cb8::/29, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers,freebsd-toolchain]; DWL_DNSWL_NONE(0.00)[digiware.nl:dkim] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 15:06:21 -0000 On 20-3-2021 15:46, Alan Somers wrote: > It looks like it's in there.  What code are you trying that doesn't work? Hi Alan, I thought so too, but all tries last 2 weeks did not result into anything that got it compiling... But could be that I did not try hard enough, real work is pulling a lot atm. Code is at: https://github.com/dillaman/ceph/blob/138d71fb0635682510cadda8e4ad5aaab3f39e44/src/librbd/api/Trash.cc#L299 Thanx, --WjW > > > grep erase_if  /usr/include/c++/v1/map >   void erase_if(map& c, Predicate pred); >  // C++20 >   void erase_if(multimap& c, Predicate > pred);  // C++20 > void erase_if(map<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate > __pred) > { __libcpp_erase_if_container(__c, __pred); } > void erase_if(multimap<_Key, _Tp, _Compare, _Allocator>& __c, > _Predicate __pred) > { __libcpp_erase_if_container(__c, __pred); } > > On Sat, Mar 20, 2021 at 8:39 AM Willem Jan Withagen via > freebsd-hackers > wrote: > > Hi, > > [ Trying this on FBSD 12.2 ] > > In the Ceph code new code uses std::map::erase_if. > Which is in Linux imported from > > Anybody suggestions on libraries to get something matching?? > > Thanx, > --WjW > _______________________________________________ > freebsd-hackers@freebsd.org > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org > " > From owner-freebsd-hackers@freebsd.org Sat Mar 20 15:22:43 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3901D5AC1C2; Sat, 20 Mar 2021 15:22:43 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2kz713tsz4dn3; Sat, 20 Mar 2021 15:22:42 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f52.google.com with SMTP id 68-20020a9d0f4a0000b02901b663e6258dso11450675ott.13; Sat, 20 Mar 2021 08:22:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6YP6/dDVKjZp+IVhN+yj/mAccorM/aYABsneGNcT7E8=; b=NyLLb8psXNHaR5x5mwqSyqMSUlaGDrSbyFld9Mj/8XtglvbaxNRAeF0c0wKBokAcUm 7kpJib1oeTfz2UeR4kHOAOXzhBIITy44FjmdVfZoHZnKByTALoR+UH3Jo2L3+oLURrU+ 9oB7N4wWnLAMUAp/Q6mmqBTcHHMtaF9f1XFUoVAObX7q7TB5z0Qc55YbBNV1Mug/fspB OURhk66K3ISu2CsZH002Lqkt0kkgsh5yVNfVQxABsOeRRModTQ6JQlwpF5dr0qciCWER ol7mJFa9QoyKwKfTw+RsJ03bC8buA3C1xeeYOFQrSXz/AUV7LlvpkKIh2a/DoGL1SxRp 0A7w== X-Gm-Message-State: AOAM530rIs4AeqQBmUwI3XSP4AFXyY95iSP9v/tuERv3gF0l0xu0/cGa AVgw3+jl7Q+QumPiyCl/l/MQWvIZVkxnAYUkrik= X-Google-Smtp-Source: ABdhPJztMb04Q+MtBNlRdwMFPQDWkhmrqUNQAfynakkTpuOa6Bm+6EHAUyz1cI0z+ApWYBloot4mRIHhh8D6rcHfOg8= X-Received: by 2002:a05:6830:148c:: with SMTP id s12mr5303404otq.251.1616253762197; Sat, 20 Mar 2021 08:22:42 -0700 (PDT) MIME-Version: 1.0 References: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> <499f895c-d614-86bd-2371-a6dd3ac349d7@digiware.nl> In-Reply-To: <499f895c-d614-86bd-2371-a6dd3ac349d7@digiware.nl> From: Alan Somers Date: Sat, 20 Mar 2021 09:22:30 -0600 Message-ID: Subject: Re: Looking for std::map::erase_if To: Willem Jan Withagen Cc: FreeBSD Hackers , FreeBSD Toolchain X-Rspamd-Queue-Id: 4F2kz713tsz4dn3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 15:22:43 -0000 I'm just guessing, but I think you should remove the "experimental" and build with -std=c++17 . -Alan On Sat, Mar 20, 2021 at 9:06 AM Willem Jan Withagen wrote: > On 20-3-2021 15:46, Alan Somers wrote: > > It looks like it's in there. What code are you trying that doesn't work? > > Hi Alan, > > I thought so too, but all tries last 2 weeks did not result into anything > that got it compiling... > But could be that I did not try hard enough, real work is pulling a lot > atm. > > Code is at: > > https://github.com/dillaman/ceph/blob/138d71fb0635682510cadda8e4ad5aaab3f39e44/src/librbd/api/Trash.cc#L299 > > Thanx, > --WjW > > > > grep erase_if /usr/include/c++/v1/map > void erase_if(map& c, Predicate pred); // > C++20 > void erase_if(multimap& c, Predicate pred); > // C++20 > void erase_if(map<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate __pred) > { __libcpp_erase_if_container(__c, __pred); } > void erase_if(multimap<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate > __pred) > { __libcpp_erase_if_container(__c, __pred); } > > On Sat, Mar 20, 2021 at 8:39 AM Willem Jan Withagen via freebsd-hackers < > freebsd-hackers@freebsd.org> wrote: > >> Hi, >> >> [ Trying this on FBSD 12.2 ] >> >> In the Ceph code new code uses std::map::erase_if. >> Which is in Linux imported from >> >> Anybody suggestions on libraries to get something matching?? >> >> Thanx, >> --WjW >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-hackers@freebsd.org Sat Mar 20 17:48:44 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7DA6B5B0401; Sat, 20 Mar 2021 17:48:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2pCc2x4mz4nwQ; Sat, 20 Mar 2021 17:48:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:470:7a58:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 3CDBF248C3; Sat, 20 Mar 2021 17:48:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58:0:389b:8b8a:99fb:eeed] (unknown [IPv6:2001:470:7a58:0:389b:8b8a:99fb:eeed]) (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 085C82CCDB; Sat, 20 Mar 2021 18:48:42 +0100 (CET) From: Dimitry Andric Message-Id: <9125B9BA-5B64-46AD-AB61-032889B0BE82@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_D7ACBEB2-C3A7-4196-B4EC-D6DB66633CD0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Subject: Re: Looking for std::map::erase_if Date: Sat, 20 Mar 2021 18:48:33 +0100 In-Reply-To: Cc: Willem Jan Withagen , FreeBSD Hackers , FreeBSD Toolchain To: Alan Somers References: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> <499f895c-d614-86bd-2371-a6dd3ac349d7@digiware.nl> X-Mailer: Apple Mail (2.3654.60.0.2.21) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 17:48:44 -0000 --Apple-Mail=_D7ACBEB2-C3A7-4196-B4EC-D6DB66633CD0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Well, -std=3Dc++20 even, it is that new. :) That said, it's always hazardous to rely on experimental features, they = are effectively unsupported. As shown on e.g. cppreference.com, you can use an equivalent function = that looks like: auto old_size =3D c.size(); for (auto i =3D c.begin(), last =3D c.end(); i !=3D last; ) { if (pred(*i)) { i =3D c.erase(i); } else { ++i; } } -Dimitry > On 20 Mar 2021, at 16:22, Alan Somers wrote: >=20 > I'm just guessing, but I think you should remove the "experimental" = and > build with -std=3Dc++17 . > -Alan >=20 > On Sat, Mar 20, 2021 at 9:06 AM Willem Jan Withagen = wrote: >=20 >> On 20-3-2021 15:46, Alan Somers wrote: >>=20 >> It looks like it's in there. What code are you trying that doesn't = work? >>=20 >> Hi Alan, >>=20 >> I thought so too, but all tries last 2 weeks did not result into = anything >> that got it compiling... >> But could be that I did not try hard enough, real work is pulling a = lot >> atm. >>=20 >> Code is at: >>=20 >> = https://github.com/dillaman/ceph/blob/138d71fb0635682510cadda8e4ad5aaab3f3= 9e44/src/librbd/api/Trash.cc#L299 >>=20 >> Thanx, >> --WjW >>=20 >>=20 >>> grep erase_if /usr/include/c++/v1/map >> void erase_if(map& c, Predicate pred); = // >> C++20 >> void erase_if(multimap& c, Predicate = pred); >> // C++20 >> void erase_if(map<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate = __pred) >> { __libcpp_erase_if_container(__c, __pred); } >> void erase_if(multimap<_Key, _Tp, _Compare, _Allocator>& __c, = _Predicate >> __pred) >> { __libcpp_erase_if_container(__c, __pred); } >>=20 >> On Sat, Mar 20, 2021 at 8:39 AM Willem Jan Withagen via = freebsd-hackers < >> freebsd-hackers@freebsd.org> wrote: >>=20 >>> Hi, >>>=20 >>> [ Trying this on FBSD 12.2 ] >>>=20 >>> In the Ceph code new code uses std::map::erase_if. >>> Which is in Linux imported from >>>=20 >>> Anybody suggestions on libraries to get something matching?? >>>=20 >>> Thanx, >>> --WjW >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org >>> " >>>=20 >>=20 >>=20 > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org" --Apple-Mail=_D7ACBEB2-C3A7-4196-B4EC-D6DB66633CD0 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCYFY1cgAKCRCwXqMKLiCW o0K7AKDRg+ynTANYSuoru0z7AvijhLXzXwCgujVObtyYtPaUyg19GqkSVCRlFhI= =ijzk -----END PGP SIGNATURE----- --Apple-Mail=_D7ACBEB2-C3A7-4196-B4EC-D6DB66633CD0-- From owner-freebsd-hackers@freebsd.org Sat Mar 20 18:13:32 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 183A25B1002 for ; Sat, 20 Mar 2021 18:13:32 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2pmC1dPFz4qNW for ; Sat, 20 Mar 2021 18:13:31 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from [10.0.10.15] (unknown [10.0.10.15]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 535243C659 for ; Sat, 20 Mar 2021 11:13:24 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pinyon.org; s=dkim; t=1616264004; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eMi9jZ6dkquVUcWvbb7g+U9fqHyZsaDgv+94TuCX2Rw=; b=ilngq5pkUljwBUSMv9dOrSgpzVjC32TXeeDIjIIzwq7qrIhlmkFXM6iTT8wcVKcLgCkiqL xdkMJFf3eRXMklGLz5GrW73K7dm7DN1ipwXa8093yHBEPF1ilssqcConv8HT5gcF6HjMjR rWwn3wVJtXMEb4CwKSgASGVmfhB+upI= Subject: Re: Looking for std::map::erase_if To: "freebsd-hackers@freebsd.org" References: <941ef2dc-e6e1-bd30-0533-f6789b1463b5@digiware.nl> <499f895c-d614-86bd-2371-a6dd3ac349d7@digiware.nl> <9125B9BA-5B64-46AD-AB61-032889B0BE82@FreeBSD.org> From: "Russell L. Carter" Message-ID: <2df9f15b-2ef7-268f-7299-e2f7cc7ad4b2@pinyon.org> Date: Sat, 20 Mar 2021 11:13:23 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <9125B9BA-5B64-46AD-AB61-032889B0BE82@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.10 X-Rspamd-Server: h2 X-Rspamd-Queue-Id: 4F2pmC1dPFz4qNW X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pinyon.org header.s=dkim header.b=ilngq5pk; dmarc=none; spf=pass (mx1.freebsd.org: domain of rcarter@pinyon.org designates 65.101.20.170 as permitted sender) smtp.mailfrom=rcarter@pinyon.org X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[pinyon.org:s=dkim]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[65.101.20.170:from:127.0.2.255]; DMARC_NA(0.00)[pinyon.org]; DKIM_TRACE(0.00)[pinyon.org:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[65.101.20.170:from]; ASN(0.00)[asn:209, ipnet:65.101.0.0/18, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2021 18:13:32 -0000 On 3/20/21 10:48 AM, Dimitry Andric wrote: > Well, -std=c++20 even, it is that new. :) > > That said, it's always hazardous to rely on experimental features, they are effectively unsupported. > > As shown on e.g. cppreference.com, you can use an equivalent function that looks like: > > auto old_size = c.size(); > for (auto i = c.begin(), last = c.end(); i != last; ) { > if (pred(*i)) { > i = c.erase(i); > } else { > ++i; > } > } -std=c++20 is the way I would go to future proof, as then eg erase_if(std::map) is no longer experimental. The potential downside is then dealing with other oddball usages that are deprecated in c++20 (or c++17, c++14). If you fix these upstream might be receptive to patches. One other detail is the switch for slightly older clang++ or g++ is -std=c++2a, not -std=c++20. Dimitry is right, cppreference.com is your friend for this. Very easy to google your problem method/class and get to exactly what you need in terms of std compatibility. Russell > -Dimitry > >> On 20 Mar 2021, at 16:22, Alan Somers wrote: >> >> I'm just guessing, but I think you should remove the "experimental" and >> build with -std=c++17 . >> -Alan >> >> On Sat, Mar 20, 2021 at 9:06 AM Willem Jan Withagen wrote: >> >>> On 20-3-2021 15:46, Alan Somers wrote: >>> >>> It looks like it's in there. What code are you trying that doesn't work? >>> >>> Hi Alan, >>> >>> I thought so too, but all tries last 2 weeks did not result into anything >>> that got it compiling... >>> But could be that I did not try hard enough, real work is pulling a lot >>> atm. >>> >>> Code is at: >>> >>> https://github.com/dillaman/ceph/blob/138d71fb0635682510cadda8e4ad5aaab3f39e44/src/librbd/api/Trash.cc#L299 >>> >>> Thanx, >>> --WjW >>> >>> >>>> grep erase_if /usr/include/c++/v1/map >>> void erase_if(map& c, Predicate pred); // >>> C++20 >>> void erase_if(multimap& c, Predicate pred); >>> // C++20 >>> void erase_if(map<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate __pred) >>> { __libcpp_erase_if_container(__c, __pred); } >>> void erase_if(multimap<_Key, _Tp, _Compare, _Allocator>& __c, _Predicate >>> __pred) >>> { __libcpp_erase_if_container(__c, __pred); } >>> >>> On Sat, Mar 20, 2021 at 8:39 AM Willem Jan Withagen via freebsd-hackers < >>> freebsd-hackers@freebsd.org> wrote: >>> >>>> Hi, >>>> >>>> [ Trying this on FBSD 12.2 ] >>>> >>>> In the Ceph code new code uses std::map::erase_if. >>>> Which is in Linux imported from >>>> >>>> Anybody suggestions on libraries to get something matching?? >>>> >>>> Thanx, >>>> --WjW >>>> _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >>>> " >>>> >>> >>> >> _______________________________________________ >> freebsd-toolchain@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain >> To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe@freebsd.org" >