From owner-freebsd-hackers@freebsd.org Sun Aug 6 07:18:40 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D020DC8A72 for ; Sun, 6 Aug 2017 07:18:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5A697683A; Sun, 6 Aug 2017 07:18:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1deFpR-0004bj-FC; Sun, 06 Aug 2017 10:18:25 +0300 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: autos and /net problem Message-Id: <744F5E6C-0CD7-47E0-A744-7332751D4305@cs.huji.ac.il> Date: Sun, 6 Aug 2017 10:18:24 +0300 Cc: =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= To: Freebsd hackers list X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 07:18:40 -0000 hi, on the server I have exported /h/x and /h/x/y, both are zfs file = systems, showmount -E =E2=80=98server-host=E2=80=99 reports /h/x/y /h/x but autofs only mounts /h/x but not /h/x/y is there a solution to this? thanks, danny From owner-freebsd-hackers@freebsd.org Sun Aug 6 14:26:27 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 880BCDAE8B5 for ; Sun, 6 Aug 2017 14:26:27 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BBCA2DDB for ; Sun, 6 Aug 2017 14:26:26 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id v76EFcbq062733 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 6 Aug 2017 16:15:38 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: puchar.net: Host puchar-wojtek-router.vpn.intra [10.0.224.34] claimed to be wojtek.intra Received: from wojtek.intra (localhost [127.0.0.1]) by wojtek.intra (8.15.2/8.15.2) with ESMTP id v76EFXdR010443; Sun, 6 Aug 2017 16:15:33 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by wojtek.intra (8.15.2/8.15.2/Submit) with ESMTP id v76EFSpL010440; Sun, 6 Aug 2017 16:15:28 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: wojtek.intra: wojtek owned process doing -bs Date: Sun, 6 Aug 2017 16:15:28 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@wojtek.intra To: Eric McCorkle cc: freebsd-hackers@freebsd.org Subject: Re: nested GPT In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 14:26:27 -0000 > Please note that the boot loaders are unable to handle nested partition I don't need this. > schemes. If you have any data necessary for the initial boot on such a > partition, it won't work. > > On 07/29/2017 08:30, Oliver Pinter wrote: >> On 7/29/17, Wojciech Puchar wrote: >>> i have GPT partitioned SSD, and some partitions are used for bhyve virtual >>> disk containing windows - itself GPT partitioned. >>> >>> whenbhyve is stopped geom doesn't look at this GPT partitioned partition. >>> ggatel is a workaround but can it be changed so nested GPT partitions will >>> work? >> >> Take a look at geom_map(4). >> >>> _______________________________________________ >>> 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-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-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 Mon Aug 7 00:11:46 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B75BDD2753 for ; Mon, 7 Aug 2017 00:11:46 +0000 (UTC) (envelope-from Keith.Owens2@dell.com) Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.dell-outbound.iphmx.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 263B473522 for ; Mon, 7 Aug 2017 00:11:45 +0000 (UTC) (envelope-from Keith.Owens2@dell.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1502064598; x=1533600598; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=rs6G2o4oOZkx+766YEyoFBYy9viFcquj2DXb5Gwckvo=; b=rZ4G5GLyWAqbQwzMqlZbRi0aCFsWguhZciR0x6c3PAS/2U3L1Jc4vNW9 AAWymRAMqhzseDmB2I3eaan1F1b2m9El+9HJiI0elzmFkpXXUeT4cCQDj A+m2UVT++YO5hPimvvGlYhBEPgYVMybi+NIlb1MoE6lKTlDd4Czbfvno5 4=; Received: from esa1.dell-outbound2.iphmx.com ([68.232.153.201]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Aug 2017 19:02:49 -0500 From: "Owens, Keith" Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa1.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Aug 2017 05:52:36 +0600 Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v7703Hj1006000 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 6 Aug 2017 20:03:18 -0400 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com v7703Hj1006000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=isilon.com; s=jan2013; t=1502064198; bh=7hng1dY7JKTcSoDAVRfm0zABnCg=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ZU/sWpwaPzn8UXHttTSz/dWIvJbnlAZEJXZSEfdqV630PXqwgkhJfcdO0nSm44vBv xCeMhk+gjfqhx9U8REsCz8/x2UNAh8nCaeJWp1/im3eG3PUTR7MpX4rbbI5YZwaxn+ /J0v4V0wCW3zFVaoxCbabE1gD7LFpoAhPDDdPQwM= X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com v7703Hj1006000 Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd54.lss.emc.com (RSA Interceptor) for ; Sun, 6 Aug 2017 20:03:00 -0400 Received: from MXHUB102.corp.emc.com (MXHUB102.corp.emc.com [10.253.58.15]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v77032co001115 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 6 Aug 2017 20:03:03 -0400 Received: from MX202CL01.corp.emc.com ([fe80::401b:e935:5cb1:a681]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0352.000; Sun, 6 Aug 2017 20:03:02 -0400 To: "freebsd-hackers@freebsd.org" Subject: Writing a GEOM class, threads that can or cannot sleep Thread-Topic: Writing a GEOM class, threads that can or cannot sleep Thread-Index: AdMPEIjWIJjYg4smSveLg5AfG9EQsQ== Date: Mon, 7 Aug 2017 00:03:01 +0000 Message-ID: <0A22297308D147479E18AA1807A03807017CD4A8@MX202CL01.corp.emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.32.243.43] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com X-RSA-Classifications: public X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 00:11:46 -0000 Looking at https://www.freebsd.org/doc/en/articles/geom-class/article.html,= section 4.7.=0A= =0A= "The event functions are" ... "These functions are called from the g_down k= ernel thread and there can be no sleeping in this context".=0A= =0A= Correct me if I'm wrong, but only the start event goes via g_down.=0A= dumpconf, orphan, spoiled events go via g_event which can sleep.=0A= access can be called from any code on any thread (including g_down) so it m= ust not sleep.=0A= =0A= What is the process for updating articles?=0A= From owner-freebsd-hackers@freebsd.org Tue Aug 8 08:46:39 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9516DCC794 for ; Tue, 8 Aug 2017 08:46:39 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from know-smtprelay-omc-8.server.virginmedia.net (know-smtprelay-omc-8.server.virginmedia.net [80.0.253.72]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5ABED76422 for ; Tue, 8 Aug 2017 08:46:38 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from [192.168.1.5] ([86.10.211.13]) by know-smtprelay-8-imp with bizsmtp id uYlR1v0060HtmFq01YlR7f; Tue, 08 Aug 2017 09:45:25 +0100 X-Originating-IP: [86.10.211.13] X-Authenticated-User: J.deBoynePollard-newsgroups@NTLWorld.COM X-Spam: 0 X-Authority: v=2.1 cv=APW+KdU1 c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=2rVjqWD_AAAA:8 a=itly7gIdAAAA:8 a=WPrzpzyKt5dPABNCQWUA:9 a=QEXdDO2ut3YA:10 a=Y_mOOdSlYPkA:10 a=cdw2RfX-_zcA:10 a=-FEs8UIgK8oA:10 a=NWVoK91CQyQA:10 a=ULaUcM2Ibn9MdPUUwucP:22 a=1RpNR2E4bTkVPcsa2RFZ:22 Subject: djbwares version 6 To: Debian users , FreeBSD Hackers , Supervision References: <736737774.3548811.1490898899979.JavaMail.open-xchange@oxbe11.tb.ukmail.iss.as9143.net> From: Jonathan de Boyne Pollard Message-ID: Date: Tue, 8 Aug 2017 09:45:24 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <736737774.3548811.1490898899979.JavaMail.open-xchange@oxbe11.tb.ukmail.iss.as9143.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1502181925; bh=KiYIPU8HN9WlBpYvkCz/bOTpmM5rzSLoBAj8LqS9mSM=; h=Subject:To:References:From:Date:In-Reply-To; b=nSbChjkcCf0K0nvER/gyxDdlyOrp1QYZJBb0jzUO6wbizvQthPgs1Ktc8NnZAs1Ti 0UqjU3QIJ/UrA5jbT7RetKhUjzqGwVeDlWEeX2S2Y6kGgRmLVjO2wtORRUOqVbYZXS i/BB+SUb0Jl2zvM9GDWh/NcuLqaSuZlFpDo5DuZ62+DhTuy+xDzr6srmmrzXfPheGA 5OSic78AFcqZD++IBiCER8zzlsr3JoePb2hFMol96VVlbg0PW5qIuQauAlxWyUxBQe DWNVhSTwtSN/16ejIgWbes2qaRM2tGiLjIsyTLqJsE6YJsj4M6d2hjviBSxDqXraWM syWTu7Pv4tApw== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 08:46:40 -0000 djbwares is now at version 6. * http://jdebp.eu./Softwares/djbwares/ * http://jdebp.info./Softwares/djbwares/ The main changes here are in dnscache and ftpd. dnscache now has a built-in AAAA resource record for localhost, like it already had a built-in A resource record. I've slightly improved the way that it caches AAAA resource record sets, to match the way that it was handling A resource record sets. And it now caches SOA resource records. There are also some minor improvements to the logging to decode SRV, A, and AAAA records rather than print them in raw hexadecimal format. The changes to ftpd were motivated by my pointing several WWW browsers at a publicfile FTP site and discovering that the WWW browsers adhere to the RFCs far less than they used to at the turn of the century. You can read some of the saddening discoveries in the Hall of Shame. I have enhanced publicfile ftpd to support OPTS, FEAT, SIZE, EPSV, and HOST; to interoperate better with some faulty FTP ALGs that cannot cope with an FTP server that one does not need to log in to; to interoperate better with some faulty WWW browsers that misuse CWD as a type testing mechanism; and to log things more clearly in order to diagnose such faults from server logs. HOST support means that ftpd supports virtual hosting on FTP, which is explained in the manual, although it is hard to find any FTP client that employs this. * http://jdebp.eu./FGA/web-browser-ftp-hall-of-shame.html * http://jdebp.info./FGA/web-browser-ftp-hall-of-shame.html A further minor addition is a host command, a subset of the host commands from ISC and from KnotDNS that uses the same DNS client library from djbdns as all of the other djbdns query tools do. Of course, the conventional djbdns client tools have a simpler syntax and more regular behaviours than the host command, and are preferable. Moreover, the subset excludes rarities that djbdns has never supported, such as non-IN class queries. From owner-freebsd-hackers@freebsd.org Wed Aug 9 08:12:26 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44BE2DC61DC for ; Wed, 9 Aug 2017 08:12:26 +0000 (UTC) (envelope-from list@execve.net) Received: from lax012.relay.arandomserver.com (lax012.relay.arandomserver.com [198.252.106.48]) (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 0EF32671E4 for ; Wed, 9 Aug 2017 08:12:25 +0000 (UTC) (envelope-from list@execve.net) Received: from sng001.hawkhost.com ([119.81.196.36]) by se003.arandomserver.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dfL93-0002qB-En for freebsd-hackers@freebsd.org; Wed, 09 Aug 2017 02:11:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=execve.net; s=default; h=Content-Type:To:Subject:Message-ID:Date:From:MIME-Version: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=yEODKYFwBzS+9jYBRXxBsHSL28z6HM70+jEXgdRt1tE=; b=llMGiAEHDDZZzDYN1at9lg/VFM o1DlKnIt3Fl8z92Qjp01VGllHq+B6P+PBot+KF9RcYQtuCD8avItBtBlcoXEC2SAcBC+k1YHfAfjy xBHyD7CPQfsW37ypb/3QtxvDE; Received: from mail-vk0-f44.google.com ([209.85.213.44]:36712) by sng001.hawkhost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dfL8z-0004eG-EU for freebsd-hackers@freebsd.org; Wed, 09 Aug 2017 15:11:05 +0800 Received: by mail-vk0-f44.google.com with SMTP id u133so22515054vke.3 for ; Wed, 09 Aug 2017 00:11:05 -0700 (PDT) X-Gm-Message-State: AHYfb5gmY9xpAAfoln9s/Sts4i/nRP0uwFnWrj6AVtLbQK6dYb5WDiUV 9i4SAI/XSrDEQ7w35gv4ItQcwLE3eQ== X-Received: by 10.31.99.7 with SMTP id x7mr4575770vkb.91.1502262663193; Wed, 09 Aug 2017 00:11:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.40.136 with HTTP; Wed, 9 Aug 2017 00:11:02 -0700 (PDT) From: Gautam Date: Wed, 9 Aug 2017 12:41:02 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Freebsd 11.0 - system freeze on intensive I/O To: freebsd-hackers@freebsd.org X-Originating-IP: 119.81.196.36 X-SpamExperts-Domain: sng001.hawkhost.com X-SpamExperts-Username: relay Authentication-Results: arandomserver.com; auth=pass (login) smtp.auth=relay@sng001.hawkhost.com X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.17) X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZiEh/Q2y0dK8jSMLTE55fwqH0Nprjby6XDb qzVlIOQ03kAwPN4M+BNtq20Hh3O6Az9ismS84NPFas3IWADbmzJ9CZryIsNFvaBrlzs70sT7iKmx j3Zz/WM/IwRyPjIHIwBUob/yW30DOJj+Kss2vDc/5SEjKwPh0WkSDfiKvcISYh5e973vehgRRMJd d1x498TEPIrJLOIiaQMIoqwZC1nFGzcWMr0czofRVh8rMXrt/SyLxLEJIkbWABkyXJwBVLal3W+/ PI81P534n3yak4n7EfJL2hMI4yCDSSr/HxDyN5bD8YyxjFtJAz2loLb4we0tFPPhpWPZ07PAOr0y wYIXuCj9wj08m7429e2ZOl/ZXvNM2/zURZVxzSV/eszOttj6AVIvY+ILsI7br1ka/ZVMZg0RCmXs LQSJNPsmBKPgn+7xA5exucQFZoY/QWsFvfiVu34H+eqH7iWBpUrKGrffGcXZKnwjnRMG9jJ/knTt +XiA50wwIMuM3BDtnoPm4HpIizaH26GaoEDwTtnQE6q4ZRNP3CPS3YZT5ODGEA+uOpLZY+4z/dwR ocCZGdc1cl9f9x/pKLS918QV+MmO1bAAEgjXIny51RJ3yyIOVX71wEukYspuIwswojsoiyB8OuXo nV+E7OMXRvgtdyMlnmWi9uF4/xGeHumbSXx1nykjkg3q5Go+y6UPrDLg9O+nbQEat0d9vQKDQuJS Y6oEFeAiQnTIgDfxZ2/WGqYvyOVteVOdo6Dvr8fbMJVJ9/erL6/4IvMfhB2h/z0m0D607pH+pWX8 JH76UCDHe+VBXhtjrZr9RUQzcLUz45TvUuLctG5L8ZHLV0zHQOMuxVjpDkV6 X-Report-Abuse-To: spam@se001.arandomserver.com Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 08:12:26 -0000 Hi, I raised this topic on freebsd-questions where I suspect a bug caused due to swapfile usage on FreeBSD. You could read details in the below thread, but summary is that with using a swapfile (not a swap partition) the system freezes on some single process intensive I/O. This is 100% reproducible. http://marc.info/?l=freebsd-questions&m=150088763825675&w=2 I raised a PR - 220971 ; but there are no backtraces / logs etc. that could possibly help. I would like to help narrow this down, but do not know how. Any suggestions on how to debug a system freeze and what I need to do ? I could then try to reproduce this and collect the needed information - traces etc. Thanks, Gautam From owner-freebsd-hackers@freebsd.org Wed Aug 9 08:35:39 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83B26DC6A2D for ; Wed, 9 Aug 2017 08:35:39 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5467D68078 for ; Wed, 9 Aug 2017 08:35:39 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: by mail-pf0-x22f.google.com with SMTP id h68so25170279pfk.0 for ; Wed, 09 Aug 2017 01:35:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ieTLnmq0/h/BnRk1KkSNimYqFprQQZLXZQ3aZHEW5Qw=; b=eq5TRfAsGAq1zsNefHx+6A3hPt0NpnGHtvrWRMgfPLmXAvtkkGBByKRTBKtAHaeEmS UGY+Z4oReSCkXN54koX7FGJt2JgNbCIxNO31QBFpL/0qny2lzx4I1G8o0b3Q2CuFF98F WfN9ZpBtItrC0366djtj7kjc/D8JnWjeM1/QsmWjCyAzggxoQw9tHTPCvzqA4m2C6m2i kGaBTzyHhiECSoU2XFL94JDdroa6KwZFjoKOmeCKLowG/t6abznSceUF7p28Ah5oGTh3 5S6lMJ8sbpp4RYm2lDV2/oUcXkLZx51wmgnm+11FBmThJIMF2qEQcTzYFIRoUXbJ3wHP r2WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ieTLnmq0/h/BnRk1KkSNimYqFprQQZLXZQ3aZHEW5Qw=; b=jL6+KIrM9aZMzorm0cBTLdZS1ZdYt9YpTETUbaSIFO4JkMJvH2xrl8UWuYcnPL42RW 8Ox2AisVkvdbidaZuZ/pfR0QpRmwPmbcOMKxUBq7F6W1Icq25hUAVbYPZDHzw3Cl5dPX iUFGrR8/A2orqzYssEDWJ5tpZ2hxxK0liQ7m4m2ia3bG9Ch4jU7/qutif9hw11tgEycF mAGNuCgoF6YHoik43o5ET+DoEgI2ItbzW+Od6mUiHjnOBZUdarE2pmWytsXC66zw9Vov UQS3vUx56HfvQxVnMt9lmGRxL55t0nu3yxcTDhrl2Z0MP4wywAQDMRqbigWy1cNUh901 AbIQ== X-Gm-Message-State: AHYfb5jzJVMuYK2q8IG0qDKOl9j/IgzGCak1flSfzJ/EfbNtDIuyl7rV OzTCWy0h38EFcFkdiosIzjkyqQr1sg== X-Received: by 10.98.109.65 with SMTP id i62mr7449632pfc.309.1502267738732; Wed, 09 Aug 2017 01:35:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.166.235 with HTTP; Wed, 9 Aug 2017 01:35:08 -0700 (PDT) In-Reply-To: References: From: Gleb Popov <6yearold@gmail.com> Date: Wed, 9 Aug 2017 11:35:08 +0300 Message-ID: Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: freebsd-hackers Cc: Gautam Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 08:35:39 -0000 On Wed, Aug 9, 2017 at 10:11 AM, Gautam wrote: > Hi, > > I raised this topic on freebsd-questions where I suspect a bug caused due > to swapfile usage on FreeBSD. > > You could read details in the below thread, but summary is that with using > a swapfile (not a swap partition) the system freezes on some single process > intensive I/O. This is 100% reproducible. > > http://marc.info/?l=freebsd-questions&m=150088763825675&w=2 > > I raised a PR - 220971 ; but there are no backtraces / logs etc. that could > possibly help. > > I would like to help narrow this down, but do not know how. Any suggestions > on how to debug a system freeze and what I need to do ? I could then try to > reproduce this and collect the needed information - traces etc. > > Thanks, > Gautam > _______________________________________________ > 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" > I also see symptoms you mentioned on my system, but I'm using ZFS. But my system is very ancient, so I've been taking it as normal behavior. Like you said, intensive disk IO turns OS completely unresponsive, except pings. From owner-freebsd-hackers@freebsd.org Wed Aug 9 08:46:06 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB803DC6E3B for ; Wed, 9 Aug 2017 08:46:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2772C6870F for ; Wed, 9 Aug 2017 08:46:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v798jksC023294 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 9 Aug 2017 11:45:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v798jksC023294 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v798jkqw023293; Wed, 9 Aug 2017 11:45:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 9 Aug 2017 11:45:46 +0300 From: Konstantin Belousov To: Gautam Cc: freebsd-hackers@freebsd.org Subject: Re: Freebsd 11.0 - system freeze on intensive I/O Message-ID: <20170809084546.GQ1700@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 08:46:06 -0000 On Wed, Aug 09, 2017 at 12:41:02PM +0530, Gautam wrote: > Hi, > > I raised this topic on freebsd-questions where I suspect a bug caused due > to swapfile usage on FreeBSD. > > You could read details in the below thread, but summary is that with using > a swapfile (not a swap partition) the system freezes on some single process > intensive I/O. This is 100% reproducible. Also this is expected. > > http://marc.info/?l=freebsd-questions&m=150088763825675&w=2 > > I raised a PR - 220971 ; but there are no backtraces / logs etc. that could > possibly help. See https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > I would like to help narrow this down, but do not know how. Any suggestions > on how to debug a system freeze and what I need to do ? I could then try to > reproduce this and collect the needed information - traces etc. > > Thanks, > Gautam > _______________________________________________ > 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 Wed Aug 9 09:24:03 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CEE6DC7E56 for ; Wed, 9 Aug 2017 09:24:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-90.reflexion.net [208.70.210.90]) (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 CFEDD6A49F for ; Wed, 9 Aug 2017 09:24:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 31591 invoked from network); 9 Aug 2017 09:19:05 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 9 Aug 2017 09:19:05 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Wed, 09 Aug 2017 05:17:20 -0400 (EDT) Received: (qmail 20517 invoked from network); 9 Aug 2017 09:17:20 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 9 Aug 2017 09:17:20 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id C3D15EC8676; Wed, 9 Aug 2017 02:17:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Freebsd 11.0 - system freeze on intensive I/O From: Mark Millard In-Reply-To: Date: Wed, 9 Aug 2017 02:17:19 -0700 Cc: freebsd-hackers , Gautam Content-Transfer-Encoding: quoted-printable Message-Id: <10B7A852-29E9-421A-A4C6-8CC21507E201@dsl-only.net> References: To: Gleb Popov <6yearold@gmail.com> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 09:24:03 -0000 On 2017-Aug-9, at 1:35 AM, Gleb Popov <6yearold at gmail.com> wrote: > On Wed, Aug 9, 2017 at 10:11 AM, Gautam wrote: >=20 >> Hi, >>=20 >> I raised this topic on freebsd-questions where I suspect a bug caused = due >> to swapfile usage on FreeBSD. >>=20 >> You could read details in the below thread, but summary is that with = using >> a swapfile (not a swap partition) the system freezes on some single = process >> intensive I/O. This is 100% reproducible. >>=20 >> http://marc.info/?l=3Dfreebsd-questions&m=3D150088763825675&w=3D2 >>=20 >> I raised a PR - 220971 ; but there are no backtraces / logs etc. that = could >> possibly help. >>=20 See bugzilla 206048 for some more information: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206048 >> I would like to help narrow this down, but do not know how. Any = suggestions >> on how to debug a system freeze and what I need to do ? I could then = try to >> reproduce this and collect the needed information - traces etc. It is a long term, known problem, not new with 11.x as I understand. No reasonable fix is known as I understand: it is not a coding error but a design property. >> Thanks, >> Gautam >> _______________________________________________ >> 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 > I also see symptoms you mentioned on my system, but I'm using ZFS. But = my > system is very ancient, so I've been taking it as normal behavior. = Like you > said, intensive disk IO turns OS completely unresponsive, except = pings. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Wed Aug 9 09:53:49 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 915F1DC860B for ; Wed, 9 Aug 2017 09:53:49 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (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 249E96B2B8 for ; Wed, 9 Aug 2017 09:53:48 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v799qpGQ098375 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 9 Aug 2017 11:52:51 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: list@execve.net Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v799qgae079027 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 9 Aug 2017 16:52:42 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: Gautam , freebsd-hackers@freebsd.org References: From: Eugene Grosbein Message-ID: <598ADB65.8060701@grosbein.net> Date: Wed, 9 Aug 2017 16:52:37 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 09:53:49 -0000 09.08.2017 14:11, Gautam пишет: > Hi, > > I raised this topic on freebsd-questions where I suspect a bug caused due > to swapfile usage on FreeBSD. > > You could read details in the below thread, but summary is that with using > a swapfile (not a swap partition) the system freezes on some single process > intensive I/O. This is 100% reproducible. > > http://marc.info/?l=freebsd-questions&m=150088763825675&w=2 > > I raised a PR - 220971 ; but there are no backtraces / logs etc. that could > possibly help. > > I would like to help narrow this down, but do not know how. Any suggestions > on how to debug a system freeze and what I need to do ? I could then try to > reproduce this and collect the needed information - traces etc. Swapfile is definitely broken in supported FreeBSD releases, it hangs the system. The only known workaround (to me) is not using it. From owner-freebsd-hackers@freebsd.org Wed Aug 9 10:38:07 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4803DC9323 for ; Wed, 9 Aug 2017 10:38:07 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (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 578496C70E for ; Wed, 9 Aug 2017 10:38:06 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v79AbZhT098682 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 9 Aug 2017 12:37:35 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: kostikbel@gmail.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v79AbW5V092487 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 9 Aug 2017 17:37:32 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: Konstantin Belousov , Gautam References: <20170809084546.GQ1700@kib.kiev.ua> Cc: freebsd-hackers@freebsd.org From: Eugene Grosbein Message-ID: <598AE5E6.3070209@grosbein.net> Date: Wed, 9 Aug 2017 17:37:26 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20170809084546.GQ1700@kib.kiev.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 10:38:07 -0000 09.08.2017 15:45, Konstantin Belousov wrote: > On Wed, Aug 09, 2017 at 12:41:02PM +0530, Gautam wrote: >> Hi, >> >> I raised this topic on freebsd-questions where I suspect a bug caused due >> to swapfile usage on FreeBSD. >> >> You could read details in the below thread, but summary is that with using >> a swapfile (not a swap partition) the system freezes on some single process >> intensive I/O. This is 100% reproducible. > Also this is expected. It worked reliably at least for 6.x/i386 versions I was forced to perform re-partitioning acrobatics for a couple of remote FreeBSD 9.x production systems to increase swap partition size to be able to do source upgrade after failed attempts to use swapfile over UFS, it hangs. From owner-freebsd-hackers@freebsd.org Wed Aug 9 11:02:04 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C739DC9C66 for ; Wed, 9 Aug 2017 11:02:04 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16B4D6D3E5 for ; Wed, 9 Aug 2017 11:02:04 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id 16so34065286qtz.4 for ; Wed, 09 Aug 2017 04:02:04 -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=YENj6uk4gsOgwFDgO11wgSKLWbJ2siIBk18XZqTc5JQ=; b=sdfF3YmU5UF+SSZEyc4BqwoSnjOPW75Qqfelcjo9HNe5HVIkD4WUKKIoPvy4KQKmtJ mVScTtRlDEbvog7VZcNhHhOy59Ne2E7SBjcpMmGKOXw4AzXKM4dHyo2bTfm0an+J1oSn sqn3UpACqRkn+958pr4oL14X6LfsQFQOpgQLWjnj/UbUfCbngGBJS9xhHRUqWKp/eVO3 9YQH7LVvUPR3vJSkDDZMw4D5mGe6wovWrtC0yJPIs6UVbCwabygvdFfBTjrYsNX8DnzZ AqyXJqp7qSuErTi/jsB96a7iCr0bu/YHXJ6qmnHSwVpJoyvG8k/6gV5tYyF7xunk55Qv qAsA== 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=YENj6uk4gsOgwFDgO11wgSKLWbJ2siIBk18XZqTc5JQ=; b=UxS2V8J4xKnnuN4myxzJ40qxYbCIY3EqTRXA4slsFGURTa2dPxFA+uhlG2s5RDK4JS P8oai4UQhdtTVVYvOEPeSLFfoYLqwXNZZ9ZxArADZxtb0gUx79iL1Kp3tRCtrw6aByJB 6JPWbhgXuxKf/6v19AT9Dcpp4rNUa6bxDXdA159BBXjhX/9XuCxdcyVQmpV41aVFckCG SrUA73BXT2M7/JWSWfJ07SuqgvlZgVUa//W5wgl7Z5MP5ys3aYiIVlFXadM3UpZts51p 6j/pi44RoU8j9Mon2Jt7EVKcZXD6KcQYI4jel1ec9hDZmSIFIiPWAkgIAdEwdO+WmbRN 7+RA== X-Gm-Message-State: AHYfb5gVwfzCjH8LB0+w4DD6XkhkiIC7wMsYlcB3ktPznLUMyi+cad6R qB1HGlaXM8RSui/TmEs5clS2ns2Dmfzogz4= X-Received: by 10.200.51.212 with SMTP id d20mr10296052qtb.204.1502276522819; Wed, 09 Aug 2017 04:02:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.39.180 with HTTP; Wed, 9 Aug 2017 04:02:02 -0700 (PDT) From: rahul gupta Date: Wed, 9 Aug 2017 16:32:02 +0530 Message-ID: Subject: Need Help regarding contribution to Free BSD Projects To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Wed, 09 Aug 2017 12:05:25 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 11:02:04 -0000 Hi Team, As I am working in Dell EMC in Isilon Product , and i want to contribute in Free BSD Open source projects as i love to do codning, My Area of interested is Data Structure and Algorithm and i have fond of learn system related coding. kindly request you help me how i can help in the development of free BSD OS and also help me out that i how can contribute to free BSD and what is smallest thigh from i can start to contribute. your valuable help and guidance are awaited.. -- Thanks & Regards Rahul Gupta Dell EMC Isilon Engineering Team +917200744656 From owner-freebsd-hackers@freebsd.org Wed Aug 9 13:46:04 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73736DCD745 for ; Wed, 9 Aug 2017 13:46:04 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4493472B8F for ; Wed, 9 Aug 2017 13:46:04 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: by mail-pg0-x22b.google.com with SMTP id y129so28321189pgy.4 for ; Wed, 09 Aug 2017 06:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Xcg3lgKP+EqdHL89m1q9nGiq3XXB3GjLhsku/BeWvsw=; b=TECCSLnJQyrXdH0wuKSAyEo4dZZBQCcslkQIMSNmqfCupddMPlbreFaq4wSo6GyGj0 bg7a4yJHjGzW/gLDHpjmvMSVOmMhyB4EAmpX7kIH0nBd8yV1HQRNNh7cAgOWyW+oD6Hw eizEcfqNSriuzXOcrvljzhvHrmmwxWJUwebajCp6gMBwWqjczqJxRqUEhtKK0uYgFHPh o3EAJAXBQibWjKkgD98bRxTXC3XE84OjInHzaL07OKt8PxIjb+sMSeicHC46NE7R+7U9 a1SE1V7gkiAkYqA7j0wvpqE/7zoMsk1y39lyeTbDqYyx21lSJDHl38vCs/nCjZSshZQs 9jUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Xcg3lgKP+EqdHL89m1q9nGiq3XXB3GjLhsku/BeWvsw=; b=PiUtWY/33mtFGUAAY5QyvF5A4Tq4ka2LvFkJUMN6+8JiZ8l/Gj6xjYgTihCx7TExRg thHD18QxGFOpaPCs6m+YeyQMqcPNLvhxXqM3uDKT5HTDbdXvmpfTNVutiKI+jLAq5KKt nlD8A72LR7MYIvtbwHcgyIpd7Wuk4x+8Or8dOYUs7e4RlRj+8fM0E1OjE9OXhRUxDiCM YBG9Ql/hC8hVD4PAxjWmDQXke+qtkHeBhg1Q2GLd9XsZbM9rS9YotqdfAZ5ondFaF4u1 +aKS9atdW+bhDifwcJiPN9evPtT+UOeVgYcPXdnnKnSMxRajZhooIQkDhzdoTxz6lXfT /yAQ== X-Gm-Message-State: AHYfb5jPzFHWg+RUmzdSlatGKUomkC9b/X/8X8iMpFR5rZR034UWBVn4 TCMKwLG9soywW8ysaJFSAHoX4K6HWg== X-Received: by 10.99.167.70 with SMTP id w6mr7617405pgo.17.1502286363476; Wed, 09 Aug 2017 06:46:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.166.235 with HTTP; Wed, 9 Aug 2017 06:45:33 -0700 (PDT) In-Reply-To: <598ADB65.8060701@grosbein.net> References: <598ADB65.8060701@grosbein.net> From: Gleb Popov <6yearold@gmail.com> Date: Wed, 9 Aug 2017 16:45:33 +0300 Message-ID: Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: freebsd-hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 13:46:04 -0000 On Wed, Aug 9, 2017 at 12:52 PM, Eugene Grosbein wrote= : > 09.08.2017 14:11, Gautam =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Hi, > > > > I raised this topic on freebsd-questions where I suspect a bug caused d= ue > > to swapfile usage on FreeBSD. > > > > You could read details in the below thread, but summary is that with > using > > a swapfile (not a swap partition) the system freezes on some single > process > > intensive I/O. This is 100% reproducible. > > > > http://marc.info/?l=3Dfreebsd-questions&m=3D150088763825675&w=3D2 > > > > I raised a PR - 220971 ; but there are no backtraces / logs etc. that > could > > possibly help. > > > > I would like to help narrow this down, but do not know how. Any > suggestions > > on how to debug a system freeze and what I need to do ? I could then tr= y > to > > reproduce this and collect the needed information - traces etc. > > Swapfile is definitely broken in supported FreeBSD releases, it hangs the > system. > The only known workaround (to me) is not using it. > > > _______________________________________________ > 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= " > I'm using swap on ZFS, and still see the problem, so this might not be tied to swapfile. From owner-freebsd-hackers@freebsd.org Wed Aug 9 14:04:32 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4530BDCDEB7 for ; Wed, 9 Aug 2017 14:04:32 +0000 (UTC) (envelope-from shivanshrai84@gmail.com) Received: from mail-ua0-f195.google.com (mail-ua0-f195.google.com [209.85.217.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 050667380F for ; Wed, 9 Aug 2017 14:04:31 +0000 (UTC) (envelope-from shivanshrai84@gmail.com) Received: by mail-ua0-f195.google.com with SMTP id k43so3928284uaf.1 for ; Wed, 09 Aug 2017 07:04:31 -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; bh=SIhBXsnRef/A4526OXPiE/xduUCVepQTlQv9low8p6g=; b=qMvr7fqjd8FP1ByrmPCopUalS8ahKOZfJ7ewJdT7moqj6Ip6wxF93x45oFKQo9PcMe ergzAP4lXwLA4iI4Z60tUQ1yGhPc1+wspn8IMuCz7Bn5pjuOZon4eBNp6lBPBMj7Xk4z +1XwApvRLuWwVV11K1c28+XhZ/pZzZBiFhwP/z/Uqk6u2Zo6Y0HgaZHPcr5tPqSjZaEe Y1qIvwpCHmTaAe38mIsc4kqZ7lZIDjugZzMjz6MhkluXubK7GYKC5aceZHFGccg+uMMX Jz/H2TKw8CYQ4+NwdoTGVxzLseEXjSN/7ainE36cRiCnZmYYU/wCV+g874ZFeEG/JHr8 gRiQ== X-Gm-Message-State: AHYfb5gqqtTW8wy+VIHDU7R1U+ZxsiaDOJxbvs/8EhwVbsrB1Hf+1pQ8 GsS5j9oCA7pST9fXhIU= X-Received: by 10.176.28.71 with SMTP id o7mr5072146uaj.38.1502285762228; Wed, 09 Aug 2017 06:36:02 -0700 (PDT) Received: from mail-ua0-f171.google.com (mail-ua0-f171.google.com. [209.85.217.171]) by smtp.gmail.com with ESMTPSA id y7sm1625528uah.48.2017.08.09.06.36.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Aug 2017 06:36:01 -0700 (PDT) Received: by mail-ua0-f171.google.com with SMTP id d29so28447928uai.2 for ; Wed, 09 Aug 2017 06:36:00 -0700 (PDT) X-Received: by 10.176.23.77 with SMTP id k13mr6158832uaf.128.1502285760751; Wed, 09 Aug 2017 06:36:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Shivansh Rai Date: Wed, 09 Aug 2017 13:35:50 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: rahul gupta , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 14:04:32 -0000 Hi Rahul, I can say that your interests greatly match with mine so I'd write here what I did when I first got introduced to FreeBSD. It is possible that you might find the following very easy as I'm a beginner :-) * I made my first contribution during Google Summer of Code '16. The project ideas proposed every year are very cool and I'd suggest having a look at some of the previous years' ideas as not all of them are taken up (you can also have a look at the previous projects). A good thing about them is that they have a mention of the difficulty level and the domain knowledge required to participate, so you can easily filter out the ones you might be interested in - https://wiki.freebsd.org/SummerOfCodeIdeas. * Look up the src tree and try to find a piece of code which interests you (for e.g. it may be a base utility, say ls). Read through the code to see how it works. It is a fun activity which I occasionally do. It is also possible that in the process you might come up with an improvement. * *Testing* I have come to realize that testing is a great way to explore and learn a lot very fast (according to me). Firstly, you get to study how things work. For e.g. if you want to perform testing of the TCP stack, you might first start off learning about how TCP works. Since it is very extensive, at a time you can pick up a single functionality (say, selective acknowledgements) and study it end to end after which you try to come up with ways of testing it. So you didn't study the entire theory behind TCP, but now you know how this specific functionality works very well. Then you proceed on with other functionalities and in some time you'll cover a lot of theory. Secondly, the process of coming up with ways to test a specific functionality proves to be a great (and fun) way to learn. And it is also a great way of applying what you just learnt. Last (but not the least) you are in luck if you come across a bug or an unexpected behavior! If you are interested in testing, I'd suggest having a look at the documentation of the FreeBSD testsuite: https://wiki.freebsd.org/TestSuite and also the TCP testsuite: https://github.com/freebsd-net/tcp-testsuite (I am only familiar with these, other members might add more to the list). * To start off contributing right away, I'd suggest having a look at some of these links: - https://wiki.freebsd.org/IdeasPage - https://bugs.freebsd.org/bugzilla/describecomponents.cgi - https://wiki.freebsd.org/JuniorJobs * Ask questions! The community members are extremely friendly (and highly experienced, so you get to learn something new everytime you ask). * Also, you can have a look at how some of the community members first started off (it is quite interesting): https://wiki.freebsd.org/HowWeGotHere . Over time I got to realize that the key is to always keep learning and enjoying the entire process. In these fields (and any CS field for that matter) you never get to stop being amazed by something new everyday. I think I'm starting to go off-topic so I'll stop. PS. I am relatively very new to the community (around only 2 years) so I'm sure the experienced and senior members will have some great and better advice to share. My apologies in advance if I wrote something wrong above. Hope this helps. Thank you for your interest! With best regards, Shivansh Rai https://wiki.freebsd.org/ShivanshRai On Wed, Aug 9, 2017 at 5:35 PM rahul gupta wrote: > Hi Team, > > As I am working in Dell EMC in Isilon Product , > and i want to contribute in Free BSD Open source projects as i love to do > codning, > My Area of interested is Data Structure and Algorithm and i have fond of > learn system related coding. > kindly request you help me how i can help in the development of free BSD OS > and > also help me out that i how can contribute to free BSD and what is smallest > thigh from i can start to contribute. > > your valuable help and guidance are awaited.. > > -- > Thanks & Regards > Rahul Gupta > Dell EMC Isilon Engineering Team > +917200744656 <+91%2072007%2044656> > _______________________________________________ > 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 Wed Aug 9 14:13:57 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59287DCE1E5 for ; Wed, 9 Aug 2017 14:13:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-90.reflexion.net [208.70.210.90]) (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 EBB1173CA1 for ; Wed, 9 Aug 2017 14:13:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19192 invoked from network); 9 Aug 2017 14:18:48 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 9 Aug 2017 14:18:48 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Wed, 09 Aug 2017 10:13:55 -0400 (EDT) Received: (qmail 9053 invoked from network); 9 Aug 2017 14:13:55 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 9 Aug 2017 14:13:55 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 7FD42EC8559; Wed, 9 Aug 2017 07:13:54 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Freebsd 11.0 - system freeze on intensive I/O From: Mark Millard In-Reply-To: Date: Wed, 9 Aug 2017 07:13:53 -0700 Cc: freebsd-hackers , Eugene Grosbein , Gautam Content-Transfer-Encoding: quoted-printable Message-Id: References: <598ADB65.8060701@grosbein.net> To: Gleb Popov <6yearold@gmail.com> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 14:13:57 -0000 On 2017-Aug-9, at 6:45 AM, Gleb Popov <6yearold at gmail.com> wrote: > On Wed, Aug 9, 2017 at 12:52 PM, Eugene Grosbein wrote: >=20 >> 09.08.2017 14:11, Gautam =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> Hi, >>>=20 >>> I raised this topic on freebsd-questions where I suspect a bug = caused due >>> to swapfile usage on FreeBSD. >>>=20 >>> You could read details in the below thread, but summary is that with >> using >>> a swapfile (not a swap partition) the system freezes on some single >> process >>> intensive I/O. This is 100% reproducible. >>>=20 >>> http://marc.info/?l=3Dfreebsd-questions&m=3D150088763825675&w=3D2 >>>=20 >>> I raised a PR - 220971 ; but there are no backtraces / logs etc. = that >> could >>> possibly help. >>>=20 >>> I would like to help narrow this down, but do not know how. Any >> suggestions >>> on how to debug a system freeze and what I need to do ? I could then = try >> to >>> reproduce this and collect the needed information - traces etc. >>=20 >> Swapfile is definitely broken in supported FreeBSD releases, it hangs = the >> system. >> The only known workaround (to me) is not using it. >=20 > I'm using swap on ZFS, and still see the problem, so this might not be = tied > to swapfile. Swap files on ZFS are also known to have the problem. Quoting bugzilla 206048's comment #7 (which is quoting an older list message): On 2017-Feb-13, at 7:20 PM, Konstantin Belousov = wrote on the freebsd-arm list: . . . swapfile write requires the write request to come through the filesystem write path, which might require the filesystem to allocate more memory and read some data. E.g. it is known that any ZFS write request allocates memory, and that write request on large UFS file might require allocating and reading an indirect block buffer to find the block number of the written block, if the indirect block was not yet read. As result, swapfile swapping is more prone to the trivial and = unavoidable deadlocks where the pagedaemon thread, which produces free memory, needs more free memory to make a progress. Swap write on the raw partition = over simple partitioning scheme directly over HBA are usually safe, while = e.g. zfs over geli over umass is the worst construction. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Wed Aug 9 14:01:37 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B29FDCDD13 for ; Wed, 9 Aug 2017 14:01:37 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33D617363B; Wed, 9 Aug 2017 14:01:37 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: by mail-qk0-x243.google.com with SMTP id d136so5693379qkg.3; Wed, 09 Aug 2017 07:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bED+kVKOWeAyoZ0SxTS7rReEBJMd0VHlM2xbyHJideI=; b=mU38libulmha8NO+B6RVg8cgkV+mM7z6IiFlMK12BxT1kOiOI2F8c35wpNayIc4vbD w3KPEMaUc59KtotihZKvYN5kVpDFvz4Gw/Iro5HPdzPjQG6hDfx/voAxT37eZ8KxoFyb LOIMVI9dbDtZEi6e20p+MJIrvuC34W7k88lDgHn1Tupt8yZv129xjNneD554PwPk6n+o 4wUlQV3b0wV5xigJwECurQm+YVC4C0uMapf1Yr1LKUw2HmGp8xYGtr5WmHxzjSY6CJdx UNqeHGlgwtv+jm7fqcBXC/5SeYpLBIEKVeZV7/X/ff7lvIw9uJU8s5f86zthRpVBsflt T7tA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bED+kVKOWeAyoZ0SxTS7rReEBJMd0VHlM2xbyHJideI=; b=XhRreRp4xone8RHaib6mu8YBA4awwr/z1dHKMBEU0m4j+kdeyOhXAi8JBeOtkSYdI3 AvpWIQPQYdrXwJhsMukEaXj60YA3NzXJRCg6Ql4cYI6UtBLKHU0dTrjQRWp1MdvM8Lv6 yPzKu5wIjZ2TFkX2VFB26VzjwICW/gb4Z2gDBege9ag2xP48LOo+PWKbIEF/kQ917jgS qvyTbpDA353TUbbmWDlpiKZQXjhcxKFjdDmiEwZ8uIHCrtSYgylk0RSWq8pE3RcKnQfD EkGT9/Eelid07sKuvUBqWV1bT3mh0+0s4LBvT/qX81tOb/sFFj4GA4VIDTbbmtS9icVf Wq0w== X-Gm-Message-State: AHYfb5gPgKwH2ckLLYvv2quKvQYYXedncgf976lfxu0ICOVav/6Qd6kj tB3WJo53x+8BiZnzM/EfJqi2JP+25aHY X-Received: by 10.55.39.82 with SMTP id n79mr10769668qkn.238.1502287295763; Wed, 09 Aug 2017 07:01:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.39.180 with HTTP; Wed, 9 Aug 2017 07:01:34 -0700 (PDT) Received: by 10.140.39.180 with HTTP; Wed, 9 Aug 2017 07:01:34 -0700 (PDT) In-Reply-To: References: From: rahul gupta Date: Wed, 9 Aug 2017 19:31:34 +0530 Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: Shivansh Rai Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Wed, 09 Aug 2017 14:27:01 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 14:01:37 -0000 This is great, thank you! On 09-Aug-2017 7:06 PM, "Shivansh Rai" wrote: > Hi Rahul, > > I can say that your interests greatly match with mine so I'd write here > what I did when I first got introduced to FreeBSD. It is possible that you > might find the following very easy as I'm a beginner :-) > > * I made my first contribution during Google Summer of Code '16. The > project ideas proposed every year are very cool and I'd suggest having a > look at some of the previous years' ideas as not all of them are taken up > (you can also have a look at the previous projects). A good thing about > them is that they have a mention of the difficulty level and the domain > knowledge required to participate, so you can easily filter out the ones > you might be interested in - https://wiki.freebsd.org/SummerOfCodeIdeas. > > * Look up the src tree and try to find a piece of code which interests you > (for e.g. it may be a base utility, say ls). Read through the code to see > how it works. It is a fun activity which I occasionally do. It is also > possible that in the process you might come up with an improvement. > > * *Testing* > I have come to realize that testing is a great way to explore and learn a > lot very fast (according to me). Firstly, you get to study how things work. > For e.g. if you want to perform testing of the TCP stack, you might first > start off learning about how TCP works. Since it is very extensive, at a > time you can pick up a single functionality (say, selective > acknowledgements) and study it end to end after which you try to come up > with ways of testing it. So you didn't study the entire theory behind TCP, > but now you know how this specific functionality works very well. Then you > proceed on with other functionalities and in some time you'll cover a lot > of theory. Secondly, the process of coming up with ways to test a specific > functionality proves to be a great (and fun) way to learn. And it is also a > great way of applying what you just learnt. Last (but not the least) you > are in luck if you come across a bug or an unexpected behavior! > If you are interested in testing, I'd suggest having a look at the > documentation of the FreeBSD testsuite: https://wiki.freebsd.org/TestSuite and > also the TCP testsuite: https://github.com/freebsd-net/tcp-testsuite (I > am only familiar with these, other members might add more to the list). > > * To start off contributing right away, I'd suggest having a look at some > of these links: > - https://wiki.freebsd.org/IdeasPage > - https://bugs.freebsd.org/bugzilla/describecomponents.cgi > - https://wiki.freebsd.org/JuniorJobs > > * Ask questions! The community members are extremely friendly (and highly > experienced, so you get to learn something new everytime you ask). > > * Also, you can have a look at how some of the community members first > started off (it is quite interesting): https://wiki.freebsd.org/ > HowWeGotHere. > > Over time I got to realize that the key is to always keep learning and > enjoying the entire process. In these fields (and any CS field for that > matter) you never get to stop being amazed by something new everyday. I > think I'm starting to go off-topic so I'll stop. > > PS. I am relatively very new to the community (around only 2 years) so I'm > sure the experienced and senior members will have some great and better > advice to share. My apologies in advance if I wrote something wrong above. > > Hope this helps. Thank you for your interest! > With best regards, > Shivansh Rai > https://wiki.freebsd.org/ShivanshRai > > On Wed, Aug 9, 2017 at 5:35 PM rahul gupta wrote: > >> Hi Team, >> >> As I am working in Dell EMC in Isilon Product , >> and i want to contribute in Free BSD Open source projects as i love to do >> codning, >> My Area of interested is Data Structure and Algorithm and i have fond of >> learn system related coding. >> kindly request you help me how i can help in the development of free BSD >> OS >> and >> also help me out that i how can contribute to free BSD and what is >> smallest >> thigh from i can start to contribute. >> >> your valuable help and guidance are awaited.. >> >> -- >> Thanks & Regards >> Rahul Gupta >> Dell EMC Isilon Engineering Team >> +917200744656 <+91%2072007%2044656> >> _______________________________________________ >> 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 Wed Aug 9 16:54:04 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 772F5DD10AA for ; Wed, 9 Aug 2017 16:54:04 +0000 (UTC) (envelope-from list@execve.net) Received: from lax012.relay.arandomserver.com (lax012.relay.arandomserver.com [198.252.106.48]) (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 3D55E7CEB2 for ; Wed, 9 Aug 2017 16:54:03 +0000 (UTC) (envelope-from list@execve.net) Received: from sng001.hawkhost.com ([119.81.196.36]) by se003.arandomserver.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dfUF2-0006yt-GH for freebsd-hackers@freebsd.org; Wed, 09 Aug 2017 11:54:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=execve.net; s=default; h=Content-Type:To:Subject:Message-ID:Date:From:References: In-Reply-To:MIME-Version:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=oxnuAhfsrjO6ChYA8wY4F7JSDx013Ov+uwReHBD/6fk=; b=QVadJEk9AupCQ/V15YNPDiP15W wzKt6vqQ8VxhQOBuhBO4aEIbR+IDprTKPQb4pqMbYASvM7a5pXHEBWOD1q/aX6EYjbrzYOizu67LM EWeXEIoc27Na0HdGVi+vuot7R; Received: from mail-ua0-f171.google.com ([209.85.217.171]:36260) by sng001.hawkhost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dfUEy-003knS-ID for freebsd-hackers@freebsd.org; Thu, 10 Aug 2017 00:53:52 +0800 Received: by mail-ua0-f171.google.com with SMTP id k43so30897175uaf.3 for ; Wed, 09 Aug 2017 09:53:52 -0700 (PDT) X-Gm-Message-State: AHYfb5gDrZOmJZGCoFs0s5fkUUADpjRkifr1iicVghTXSq4Ppv+6vb6e G5uaCWiowUg34q9UgoVWi3vVmLMITg== X-Received: by 10.159.56.10 with SMTP id p10mr3087778uad.189.1502297631019; Wed, 09 Aug 2017 09:53:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.40.136 with HTTP; Wed, 9 Aug 2017 09:53:50 -0700 (PDT) In-Reply-To: References: <598ADB65.8060701@grosbein.net> From: Gautam Date: Wed, 9 Aug 2017 22:23:50 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: freebsd-hackers X-Originating-IP: 119.81.196.36 X-SpamExperts-Domain: sng001.hawkhost.com X-SpamExperts-Username: relay Authentication-Results: arandomserver.com; auth=pass (login) smtp.auth=relay@sng001.hawkhost.com X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.12) X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZiEh/Q2y0dK8jSMLTE55fwqH0Nprjby6XDb qzVlIOQ03kAwPN4M+BNtq20Hh3O6Az9ismS84NPFas3IWADbmzJ9CZryIsNFvaBrlzs70sT7iKmx j3Zz/WM/IwRyPjIHIwDPF1ZlofeOwAIM7JgtjyhlpinkyDC41hCHKs1oE2UeMx5e973vehgRRMJd d1x498Tufal7CMGWrqEKEiC/97WgGzcWMr0czofRVh8rMXrt/SyLxLEJIkbWABkyXJwBVLal3W+/ PI81P534n3yak4n7EfJL2hMI4yCDSSr/HxDyN5bD8YyxjFtJAz2loLb4we0tFPPhpWPZ07PAOr0y wYIXuCj9wj08m7429e2ZOl/ZXvNM2/zURZVxzSV/eszOttj6AVIvY+ILsI7br1ka/ZVMg6RdYTdA xY74GsEonmxBjzpKeIF2yKaDUU/b2z0vdzaVu34H+eqH7iWBpUrKGrffGcXZKnwjnRMG9jJ/knTt +XiA50wwIMuM3BDtnoPm4HpIizaH26GaoEDwTtnQE6q4ZRNP3CPS3YZT5ODGEA+uOpLZY+4z/dwR ocCZGdc1cl9f9x/pKLS918QV+MmO1bAAEgjXIny51RJ3yyIOVX71wEukYspuIwswojsoiyB8OuXo nV+E7OMXRvgtdyMlnmWi9uF4/xGeHumbSXx1nykjkg3q5Go+y6UPrDLg9O+nbQFoH9UL1HQ24F+S 4+SX5+akQnTIgDfxZ2/WGqYvyOVteVOdo6Dvr8fbMJVJ9/erL6/4IvMfhB2h/z0m0D607pH+pWX8 JH76UCDHe+VBXhtjrZr9RUQzcLUz45TvUuLctG5L8ZHLV0zHQOMuxVjpDkV6 X-Report-Abuse-To: spam@se001.arandomserver.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 16:54:04 -0000 Hi, On Wed, Aug 9, 2017 at 7:43 PM, Mark Millard wrote: > > Swap files on ZFS are also known to have the problem. > > Quoting bugzilla 206048's comment #7 (which is quoting an older > list message): > > On 2017-Feb-13, at 7:20 PM, Konstantin Belousov > wrote > on the freebsd-arm list: > > . . . > > swapfile write requires the write request to come through the filesystem > write path, which might require the filesystem to allocate more memory > and read some data. E.g. it is known that any ZFS write request > allocates memory, and that write request on large UFS file might require > allocating and reading an indirect block buffer to find the block number > of the written block, if the indirect block was not yet read. > > As result, swapfile swapping is more prone to the trivial and unavoidable > deadlocks where the pagedaemon thread, which produces free memory, needs > more free memory to make a progress. Swap write on the raw partition ove= r > simple partitioning scheme directly over HBA are usually safe, while e.g. > zfs over geli over umass is the worst construction. > > =E2=80=8BFirstly, thanks all for the responses. I just want to comment, that when I tested it there was absolutely no need for any swap usage. I tried the test on a laptop with 8GB RAM and did it from the console mode. But it does seem that there might be some request (read/write) to swap which =E2=80=8Bcauses a lock up to the system.=E2=80=8B =E2=80=8BThanks, Gautam =E2=80=8B From owner-freebsd-hackers@freebsd.org Wed Aug 9 17:20:28 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D6A9DD1860 for ; Wed, 9 Aug 2017 17:20:28 +0000 (UTC) (envelope-from datasmurf@mail.ru) Received: from fallback.mail.ru (fallback15.m.smailru.net [94.100.179.50]) (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 D6DBE7DA45 for ; Wed, 9 Aug 2017 17:20:26 +0000 (UTC) (envelope-from datasmurf@mail.ru) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:Cc:To:From:Date; bh=3oHMZoxGUwZCqnHQcvUN33zi2cp6xkKDLgJLyUHpZo8=; b=imDTd0u8aBaCkD9fME8B/BwZIRslXeyFTj+5/Uou48dcy2zLlLE2ZYIR4vuPHR2NOFbg77NYru7DuHRfrjOROeHS4A0kujujFlPy/wexXjo3zkJQPh0x4Sv87l7HpS7vnEvGnMJBrod3nZoIlpUDdCG5VFx6wqIHuRuVWdcUGeo=; Received: from [10.161.64.44] (port=48610 helo=smtp36.i.mail.ru) by fallback15.m.smailru.net with esmtp (envelope-from ) id 1dfUeb-00076m-GT for freebsd-hackers@freebsd.org; Wed, 09 Aug 2017 20:20:21 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:Cc:To:From:Date; bh=3oHMZoxGUwZCqnHQcvUN33zi2cp6xkKDLgJLyUHpZo8=; b=imDTd0u8aBaCkD9fME8B/BwZIRslXeyFTj+5/Uou48dcy2zLlLE2ZYIR4vuPHR2NOFbg77NYru7DuHRfrjOROeHS4A0kujujFlPy/wexXjo3zkJQPh0x4Sv87l7HpS7vnEvGnMJBrod3nZoIlpUDdCG5VFx6wqIHuRuVWdcUGeo=; Received: by smtp36.i.mail.ru with esmtpa (envelope-from ) id 1dfUeS-0000ab-3t; Wed, 09 Aug 2017 20:20:12 +0300 Date: Wed, 9 Aug 2017 19:18:29 +0200 From: Datasmurf To: Farhan Khan Cc: freebsd-hackers@freebsd.org Subject: Re: PCI bus detaching when driver crashing? Message-Id: <20170809191829.4c541da5313af503ef3f470f@mail.ru> In-Reply-To: References: X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-7FA49CB5: 0D63561A33F958A5379F90975EC21C89CBEF2C082954B51DDE279ACE2C80A6DC725E5C173C3A84C3777F8C72A04D893BF14DAC2CF4D7C772834E4788B0B27831C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F2EF91E2201DEA5EC574AF45C6390F7469DAA53EE0834AAEE X-Mailru-Sender: 620CA5946F1319E26837F971D57E01D22E9BE864D95A594542248D9F6949E006F817479B9098B06449070C57D405204EDA8FEABC02D41E1BE882F7789A3AA0D09AFAE9D0B87C27BAB91D000EF664C42CB93E98C39DA16A030DA7A0AF5A3A8387 X-Mras: OK X-7FA49CB5: 0D63561A33F958A51461E51021335F656B6E1F6BE23E281D4549B87D7E2FAE42462275124DF8B9C910FF24F588AC80D2BD9CCCA9EDD067B1EDA766A37F9254B7 X-Mailru-Sender: A5480F10D64C9005E7955441BDF8626595C11B680804F265159231F51B0C43CCC655969879B08F7949070C57D405204EDA8FEABC02D41E1BE882F7789A3AA0D09AFAE9D0B87C27BAB91D000EF664C42CB93E98C39DA16A030DA7A0AF5A3A8387 X-Mras: OK X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 17:20:28 -0000 On Thu, 3 Aug 2017 22:17:17 -0400 Farhan Khan wrote: > Hi all, > > I am trying to write the Realtek 8188e (pci) driver for FreeBSD. I am > making slow incremental progress, and having the driver safely exit > out (as opposed to a segfault). I noticed that when the device > detaches, due to an error in the driver, the entire pci bus will also > detach! For example, here is my kernel output: > > rtwn0: rtwn_load_firmware: failed to upload firmware rtwn-rtl8188eefw > (error 60) > rtwn0: detached > pci2: detached I have/had seen similar errors with my Hardware. T61 with Pro/Wireless 4965AGN and the if_iwn driver. I get Firmware error and then from time to time the pci bus gets detached as well. But i did not think of it as a Problem of the driver or code but of my faulty old Hardware. I have to reboot to get it working. Sorry at the moment i have no log about it. Uptime is 2 days since upgrading to 11.1 Release. > > The first line is where the code crashes: sys/dev/rtwn/if_rtwn_fw.c > line 129 > https://github.com/khanzf/freebsd/blob/103c05369b1ced770a2cadc9468e0134c8d9421b/sys/dev/rtwn/if_rtwn_fw.c#L129 > 404 > Why would this result in the entire pci2 bus detatching? Strangely > enough, I did not have this problem a few months ago, then it > suddenly began. This is significantly slowing down my workflow, and > would be nice to have it resolved. Otherwise, I have to reboot to > bring pci2 back up. > > Any insight? > Thanks! > > Farhan Khan > _______________________________________________ > 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" Greetings Daniel -- #irc - real netizens last resort From owner-freebsd-hackers@freebsd.org Wed Aug 9 18:47:05 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E96D7DD3549 for ; Wed, 9 Aug 2017 18:47:05 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.etoilesoft.fr (mx1.etoilesoft.fr [52.57.51.18]) by mx1.freebsd.org (Postfix) with ESMTP id B468680F19 for ; Wed, 9 Aug 2017 18:47:05 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.etoilesoft.fr (localhost [127.0.0.1]) by mx1.etoilesoft.fr (Postfix) with ESMTP id 41B329D1A9 for ; Wed, 9 Aug 2017 18:47:13 +0000 (UTC) Received: from [172.25.59.64] (localhost [127.0.0.1]) (Authenticated sender: auryn@zirakzigil.org) by mx1.etoilesoft.fr (Postfix) with ESMTPA id DD4FD9C944 for ; Wed, 9 Aug 2017 18:47:12 +0000 (UTC) From: Giulio Ferro Subject: devd in jail To: freebsd-hackers@freebsd.org Message-ID: Date: Wed, 9 Aug 2017 20:47:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 18:47:06 -0000 Hello all, Setup : 11.1-STABLE FreeBSD 11.1-STABLE #0 r321925M amd64 I'm trying to create a fully virtualized desktop enviroment in a jail by means of installing there a xrdp-devel server + Xorg installation (xorg + xorgrdp). Everything seems to work until the moment when the X server actually tries to come up (after I choose session=xorg, username + password) In the X logs in the jail, in fact, I have this error: ... [ 9768.824] (EE) config/devd: fail to connect to devd [ 9768.824] [config] failed to initialise devd I've checked on the host machine, and I don't have that error as everything works fine there... In my jail, I've setup the devfs like this (/etc/jail.conf in the host): --- exec.start="/bin/sh /etc/rc"; exec.stop="/bin/sh /etc/rc.shutdown"; exec.clean; mount.devfs; devfs_ruleset=1; path="/usr/home/jail/$name"; myjail { host.hostname="myjail.me.com"; vnet; vnet.interface = epair0b, epair1b; persist; } --- and in the /etc/devfs.conf everythink is commented out. In the /dev directory in the jail, I get both the devctl and devctl2 devices. As the devd demon is not running in the jail, I've tried adding devd_enable="YES" in the rc.conf (jail), but when I try to start it, I get: # /etc/rc.d/devd start Starting devd. devd: Can't open devctl device /dev/devctl: Device busy /etc/rc.d/devd: WARNING: failed to start devd Do you know if I'm doing something wrong, or there's a proper way to have devd running in the jail? I've thought that maybe I should use the devtcl2 device, as the devctl is used by the host, but I don't know how to specify that to devd... Thanks in advance for your help. Giulio From owner-freebsd-hackers@freebsd.org Wed Aug 9 19:14:23 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 906B1DD3C64 for ; Wed, 9 Aug 2017 19:14:23 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2445881CF3 for ; Wed, 9 Aug 2017 19:14:23 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id f15so4332574wmg.1 for ; Wed, 09 Aug 2017 12:14:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=CTqEs8O90uLQk1SeBCqe5exg7LX6/yI3AZ7KybzYpHg=; b=lsFc/vGXKZcJa/qKq3kgHusnFVmhhGOBV4A5P3H/kRgIcxgVukSh4VFstIgFllKUEi WPtLwQLetR4ouM6PUMm+Vvubww4ylQLo9GYBDcLMkkV5g7W2IhKX+ymFAYew2YMD6xTj oYr4oQpt40rQF1oh9GVfbk79CYRslaLXFtmWVNPGqSPMqpR7cIb1fstMCKXQgDohWUNa EeJxxdoAIOFx8iY5W90hp2oyq8gdGYfsldoIOCif30Oq5UwkS6Gz9L2WvFryAMXmmUvK HOWkRxGCeXvvXOkcgH10fmchoBmYmBOA1KB7eINQC77WQ7vPB0dwpthCD+Q19kReMLKv Pxfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=CTqEs8O90uLQk1SeBCqe5exg7LX6/yI3AZ7KybzYpHg=; b=iXeOeM1WN45hFLAfOteF1lzXowX1ctowhPq+1r1RxvhszYlF0xXs20z6PX2FnDYbWs 8mzRDBRfGZTwBNbociS38siFrI2Hn82SsQZ3BbGv40e+mxlodnKLyRnHPBX2CgoEoMSN 3/1ZY795XY2kEkLOdO2KoBLVzAVaQ9q8OAacrky0XLQzfrBmTz8/KmXpjFK+qM/Nr7XV qoe4Kl1O0k2zGOhvtBMKAtw1iStQLVRw9NmkMZ6dy6MmE2pe8+2L+DuVHvfL1h10Faik 1sy88+h3GNQZPD0ooOa7Z3SjNIsa1UWQqYC5zZftXW9o5AitO5AQOKXCBszqP0QNgO+6 P8oA== X-Gm-Message-State: AHYfb5h9ncXBImF49wcn+bVTSV98lAb9MNdov8uM4AScHr7SHEAGrWXm FAl4Plp+I+0uZI1tGNsV8X0+6izbzw== X-Received: by 10.28.170.18 with SMTP id t18mr5866836wme.6.1502306061258; Wed, 09 Aug 2017 12:14:21 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.28.208.3 with HTTP; Wed, 9 Aug 2017 12:14:20 -0700 (PDT) In-Reply-To: References: From: Alan Somers Date: Wed, 9 Aug 2017 13:14:20 -0600 X-Google-Sender-Auth: bHUFYTgiY-BekiBdXn4gtsX_zKY Message-ID: Subject: Re: devd in jail To: Giulio Ferro Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 19:14:23 -0000 On Wed, Aug 9, 2017 at 12:47 PM, Giulio Ferro wrote: > Hello all, > > Setup : 11.1-STABLE FreeBSD 11.1-STABLE #0 r321925M amd64 > > > I'm trying to create a fully virtualized desktop enviroment in a jail by > means of installing there > a xrdp-devel server + Xorg installation (xorg + xorgrdp). > > Everything seems to work until the moment when the X server actually tries > to come up (after I choose session=xorg, username + password) > In the X logs in the jail, in fact, I have this error: > > ... > [ 9768.824] (EE) config/devd: fail to connect to devd > [ 9768.824] [config] failed to initialise devd > > > I've checked on the host machine, and I don't have that error as everything > works fine there... > > In my jail, I've setup the devfs like this (/etc/jail.conf in the host): > > --- > exec.start="/bin/sh /etc/rc"; > exec.stop="/bin/sh /etc/rc.shutdown"; > exec.clean; > mount.devfs; > devfs_ruleset=1; > > path="/usr/home/jail/$name"; > > myjail { > host.hostname="myjail.me.com"; > vnet; > vnet.interface = epair0b, epair1b; > persist; > } > --- > > > and in the /etc/devfs.conf everythink is commented out. > > In the /dev directory in the jail, I get both the devctl and devctl2 > devices. > > As the devd demon is not running in the jail, I've tried adding > devd_enable="YES" > > in the rc.conf (jail), but when I try to start it, I get: > > # /etc/rc.d/devd start > Starting devd. > devd: Can't open devctl device /dev/devctl: Device busy > /etc/rc.d/devd: WARNING: failed to start devd > > > Do you know if I'm doing something wrong, or there's a proper way to have > devd running in the jail? > > I've thought that maybe I should use the devtcl2 device, as the devctl is > used by the host, > but I don't know how to specify that to devd... > > Thanks in advance for your help. > > Giulio Unfortunately, you're not going to be able to run devd(8) in the jail. /dev/devctl can be opened by only one reader at a time, and that reader is always devd(8). /dev/devctl2 is actually a completely different device with a totally different interface. Apologies for the confusing names. But you may not need to run a totally separate instance of devd. The X server is probably trying to open either /var/run/devd.pipe or /var/run/devd.seqpacket.pipe. ktrace would tell you which. If you can bridge those sockets into the jail, then X would probably run. -Alan From owner-freebsd-hackers@freebsd.org Wed Aug 9 20:18:09 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA56CDD53BB for ; Wed, 9 Aug 2017 20:18:09 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 716DB84C72 for ; Wed, 9 Aug 2017 20:18:09 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: by mail-it0-x22f.google.com with SMTP id f16so11815375itb.0 for ; Wed, 09 Aug 2017 13:18:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=y8fJvpS/dYLEvzMCOonur9SRF+uB1OzeAwjyP4DrIxc=; b=hiRYovkqN6gnH9ButnajKmb713YiENrVxt1RgaC1jE/fZPT2GNxvJjSvugwsLeIHFm bh7P5OTU4EB1v5/YsP2FLk7dinB4FS8Tjy4znRMz0c/JgDGNFIk0NMYGKkR80S6tmMKc XpxXDUQM3PqX9OIX9x6jwEVAJFVZI2lovf3pfTZQiYdxyuqwyx4EwVEAjxAcE97Uokt/ YOpvP+YOZ/XIqQ1DMiIVru0bhIrL/BqnzGSzxtRV+e/8i8HKM7VF4WPjFAEg665IlEV4 TcJlqpTR5qVVhXOUsUlLKiavyx0ASX+Wp0E0jZe2AWe7kH7MZJTr/OHtvcp/BIHD0u+1 DI4Q== 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=y8fJvpS/dYLEvzMCOonur9SRF+uB1OzeAwjyP4DrIxc=; b=Smrv5OF+oA8bJdC7zzmGc9Gykgd0bPORlX7glVSSVIeVFuH40kVKoBT5bLDuEyEkCK hBvas7omtlHolnB9NLwkwYx4uMNLTaw5swzX+bgu5hMQZQtigqMmMs4uU9hzcNtXUFM0 SXfOVL0Ew2yr7WZZOVN30VPoI0ahrHV5C8hIyHG3jl+YgPJKzojr2ugSBRnlNd5aTRPC 0/XswMva/pvRDH1Mlw1wxE6j7Mh2rlKibswbtccGAXMQ/fM/Nf6DEMHOXV12MVTgbbsV NUN5Qo28c3wGwiqMkdg8h5gRkSKcX4epnDKp74OCYURd3i0nLtBqC4bIr/j22llCfgIV 3E1Q== X-Gm-Message-State: AIVw111dYEAZCpnW+E+wVdAr8oTrNr5qzrGENVq0P4angm7nrEAvXgrZ 2MoovH5xVdnopMGmGjRLsU2KSXoTH7zq X-Received: by 10.36.237.137 with SMTP id r131mr5353148ith.70.1502309888363; Wed, 09 Aug 2017 13:18:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.16.69 with HTTP; Wed, 9 Aug 2017 13:18:07 -0700 (PDT) From: raichoo Date: Wed, 9 Aug 2017 22:18:07 +0200 Message-ID: Subject: `ifconfig` patch to resolve IPv6 scope names To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 20:18:09 -0000 Hi, I've made a trivial patch that resolves IPv6 scope names (according to rfc4291). I thought this might be handy, so one does not have to memorize what id refers to which scope. And it's a nice opportunity to get my feet wet I guess :) This is my first patch and I have no idea what's the best way to contribute to the project (probably I didn't look hard enough or in the wrong places). Feedback and pointers appreciated. Kind regards, raichoo diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c index e93d94355e..165b2cc90a 100644 --- a/sbin/ifconfig/af_inet6.c +++ b/sbin/ifconfig/af_inet6.c @@ -268,10 +268,32 @@ in6_status(int s __unused, const struct ifaddrs *ifa) if ((flags6 & IN6_IFF_PREFER_SOURCE) != 0) printf("prefer_source "); - if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) + if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { printf("scopeid 0x%x ", ((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id); + switch (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { + case 0x1: + printf("interface-local "); + break; + case 0x2: + printf("link-local "); + break; + case 0x4: + printf("admin-local "); + break; + case 0x5: + printf("site-local "); + break; + case 0x8: + printf("organization-local "); + break; + case 0xe: + printf("global "); + break; + } + } + if (ip6lifetime && (lifetime.ia6t_preferred || lifetime.ia6t_expire)) { printf("pltime "); if (lifetime.ia6t_preferred) { From owner-freebsd-hackers@freebsd.org Wed Aug 9 20:45:06 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBF59DD5AFE for ; Wed, 9 Aug 2017 20:45:06 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF4A6CCC for ; Wed, 9 Aug 2017 20:45:06 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: by mail-it0-x22f.google.com with SMTP id 76so3729930ith.0 for ; Wed, 09 Aug 2017 13:45:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=unCpwB/VccVou+W4OaffucM7Z4BeEdeEOZsJo4gGtX4=; b=MDRVFtaAli6JdvGLGe74Notbbsnm9sm3gzDOiKx7dSl3LFvaX/j/9FElNTAjjv1yAs YdyilHjo7d1+NZ2QUJpSkENEdLUFMUR9X8bFGwdxSRUlKjD2jCuFiyGk/s3TYsvoHEjL xKHCCaCGXF3uMUSZM5DhEax6z8evnTlWiRVVzdtftEeq5kiS+FCyMAnw13lYLRELf6Gs sBX2WaVPJ/bsKCOw1ksyuQPhzR7S9qJJdepBB3BDAfecvu2oyeWSc2c8Crco8rfm/glW Ui1Ha4nCeIhl3dMb0Fh96knzeyPLnBIDxHNxYZ8KOngqyTwHU03bA6idLJVMdcTsFjE4 T94g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=unCpwB/VccVou+W4OaffucM7Z4BeEdeEOZsJo4gGtX4=; b=aJToCaUOhbx/HZYbVdm5RqLmzwpF3VkCaRuuZJmz/2xhUEUbb29Wyh7ggPg+yZXciu TWqowG86QX86jsFypaiXiEfz+hlXZ/Q/SpbilDKfBa9kHfki8/N1AJayWfk7BwiHbxbd 8uPhjCkiKoAbIyeKvVWu0vSybHQTNNeoKPtktEhmDIaU2HUm38o1tRw/n0mdZHPl9zZW 1bfojXm2nKujiLFooBneVUW9w+3J9ulvs3QSk6T1NzB73N/s9QXvHmVjcDjiPzW+ANYo 74QvS9biT451mdiEw77zaEz5YW8+HZEoRFmr7gO8KVfdj3HyTinUl1dNKq8c/UeJDc5t EvgA== X-Gm-Message-State: AHYfb5ghZZZhbCYi1vEWn2JSmlqsYHAxciVPYkudKPgUPdQclgaX19PB kqOOnnMhgLEbhzE/FluVKH3lF12bTJ0u X-Received: by 10.36.50.86 with SMTP id j83mr7879261ita.95.1502311505927; Wed, 09 Aug 2017 13:45:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.16.69 with HTTP; Wed, 9 Aug 2017 13:45:05 -0700 (PDT) In-Reply-To: References: From: raichoo Date: Wed, 9 Aug 2017 22:45:05 +0200 Message-ID: Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 20:45:07 -0000 Had a little chat with kp on #bsddev and got the advice to use the constants in in6.h instead of the bare scope ids. So here's the revised version. diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c index e93d94355e..4e37656db0 100644 --- a/sbin/ifconfig/af_inet6.c +++ b/sbin/ifconfig/af_inet6.c @@ -268,10 +268,29 @@ in6_status(int s __unused, const struct ifaddrs *ifa) if ((flags6 & IN6_IFF_PREFER_SOURCE) != 0) printf("prefer_source "); - if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) + if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { printf("scopeid 0x%x ", ((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id); + switch (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { + case __IPV6_ADDR_SCOPE_INTFACELOCAL: + printf("interface-local "); + break; + case __IPV6_ADDR_SCOPE_LINKLOCAL: + printf("link-local "); + break; + case __IPV6_ADDR_SCOPE_SITELOCAL: + printf("site-local "); + break; + case __IPV6_ADDR_SCOPE_ORGLOCAL: + printf("organization-local "); + break; + case __IPV6_ADDR_SCOPE_GLOBAL: + printf("global "); + break; + } + } + if (ip6lifetime && (lifetime.ia6t_preferred || lifetime.ia6t_expire)) { printf("pltime "); if (lifetime.ia6t_preferred) { On Wed, Aug 9, 2017 at 10:18 PM, raichoo wrote: > Hi, > > I've made a trivial patch that resolves IPv6 scope names (according to > rfc4291). > I thought this might be handy, so one does not have to memorize what id > refers > to which scope. And it's a nice opportunity to get my feet wet I guess :) > > This is my first patch and I have no idea what's the best way to > contribute to the > project (probably I didn't look hard enough or in the wrong places). > > Feedback and pointers appreciated. > > Kind regards, > raichoo > > diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c > index e93d94355e..165b2cc90a 100644 > --- a/sbin/ifconfig/af_inet6.c > +++ b/sbin/ifconfig/af_inet6.c > @@ -268,10 +268,32 @@ in6_status(int s __unused, const struct ifaddrs *ifa) > if ((flags6 & IN6_IFF_PREFER_SOURCE) != 0) > printf("prefer_source "); > > - if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) > + if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { > printf("scopeid 0x%x ", > ((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_ > scope_id); > > + switch (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) > { > + case 0x1: > + printf("interface-local "); > + break; > + case 0x2: > + printf("link-local "); > + break; > + case 0x4: > + printf("admin-local "); > + break; > + case 0x5: > + printf("site-local "); > + break; > + case 0x8: > + printf("organization-local "); > + break; > + case 0xe: > + printf("global "); > + break; > + } > + } > + > if (ip6lifetime && (lifetime.ia6t_preferred || > lifetime.ia6t_expire)) { > printf("pltime "); > if (lifetime.ia6t_preferred) { > > From owner-freebsd-hackers@freebsd.org Thu Aug 10 08:24:24 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69903DCB5E4 for ; Thu, 10 Aug 2017 08:24:24 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward104j.mail.yandex.net (forward104j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06D1A76CAE for ; Thu, 10 Aug 2017 08:24:24 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback10g.mail.yandex.net (mxback10g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:171]) by forward104j.mail.yandex.net (Yandex) with ESMTP id 65FCB43440; Thu, 10 Aug 2017 11:22:33 +0300 (MSK) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:7]) by mxback10g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id p9sIcsaaCU-MXd0BoMI; Thu, 10 Aug 2017 11:22:33 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1502353353; bh=R8LEycLOhpDbAw7fvmKJ+KInmJLX1pLIQFO3qcI3HL8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=UKaoOPo6d7bYjcKNPQ0H3c603ZsXVkFJlXkzQN+i65Uux/ktS4SZSTt3UJuLYrjbQ mjz2fXMJvDEAK5i8NvP+k17cyDykCJoAYgPK38OtQSEaf+y2jkY4QF3pbUrNNiKErT WHHMMSe7IHKzRUQOQ33ktvNiPs71WBIOlFZlkyls= Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id rlhkmxPDAd-MWpeBYoV; Thu, 10 Aug 2017 11:22:32 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1502353352; bh=R8LEycLOhpDbAw7fvmKJ+KInmJLX1pLIQFO3qcI3HL8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=tD4yoksx46y/lVUBeyL1qUN/Zv+ty9CS7VndULBmleTLANyvbS5uE5in9WlxL0P5M V5pDsDgD3z8wACahuUf6MZg2EPUAIF90ypaVGLiRuvXqt9kWBoidWXs9kQ8dbXBzYa 56FTPXSp4f/ibjI7BYM79czAVG/s4/pZ+1SjwWVQ= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: raichoo , freebsd-hackers@freebsd.org References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> Date: Thu, 10 Aug 2017 11:19:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dlhXvmALTLSlcj8h0Ho4SVQd1IMOASOiO" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 08:24:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dlhXvmALTLSlcj8h0Ho4SVQd1IMOASOiO Content-Type: multipart/mixed; boundary="7s8lKON7xeJw9LRXGHvk0R9ah0rlBdigS"; protected-headers="v1" From: "Andrey V. Elsukov" To: raichoo , freebsd-hackers@freebsd.org Message-ID: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> Subject: Re: `ifconfig` patch to resolve IPv6 scope names References: In-Reply-To: --7s8lKON7xeJw9LRXGHvk0R9ah0rlBdigS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 09.08.2017 23:18, raichoo via freebsd-hackers wrote: > Hi, >=20 > I've made a trivial patch that resolves IPv6 scope names (according to > rfc4291). > I thought this might be handy, so one does not have to memorize what id= > refers > to which scope. And it's a nice opportunity to get my feet wet I guess = :) >=20 > This is my first patch and I have no idea what's the best way to contri= bute > to the > project (probably I didn't look hard enough or in the wrong places). >=20 > Feedback and pointers appreciated. >=20 > Kind regards, > raichoo >=20 > diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c > index e93d94355e..165b2cc90a 100644 > --- a/sbin/ifconfig/af_inet6.c > +++ b/sbin/ifconfig/af_inet6.c > @@ -268,10 +268,32 @@ in6_status(int s __unused, const struct ifaddrs *= ifa) > if ((flags6 & IN6_IFF_PREFER_SOURCE) !=3D 0) > printf("prefer_source "); >=20 > - if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) > + if (((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id) { > printf("scopeid 0x%x ", > ((struct sockaddr_in6 > *)(ifa->ifa_addr))->sin6_scope_id); >=20 > + switch (((struct sockaddr_in6 > *)(ifa->ifa_addr))->sin6_scope_id) { > + case 0x1: > + printf("interface-local "); > + break; > + case 0x2: > + printf("link-local "); > + break; Hi, the patch is wrong. sin6_scope_id does not describe the scope, it is scope zone id. To determine the scope, you should use an address. --=20 WBR, Andrey V. Elsukov --7s8lKON7xeJw9LRXGHvk0R9ah0rlBdigS-- --dlhXvmALTLSlcj8h0Ho4SVQd1IMOASOiO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmMFwcACgkQAcXqBBDI oXp+YQf/doemcn3dkEcg5lgvEz/vn4lQBkTzRzFDv5E5+vPNtThMmMrQWC5EyBbQ lbrBto1J7zOQ8s3v1LBcY3Xj8iu6XoMttUL9NEXN4c158H5NU0oRBdlmEJK0zZed fEDLscT9hEcFrF6HRJQGVOsq9HrTC8aQUS/tx9Nl0bUzuTKYbyaJ9sx8cS98MCJZ Wq0hTNwdVx1ExErZ1Dwd4C36znxVOs8l3vb3GAlr2cF3jukDp8eIeOvMibOgfo/E dMZz72lH135JwtT206c9znj4LmG2uDk1dBJ9j33eW914SJAAfl2HajAADcRvCuvr a5O8idsX3SReQUX7Ncl8zXD/uD0Cbg== =xMRa -----END PGP SIGNATURE----- --dlhXvmALTLSlcj8h0Ho4SVQd1IMOASOiO-- From owner-freebsd-hackers@freebsd.org Thu Aug 10 11:32:40 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 312D1DCF889 for ; Thu, 10 Aug 2017 11:32:40 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: from mail-qt0-x241.google.com (mail-qt0-x241.google.com [IPv6:2607:f8b0:400d:c0d::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE49880653; Thu, 10 Aug 2017 11:32:39 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: by mail-qt0-x241.google.com with SMTP id t37so379359qtg.2; Thu, 10 Aug 2017 04:32:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ltFIrGylLVgGtY/iiZim4kxDcUYNS3AIWD2JjfvQEBs=; b=NfSZnLCdv3oEnC8c4WtqFtKVYsb3bxSdHAD2FlFsT+TGwsGSdyVH9/w7TnMR21+Jco uMKFg2ytldATAC3xAYRsW6DYmIZUP6NHRWdPyYG7VpoQPfpdWJjZ4ksseO5PhfQDZMC7 QufLEtIQbvAvsIL5h+NmRSlfBPd2N37eUqcjwC80Hq5Ay7jJG2ABmtPPDPWWJpUQp6bO VfjcmgxMXGgPsISCj7qkJQwtRIAl4r4Y9HDN6mEzcJ4l31beny5uSw1jFuWA84GVxnZc cnhxvWGHWGx61Bgd5z9aKgbD5o+HZP7P2e2qmOlOQw0ESu8woH6SZA4ATm557Vjpl/N0 MIPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ltFIrGylLVgGtY/iiZim4kxDcUYNS3AIWD2JjfvQEBs=; b=AE/H4mRqXqrnKVYJ4uJDG49wb2TGTQJuk9bGCOk/54Hslb4Ge9uGPHiWiNyoti7Var tbm4q7rYTrWxEkEBEi5CIViXFLATV9G2e+EBSf37sulFcO0qpgsDTUxdzY4BOoupf5f9 kQIXRYYCjlecFKCXlq1finnaEPtbX10uz6OYq44qk5fuOazgrCw3cqnbvj2BAuxkS1j/ Kh3kjX9fDXibDebk0u+SIcWHW8lnR+mxo6LbjAcXDTiyouUuogQcMIi0hLezrXciPdSI GZBUPjrV/kOB/6Hb2leFcKMZDM6HEvZ/XwcktCwWG5IAfi6EklgmV1JGNCbxKtTTJx4o DMdw== X-Gm-Message-State: AHYfb5g6AiJCmFY7l5VlwfmJIj2qQYBK5VZjLCvXDcimCQoyAodHOfZn mmxt31UZbxRNPUryccHkVjAF+YbgdLd5 X-Received: by 10.200.9.43 with SMTP id t40mr14634298qth.237.1502364758772; Thu, 10 Aug 2017 04:32:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.228 with HTTP; Thu, 10 Aug 2017 04:32:38 -0700 (PDT) In-Reply-To: References: From: rahul gupta Date: Thu, 10 Aug 2017 17:02:38 +0530 Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: Shivansh Rai Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Thu, 10 Aug 2017 12:01:26 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 11:32:40 -0000 Hi Team, Actually I am looking for Some Dev and i keen to work on File system so please any body assigned me some work related to file system and guide me the way that how can start contributing because i am quite beginner to this so please help me . Thanks in advanced On Wed, Aug 9, 2017 at 7:31 PM, rahul gupta wrote: > This is great, thank you! > > On 09-Aug-2017 7:06 PM, "Shivansh Rai" wrote: > >> Hi Rahul, >> >> I can say that your interests greatly match with mine so I'd write here >> what I did when I first got introduced to FreeBSD. It is possible that you >> might find the following very easy as I'm a beginner :-) >> >> * I made my first contribution during Google Summer of Code '16. The >> project ideas proposed every year are very cool and I'd suggest having a >> look at some of the previous years' ideas as not all of them are taken up >> (you can also have a look at the previous projects). A good thing about >> them is that they have a mention of the difficulty level and the domain >> knowledge required to participate, so you can easily filter out the ones >> you might be interested in - https://wiki.freebsd.org/SummerOfCodeIdeas. >> >> * Look up the src tree and try to find a piece of code which interests >> you (for e.g. it may be a base utility, say ls). Read through the code to >> see how it works. It is a fun activity which I occasionally do. It is also >> possible that in the process you might come up with an improvement. >> >> * *Testing* >> I have come to realize that testing is a great way to explore and learn a >> lot very fast (according to me). Firstly, you get to study how things work. >> For e.g. if you want to perform testing of the TCP stack, you might first >> start off learning about how TCP works. Since it is very extensive, at a >> time you can pick up a single functionality (say, selective >> acknowledgements) and study it end to end after which you try to come up >> with ways of testing it. So you didn't study the entire theory behind TCP, >> but now you know how this specific functionality works very well. Then you >> proceed on with other functionalities and in some time you'll cover a lot >> of theory. Secondly, the process of coming up with ways to test a specific >> functionality proves to be a great (and fun) way to learn. And it is also a >> great way of applying what you just learnt. Last (but not the least) you >> are in luck if you come across a bug or an unexpected behavior! >> If you are interested in testing, I'd suggest having a look at the >> documentation of the FreeBSD testsuite: https://wiki.freebsd.org/TestS >> uite and also the TCP testsuite: https://github.com/freebsd-net >> /tcp-testsuite (I am only familiar with these, other members might add >> more to the list). >> >> * To start off contributing right away, I'd suggest having a look at some >> of these links: >> - https://wiki.freebsd.org/IdeasPage >> - https://bugs.freebsd.org/bugzilla/describecomponents.cgi >> - https://wiki.freebsd.org/JuniorJobs >> >> * Ask questions! The community members are extremely friendly (and highly >> experienced, so you get to learn something new everytime you ask). >> >> * Also, you can have a look at how some of the community members first >> started off (it is quite interesting): https://wiki.freebsd.org/HowWe >> GotHere. >> >> Over time I got to realize that the key is to always keep learning and >> enjoying the entire process. In these fields (and any CS field for that >> matter) you never get to stop being amazed by something new everyday. I >> think I'm starting to go off-topic so I'll stop. >> >> PS. I am relatively very new to the community (around only 2 years) so >> I'm sure the experienced and senior members will have some great and better >> advice to share. My apologies in advance if I wrote something wrong above. >> >> Hope this helps. Thank you for your interest! >> With best regards, >> Shivansh Rai >> https://wiki.freebsd.org/ShivanshRai >> >> On Wed, Aug 9, 2017 at 5:35 PM rahul gupta wrote: >> >>> Hi Team, >>> >>> As I am working in Dell EMC in Isilon Product , >>> and i want to contribute in Free BSD Open source projects as i love to do >>> codning, >>> My Area of interested is Data Structure and Algorithm and i have fond of >>> learn system related coding. >>> kindly request you help me how i can help in the development of free BSD >>> OS >>> and >>> also help me out that i how can contribute to free BSD and what is >>> smallest >>> thigh from i can start to contribute. >>> >>> your valuable help and guidance are awaited.. >>> >>> -- >>> Thanks & Regards >>> Rahul Gupta >>> Dell EMC Isilon Engineering Team >>> +917200744656 <+91%2072007%2044656> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@f >>> reebsd.org" >>> >> -- Thanks & Regards Rahul Gupta Dell EMC Isilon Engineering Team +917200744656 From owner-freebsd-hackers@freebsd.org Thu Aug 10 14:11:09 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E29B1DD3D67 for ; Thu, 10 Aug 2017 14:11:09 +0000 (UTC) (envelope-from shivanshrai84@gmail.com) Received: from mail-ua0-f195.google.com (mail-ua0-f195.google.com [209.85.217.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E54025F2 for ; Thu, 10 Aug 2017 14:11:09 +0000 (UTC) (envelope-from shivanshrai84@gmail.com) Received: by mail-ua0-f195.google.com with SMTP id d29so428011uai.2 for ; Thu, 10 Aug 2017 07:11:09 -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; bh=A9HrxVfkxB42+x1mtX6ssEzCwfNP5VJJoOh8ayNUnaw=; b=iTYfFdkRRigucyiZWvRp4OLDPrwILb9LqD+mFKliLO7fWx2Fq4nMmLTCuqoa3YMPAw Vw1M1rGrx0hyLntFa8zf6mDffFWj1FJ39SIXxGZA1PjzvmOAzA4r3yQ6OdFr92SnVAZH pz3GlvU1HnLqNu3d8p1xzuegWN9KbEwvTLyFZHa2Fun+dzTg6EVaRC1EqjDk1jlgDiCM TSXCE8J7jV5Q1apexsa4kqZ6pw2N8kMHGTT5usPBgZmXAI9wN4jBiK4x+THnscRQbaNa 8AYzLqCQRvROeQso30um9HWc/pO1rWHUdckhivVNiVgu7hoAsblv6JV1bRRm3auo+qei WlKw== X-Gm-Message-State: AHYfb5hTLmaoVpkSVqFjOZI5d/66MkpNIOvylTLYCaZAa+UcNG1l1fjx ivEXqYQpkHjKO3LM X-Received: by 10.159.36.133 with SMTP id 5mr8350936uar.122.1502374261763; Thu, 10 Aug 2017 07:11:01 -0700 (PDT) Received: from mail-ua0-f181.google.com (mail-ua0-f181.google.com. [209.85.217.181]) by smtp.gmail.com with ESMTPSA id r21sm2088423uaf.2.2017.08.10.07.11.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 07:11:01 -0700 (PDT) Received: by mail-ua0-f181.google.com with SMTP id 80so3671929uas.0 for ; Thu, 10 Aug 2017 07:11:01 -0700 (PDT) X-Received: by 10.159.34.197 with SMTP id 63mr8594043uan.31.1502374260966; Thu, 10 Aug 2017 07:11:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Shivansh Rai Date: Thu, 10 Aug 2017 14:10:50 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: rahul gupta , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 14:11:10 -0000 Hi Rahul, Corresponding to each of the projects listed on that page, you'll see a field named "Technical Contact". You can simply click on the link in that field to visit the wiki page of the developer concerned with that project. The common email format is something like this - if the id in "Technical Contact" is for e.g. xyz@ then the corresponding email address will be xyz@freebsd.org Hope this helps. Regards, -- Shivansh On Thu, Aug 10, 2017 at 6:15 PM rahul gupta wrote: > Hi Shivansh, > > I show some of small projects in : https://wiki.freebsd.org/JuniorJobs > > but i dont know to whom i should contacts for getting invole in this > projects , i am really keen to work in this please help me out > that how i can get involved in the development of this projects. > I have very good knowledge of C, CPP and data structure and algorithm and > i want to use my skills for this Dev and i am also interested to work in > kernel side . > > On Thu, Aug 10, 2017 at 5:02 PM, rahul gupta wrote: > >> Hi Team, >> Actually I am looking for Some Dev and i keen to work on File system so >> please any body assigned me some work related to file system and guide me >> the way that how can start contributing because i am quite beginner to this >> so please help me . >> >> Thanks in advanced >> >> On Wed, Aug 9, 2017 at 7:31 PM, rahul gupta wrote: >> >>> This is great, thank you! >>> >>> On 09-Aug-2017 7:06 PM, "Shivansh Rai" wrote: >>> >>>> Hi Rahul, >>>> >>>> I can say that your interests greatly match with mine so I'd write here >>>> what I did when I first got introduced to FreeBSD. It is possible that you >>>> might find the following very easy as I'm a beginner :-) >>>> >>>> * I made my first contribution during Google Summer of Code '16. The >>>> project ideas proposed every year are very cool and I'd suggest having a >>>> look at some of the previous years' ideas as not all of them are taken up >>>> (you can also have a look at the previous projects). A good thing about >>>> them is that they have a mention of the difficulty level and the domain >>>> knowledge required to participate, so you can easily filter out the ones >>>> you might be interested in - https://wiki.freebsd.org/SummerOfCodeIdeas >>>> . >>>> >>>> * Look up the src tree and try to find a piece of code which interests >>>> you (for e.g. it may be a base utility, say ls). Read through the code to >>>> see how it works. It is a fun activity which I occasionally do. It is also >>>> possible that in the process you might come up with an improvement. >>>> >>>> * *Testing* >>>> I have come to realize that testing is a great way to explore and learn >>>> a lot very fast (according to me). Firstly, you get to study how things >>>> work. For e.g. if you want to perform testing of the TCP stack, you might >>>> first start off learning about how TCP works. Since it is very extensive, >>>> at a time you can pick up a single functionality (say, selective >>>> acknowledgements) and study it end to end after which you try to come up >>>> with ways of testing it. So you didn't study the entire theory behind TCP, >>>> but now you know how this specific functionality works very well. Then you >>>> proceed on with other functionalities and in some time you'll cover a lot >>>> of theory. Secondly, the process of coming up with ways to test a specific >>>> functionality proves to be a great (and fun) way to learn. And it is also a >>>> great way of applying what you just learnt. Last (but not the least) you >>>> are in luck if you come across a bug or an unexpected behavior! >>>> If you are interested in testing, I'd suggest having a look at the >>>> documentation of the FreeBSD testsuite: >>>> https://wiki.freebsd.org/TestSuite and also the TCP testsuite: >>>> https://github.com/freebsd-net/tcp-testsuite (I am only familiar with >>>> these, other members might add more to the list). >>>> >>>> * To start off contributing right away, I'd suggest having a look at >>>> some of these links: >>>> - https://wiki.freebsd.org/IdeasPage >>>> - https://bugs.freebsd.org/bugzilla/describecomponents.cgi >>>> - https://wiki.freebsd.org/JuniorJobs >>>> >>>> * Ask questions! The community members are extremely friendly (and >>>> highly experienced, so you get to learn something new everytime you ask). >>>> >>>> * Also, you can have a look at how some of the community members first >>>> started off (it is quite interesting): >>>> https://wiki.freebsd.org/HowWeGotHere. >>>> >>>> Over time I got to realize that the key is to always keep learning and >>>> enjoying the entire process. In these fields (and any CS field for that >>>> matter) you never get to stop being amazed by something new everyday. I >>>> think I'm starting to go off-topic so I'll stop. >>>> >>>> PS. I am relatively very new to the community (around only 2 years) so >>>> I'm sure the experienced and senior members will have some great and better >>>> advice to share. My apologies in advance if I wrote something wrong above. >>>> >>>> Hope this helps. Thank you for your interest! >>>> With best regards, >>>> Shivansh Rai >>>> https://wiki.freebsd.org/ShivanshRai >>>> >>>> On Wed, Aug 9, 2017 at 5:35 PM rahul gupta wrote: >>>> >>>>> Hi Team, >>>>> >>>>> As I am working in Dell EMC in Isilon Product , >>>>> and i want to contribute in Free BSD Open source projects as i love to >>>>> do >>>>> codning, >>>>> My Area of interested is Data Structure and Algorithm and i have fond >>>>> of >>>>> learn system related coding. >>>>> kindly request you help me how i can help in the development of free >>>>> BSD OS >>>>> and >>>>> also help me out that i how can contribute to free BSD and what is >>>>> smallest >>>>> thigh from i can start to contribute. >>>>> >>>>> your valuable help and guidance are awaited.. >>>>> >>>>> -- >>>>> Thanks & Regards >>>>> Rahul Gupta >>>>> Dell EMC Isilon Engineering Team >>>>> +917200744656 <+91%2072007%2044656> >>>>> _______________________________________________ >>>>> 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" >>>>> >>>> >> >> >> -- >> Thanks & Regards >> Rahul Gupta >> Dell EMC Isilon Engineering Team >> +917200744656 <+91%2072007%2044656> >> > > > > -- > Thanks & Regards > Rahul Gupta > Dell EMC Isilon Engineering Team > +917200744656 <+91%2072007%2044656> > From owner-freebsd-hackers@freebsd.org Thu Aug 10 14:14:39 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E000DD3EB0 for ; Thu, 10 Aug 2017 14:14:39 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 439EE2947; Thu, 10 Aug 2017 14:14:39 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: by mail-qk0-x22e.google.com with SMTP id u139so4758973qka.1; Thu, 10 Aug 2017 07:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LQ/8NUf5/fp8AUf7Bpr6XYTCEb9jMB9X1GwwVDC5tr4=; b=vMqfGmv417ouJ8aZznkJvB6R3rBGyEe33kTq/RsJSjdpwIaCjNIk/Wh3bVsK6XdwFL lV/h8F4uiSQrRjCEYHAbyZIOtmBZ6l8bTe1EcqZSecAnEsAuN9oTNlg9PaQm4z+8f3FY DM0j5jEOLVOw3JNf2TdYQtZ3t8aYviWV9U4JFZpI5gdTFp8C67FLUqCeRWF84G4RbVSM 8hDM3eYlYiEjLGcZSzobpCBQ33gPYFcdSLSg5ASX6PVMpo/HGtbgnYGY+QHlkMMXSCnb EC8sGPfcU0+aF3797tqRDZOGi8eXk47n76BxdkrNRd2WoMjBCwqw1t65KGsUbrl3NRNJ mAuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LQ/8NUf5/fp8AUf7Bpr6XYTCEb9jMB9X1GwwVDC5tr4=; b=h2wGMuqKACT36mwbvARuQDw4z20nNu8BVTEBLN1K2/zQfmSQl32HDWmJfsRO3Ey5Ke RSEE6UNCtx0KwDijsJKLfIzyMUvyJbH3qHg0b906D0R/eKyfm+sdbk8tG8zUqX9oNcUH zb7L67PCDZX2hB+puGjx2rq2m4H4TXDma67wfqR+Lsr7EPMNn9iDTvqO0Jsehv5aHWkH hC2C/U24YG5QSvF4bj7C9xCnJbGQU1u0uTARXrAtJvu0vE9NWiXqa8coYQukJR2ZSEWF /fXgnDjMgqO2doaU3GYuBZudfW0ENNk78Y8ciA5bofC3/dfu5YumsED0dZHEMVUab57+ ojsQ== X-Gm-Message-State: AHYfb5gk8bVdBbJmdRofJjPx6Tl2/T3EmBposIbakfAtnQoRYEskAa4W PC5Qb5UvWJ7F0BVGig7qLy6/0RIbICC0 X-Received: by 10.55.160.20 with SMTP id j20mr15824382qke.119.1502374478072; Thu, 10 Aug 2017 07:14:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.228 with HTTP; Thu, 10 Aug 2017 07:14:36 -0700 (PDT) Received: by 10.140.28.228 with HTTP; Thu, 10 Aug 2017 07:14:36 -0700 (PDT) In-Reply-To: References: From: rahul gupta Date: Thu, 10 Aug 2017 19:44:36 +0530 Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: Shivansh Rai Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Thu, 10 Aug 2017 15:28:10 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 14:14:39 -0000 Thanks a lot. On 10-Aug-2017 7:41 PM, "Shivansh Rai" wrote: > Hi Rahul, > > Corresponding to each of the projects listed on that page, you'll see a > field named "Technical Contact". You can simply click on the link in that > field to visit the wiki page of the developer concerned with that project. > The common email format is something like this - if the id in "Technical > Contact" is for e.g. xyz@ then the corresponding email address will be > xyz@freebsd.org > > Hope this helps. > Regards, > -- Shivansh > > On Thu, Aug 10, 2017 at 6:15 PM rahul gupta wrote: > >> Hi Shivansh, >> >> I show some of small projects in : https://wiki.freebsd.org/JuniorJobs >> >> but i dont know to whom i should contacts for getting invole in this >> projects , i am really keen to work in this please help me out >> that how i can get involved in the development of this projects. >> I have very good knowledge of C, CPP and data structure and algorithm and >> i want to use my skills for this Dev and i am also interested to work in >> kernel side . >> >> On Thu, Aug 10, 2017 at 5:02 PM, rahul gupta wrote: >> >>> Hi Team, >>> Actually I am looking for Some Dev and i keen to work on File system so >>> please any body assigned me some work related to file system and guide me >>> the way that how can start contributing because i am quite beginner to this >>> so please help me . >>> >>> Thanks in advanced >>> >>> On Wed, Aug 9, 2017 at 7:31 PM, rahul gupta wrote: >>> >>>> This is great, thank you! >>>> >>>> On 09-Aug-2017 7:06 PM, "Shivansh Rai" wrote: >>>> >>>>> Hi Rahul, >>>>> >>>>> I can say that your interests greatly match with mine so I'd write >>>>> here what I did when I first got introduced to FreeBSD. It is possible that >>>>> you might find the following very easy as I'm a beginner :-) >>>>> >>>>> * I made my first contribution during Google Summer of Code '16. The >>>>> project ideas proposed every year are very cool and I'd suggest having a >>>>> look at some of the previous years' ideas as not all of them are taken up >>>>> (you can also have a look at the previous projects). A good thing about >>>>> them is that they have a mention of the difficulty level and the domain >>>>> knowledge required to participate, so you can easily filter out the ones >>>>> you might be interested in - https://wiki.freebsd.org/ >>>>> SummerOfCodeIdeas. >>>>> >>>>> * Look up the src tree and try to find a piece of code which interests >>>>> you (for e.g. it may be a base utility, say ls). Read through the code to >>>>> see how it works. It is a fun activity which I occasionally do. It is also >>>>> possible that in the process you might come up with an improvement. >>>>> >>>>> * *Testing* >>>>> I have come to realize that testing is a great way to explore and >>>>> learn a lot very fast (according to me). Firstly, you get to study how >>>>> things work. For e.g. if you want to perform testing of the TCP stack, you >>>>> might first start off learning about how TCP works. Since it is very >>>>> extensive, at a time you can pick up a single functionality (say, selective >>>>> acknowledgements) and study it end to end after which you try to come up >>>>> with ways of testing it. So you didn't study the entire theory behind TCP, >>>>> but now you know how this specific functionality works very well. Then you >>>>> proceed on with other functionalities and in some time you'll cover a lot >>>>> of theory. Secondly, the process of coming up with ways to test a specific >>>>> functionality proves to be a great (and fun) way to learn. And it is also a >>>>> great way of applying what you just learnt. Last (but not the least) you >>>>> are in luck if you come across a bug or an unexpected behavior! >>>>> If you are interested in testing, I'd suggest having a look at the >>>>> documentation of the FreeBSD testsuite: https://wiki.freebsd.org/ >>>>> TestSuite and also the TCP testsuite: https://github.com/freebsd- >>>>> net/tcp-testsuite (I am only familiar with these, other members might >>>>> add more to the list). >>>>> >>>>> * To start off contributing right away, I'd suggest having a look at >>>>> some of these links: >>>>> - https://wiki.freebsd.org/IdeasPage >>>>> - https://bugs.freebsd.org/bugzilla/describecomponents.cgi >>>>> - https://wiki.freebsd.org/JuniorJobs >>>>> >>>>> * Ask questions! The community members are extremely friendly (and >>>>> highly experienced, so you get to learn something new everytime you ask). >>>>> >>>>> * Also, you can have a look at how some of the community members first >>>>> started off (it is quite interesting): https://wiki.freebsd.org/ >>>>> HowWeGotHere. >>>>> >>>>> Over time I got to realize that the key is to always keep learning and >>>>> enjoying the entire process. In these fields (and any CS field for that >>>>> matter) you never get to stop being amazed by something new everyday. I >>>>> think I'm starting to go off-topic so I'll stop. >>>>> >>>>> PS. I am relatively very new to the community (around only 2 years) so >>>>> I'm sure the experienced and senior members will have some great and better >>>>> advice to share. My apologies in advance if I wrote something wrong above. >>>>> >>>>> Hope this helps. Thank you for your interest! >>>>> With best regards, >>>>> Shivansh Rai >>>>> https://wiki.freebsd.org/ShivanshRai >>>>> >>>>> On Wed, Aug 9, 2017 at 5:35 PM rahul gupta wrote: >>>>> >>>>>> Hi Team, >>>>>> >>>>>> As I am working in Dell EMC in Isilon Product , >>>>>> and i want to contribute in Free BSD Open source projects as i love >>>>>> to do >>>>>> codning, >>>>>> My Area of interested is Data Structure and Algorithm and i have fond >>>>>> of >>>>>> learn system related coding. >>>>>> kindly request you help me how i can help in the development of free >>>>>> BSD OS >>>>>> and >>>>>> also help me out that i how can contribute to free BSD and what is >>>>>> smallest >>>>>> thigh from i can start to contribute. >>>>>> >>>>>> your valuable help and guidance are awaited.. >>>>>> >>>>>> -- >>>>>> Thanks & Regards >>>>>> Rahul Gupta >>>>>> Dell EMC Isilon Engineering Team >>>>>> +917200744656 <+91%2072007%2044656> >>>>>> _______________________________________________ >>>>>> 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" >>>>>> >>>>> >>> >>> >>> -- >>> Thanks & Regards >>> Rahul Gupta >>> Dell EMC Isilon Engineering Team >>> +917200744656 <+91%2072007%2044656> >>> >> >> >> >> -- >> Thanks & Regards >> Rahul Gupta >> Dell EMC Isilon Engineering Team >> +917200744656 <+91%2072007%2044656> >> > From owner-freebsd-hackers@freebsd.org Thu Aug 10 19:54:03 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55726DDB64F for ; Thu, 10 Aug 2017 19:54:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660079.outbound.protection.outlook.com [40.107.66.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E819F6F5A0; Thu, 10 Aug 2017 19:54:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0192.CANPRD01.PROD.OUTLOOK.COM (10.165.218.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1320.16; Thu, 10 Aug 2017 19:54:00 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1320.019; Thu, 10 Aug 2017 19:53:59 +0000 From: Rick Macklem To: rahul gupta , Shivansh Rai CC: "freebsd-hackers@freebsd.org" Subject: Re: Need Help regarding contribution to Free BSD Projects Thread-Topic: Need Help regarding contribution to Free BSD Projects Thread-Index: AQHTEeOYEMA4nQnLkUO7Y4Ng/bwiLaJ9ojYAgABYprU= Date: Thu, 10 Aug 2017 19:53:59 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0192; 6:G02RzZNIPLTCnFuFeRsl0sKAEJfThZJ8/WsCs6MVUZsOIBa9CyGUk5VuO0b2RHNm2S61iHrCXJ3ERzZDpCR72GeCzQZn9UpKR2vVmhbVev35eAjZiyfiOGOzCGQiIgqUYOSAY4J4np2HAXBIalHm0xczPPNlnpCa0QDOFmR3zXtnjsr/LBep/Qg1k3ILGI/xWDOEUWk7xRsT+zESHtG7sepgztfi0b1FBpWLQM4ZZXc7LF2upasTJmQFIIRg4vBbCiG4zf+Y/KUVv8xql2jUdMT+IYR0huhLPmz5jv3sAVjwyveQHfZ0y04gtNLZ9Btli+iWzl7O/xhkw64oE8ZAmA==; 5:WCwe9tUlO0l3AuwAwhKltJmuxnfygUfA9GtS2GIJGvdoJjDltreGrtxwm0hBF6+7kwk3Bhpnl0z524dsGufcVRAYV75g7dyHsOSkJz/+QXmwdEVnNk1N6/cwe3bQh0NFbXQ51u6apnn16FrCeRWWqQ==; 24:xAvkQG3YFLqPl8/QFwM4Ml05Xes7+m0v87oIX2HHxsMxtIpOoJrgszgHgvwtk0fTeqIoDS4UvfDz/k3fDGIangQzMJtClhCNjIyL76VloG8=; 7:Pxtgn7KnWFRB+S0ZfM6gBStv8g8WqG5ZLXyiZQnTxVjYeMcRhGiyKG2g4qjxoLSYeRWvBz7aqGKcKqQ7JC9NCRyx1rcDIHdmzd+SGw8JNTF6B1by6wq1gSHyLT3bC23dwyQb3Q7pGzVCKtInxz7BUTp750RKyxdP4QpLcgLlTEshWitp9aVyftPwKJukgxUcAzyvtucTyNqWluGqfVtTIs/E6kjlXf3OM8l4dnK5vOA= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 21ce6342-b557-4a1e-f468-08d4e0298b36 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:YTXPR01MB0192; x-ms-traffictypediagnostic: YTXPR01MB0192: x-exchange-antispam-report-test: UriScan:(5213294742642); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123560025)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR01MB0192; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR01MB0192; x-forefront-prvs: 03950F25EC x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(199003)(189002)(53474002)(68736007)(3280700002)(2906002)(3660700001)(575784001)(77096006)(86362001)(102836003)(229853002)(6506006)(74316002)(7696004)(5660300001)(2950100002)(554214002)(93886004)(2900100001)(81166006)(50986999)(76176999)(81156014)(966005)(106356001)(14454004)(55016002)(25786009)(97736004)(8936002)(8676002)(33656002)(54356999)(105586002)(189998001)(101416001)(74482002)(6436002)(4326008)(53936002)(6306002)(9686003)(6246003)(39060400002)(305945005)(478600001)(437434002)(562404015); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0192; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Aug 2017 19:53:59.9216 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0192 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 19:54:03 -0000 rahul gupta wrote: [good stuff snipped] >>> Hi Team, >>> Actually I am looking for Some Dev and i keen to work on File system so >>> please any body assigned me some work related to file system and guide = me >>> the way that how can start contributing because i am quite beginner to = this >>> so please help me . >>> Well, first off I'll make a few "big picture" comments... - If you were expecting to hear from someone with a "go work on this", it w= on't happen. Why? Well, there isn't anyone. The FreeBSD project doesn't have a CTO or a com= mittee of wizards that make technical decisions. It is much more an "anonymous c= ollective". - Basically, you find something that interests you. At some point, when y= ou have a patch that you think the project will find useful, you propose it (eith= er on one of the email lists or reviews.freebsd.org). If others think it is usefu= l, hopefully some committer will pick it up and do the commit. - After a while, the committers get tired of doing this and suggest you = become a committer and do the commits yourself, etc... There is a group called "core" which are elected by the committers, but the= y mostly deal with logistics and not technical issues. They are the ones that decide= if an individual is to become a committer. Now, since you mentioned "file systems", I will note that Fuse is in need o= f some TLC. (There is a kernel component, which a few of us know a little about and a l= ibrary that at least I, know nothing about. It also could use a bunch of testing = with different file systems.) Here's a recent email thread related to Fuse: http://docs.FreeBSD.org/cgi/mid.cgi?87y3r0ankb.fsf In general, you'll want to join several email lists and what gets discussed= on them will give you an idea of what people are working on. (If you become a commi= tter, you pretty well have to watch these lists, so you might as well start now;-= ) A few I'm on are: freebsd-fs@, freebsd-current@, freebsd-stable@, freebsd-a= rch@ You will need a system that you can test source changes against head on, so= you should set up a head/current system. (head/current refers to the src tree found at repo.freebsd.org/base/head and is where the stable and release branches are created from, so that's where source patches go first). I think you can get read-only anonymous access to the subversion repo, but I haven't done so. Good luck and have fun with it, rick= From owner-freebsd-hackers@freebsd.org Thu Aug 10 20:02:17 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42B9DDDBA0E for ; Thu, 10 Aug 2017 20:02:17 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11B6C6F9BF for ; Thu, 10 Aug 2017 20:02:17 +0000 (UTC) (envelope-from raichoo@googlemail.com) Received: by mail-io0-x22a.google.com with SMTP id o9so13614884iod.1 for ; Thu, 10 Aug 2017 13:02:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rj/B/ZCdN9CLTsH8CHbxoGg8KIHKWQfSFtZ9qWe40+0=; b=Iv+3a9XHHQGhCvu6J6xzwhMPFBf0epK7LZyWnfH6g+U6QWdaMIuj1LmAMi7UMmKzuQ r1Tt+nQalHrDKqr1vp4M4mzoYPeHndzuS3RvO8Whn3fELkUPtz9TdpjGEBFG0/45Wtt1 aI/eU50Y7NKkBhiaVKQ98khknVlFKPzX+mGyBdvGAvhSbhFjSESPl28K49hOYmvDzcJw uX3BpA07aW3Va/7Sl+jkpTcU5woHY8+iT6YWN0HVqdhXlUrOrPqHothzD6E8a0okdMtn oy/bTW4LWphdC6zSKgSS+FgmxLdkyYp5Km2BhNQ4xjMPCwqBusVspoSF8+V4dJIKNdnK 6hIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rj/B/ZCdN9CLTsH8CHbxoGg8KIHKWQfSFtZ9qWe40+0=; b=SGh/N4FTQtCdWiOSFAYwBgABC/jSClmKAlwubr74jeROe0wI+i6nCz2qe3LjUSlo90 xoazydlHhvb8vX6Yko/e16A+ymu1QbQdy7KungIEMbngGQ/5dBTLEdhrytFIJiIV1QEY D4GlmV0BkK8qWKXyNhKMtXpUPRFDpV8YlyvqkP4T38kVsb3WQvUwRfu5ffkxHuZ3GHYR Y14R7+vnmfM/dzDWt6s/oOINCg4jyH40warEalNaMmnwnNrt9G6wP6gHBJ5RN1oyd6mj BBu/w1Kyx2rLbg1xLRxLJuS6LPKLbxVOLw6vYj0qcvjvE0mqZo8Q+1D294hBXghs185f Fwpw== X-Gm-Message-State: AHYfb5iD4VKuAoYnda2MrZ7J6Rjt0hE20elKCEeFfD8DVJmgSR39Aol3 ZH75wAw6jPgXbe2spCzewMaEk8o/Vg== X-Received: by 10.107.35.140 with SMTP id j134mr11530482ioj.94.1502395334250; Thu, 10 Aug 2017 13:02:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.19.225 with HTTP; Thu, 10 Aug 2017 13:02:13 -0700 (PDT) In-Reply-To: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> From: raichoo Date: Thu, 10 Aug 2017 22:02:13 +0200 Message-ID: Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: "Andrey V. Elsukov" Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 20:02:17 -0000 Oh boy, should have read more code before posting that ^^. Thanks a lot for your feedback :) I've modified that patch to make it use the macros defined in in6.h. I'm also quite aware that this patch might be rejected since it might break script depending on `ifconfig` output. But it's a useful little learning experience anyway :) Kind regards, raichoo Here's the new iteration: diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c index e93d94355e..e1d44395c9 100644 --- a/sbin/ifconfig/af_inet6.c +++ b/sbin/ifconfig/af_inet6.c @@ -167,6 +167,35 @@ setip6eui64(const char *cmd, int dummy __unused, int s, } static void +in6_addr_scope(const struct in6_addr *addr) +{ + if (IN6_IS_ADDR_LINKLOCAL(addr)) + printf("link-local "); + else if (IN6_IS_ADDR_SITELOCAL(addr)) + printf("site-local "); + else if (IN6_IS_ADDR_MULTICAST(addr)) { + printf("multicast "); + switch (__IPV6_ADDR_MC_SCOPE(addr)) { + case __IPV6_ADDR_SCOPE_NODELOCAL: + printf("node-local "); + break; + case __IPV6_ADDR_SCOPE_LINKLOCAL: + printf("link-local "); + break; + case __IPV6_ADDR_SCOPE_SITELOCAL: + printf("site-local "); + break; + case __IPV6_ADDR_SCOPE_ORGLOCAL: + printf("organization-local "); + break; + case __IPV6_ADDR_SCOPE_GLOBAL: + printf("global "); + break; + } + } +} + +static void in6_status(int s __unused, const struct ifaddrs *ifa) { struct sockaddr_in6 *sin, null_sin; @@ -272,6 +301,8 @@ in6_status(int s __unused, const struct ifaddrs *ifa) printf("scopeid 0x%x ", ((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_scope_id); + in6_addr_scope(&((struct sockaddr_in6 *)(ifa->ifa_addr))->sin6_addr); + if (ip6lifetime && (lifetime.ia6t_preferred || lifetime.ia6t_expire)) { printf("pltime "); if (lifetime.ia6t_preferred) { From owner-freebsd-hackers@freebsd.org Thu Aug 10 20:55:19 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 154B1DDCE8D for ; Thu, 10 Aug 2017 20:55:19 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F07971497 for ; Thu, 10 Aug 2017 20:55:18 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Thu, 10 Aug 2017 22:54:39 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1502398506; bh=O8KZtaGp7h6zz4LDtm0q6h2xTRPY9KBN12MOeEN6Mno=; h=Date:From:To:Subject:References:In-Reply-To; b=mQoGipsxli6SDwrhXf8yH9YoKoPHDSrgv6KxFCkrSQ8uB/rdZqh9639i1EACufWBC 8CtsvZtrF7cKaNod2joWRXSXAocZhzEwN9I57wHAzqVigyvTtUTJOENSZp9v9dlYGA hCqrQDd3e9iIMelU2/sSJpoHJm7EvDGMT4CQYUU86QQerCUIkZZNJoM06Sp2Qb6iC+ TRfHCVDlIzDocscIeLurqeXF5YNdY71m8kFqu64LHZAVpKxHYWhCGc2L1zpvr0twzw 7Sfw/pczswtYShQ/TnV7ykI0mUS0+pzyCqo0DJywMMB4aeArjv3fHnNAI0jcvyzFqd wbNgbefj3qGoQ== Message-ID: <20170810225439.Horde.1s8Qi_dlNtxgEigsNKbdrer@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-hackers@freebsd.org Subject: Re: devd in jail References: In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_OH8BZsQx_mwXwU-Il6ixHNk"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 10 Aug 2017 21:22:33 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 20:55:19 -0000 This message is in MIME format and has been PGP signed. --=_OH8BZsQx_mwXwU-Il6ixHNk Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Alan Somers (from Wed, 9 Aug 2017=20=20 13:14:20=20-0600): > On Wed, Aug 9, 2017 at 12:47 PM, Giulio Ferro wrot= e: >> Hello all, >> >> Setup : 11.1-STABLE FreeBSD 11.1-STABLE #0 r321925M amd64 >> >> >> I'm trying to create a fully virtualized desktop enviroment in a jail by >> means of installing there >> a xrdp-devel server + Xorg installation (xorg + xorgrdp). >> >> Everything seems to work until the moment when the X server actually tri= es >> to come up (after I choose session=3Dxorg, username + password) >> In the X logs in the jail, in fact, I have this error: >> >> ... >> [ 9768.824] (EE) config/devd: fail to connect to devd >> [ 9768.824] [config] failed to initialise devd >> >> >> I've checked on the host machine, and I don't have that error as everyth= ing >> works fine there... >> >> In my jail, I've setup the devfs like this (/etc/jail.conf in the host): >> >> --- >> exec.start=3D"/bin/sh /etc/rc"; >> exec.stop=3D"/bin/sh /etc/rc.shutdown"; >> exec.clean; >> mount.devfs; >> devfs_ruleset=3D1; >> >> path=3D"/usr/home/jail/$name"; >> >> myjail { >> host.hostname=3D"myjail.me.com"; >> vnet; >> vnet.interface =3D epair0b, epair1b; >> persist; >> } >> --- >> >> >> and in the /etc/devfs.conf everythink is commented out. >> >> In the /dev directory in the jail, I get both the devctl and devctl2 >> devices. >> >> As the devd demon is not running in the jail, I've tried adding >> devd_enable=3D"YES" >> >> in the rc.conf (jail), but when I try to start it, I get: >> >> # /etc/rc.d/devd start >> Starting devd. >> devd: Can't open devctl device /dev/devctl: Device busy >> /etc/rc.d/devd: WARNING: failed to start devd >> >> >> Do you know if I'm doing something wrong, or there's a proper way to hav= e >> devd running in the jail? >> >> I've thought that maybe I should use the devtcl2 device, as the devctl i= s >> used by the host, >> but I don't know how to specify that to devd... >> >> Thanks in advance for your help. >> >> Giulio > > Unfortunately, you're not going to be able to run devd(8) in the jail. > /dev/devctl can be opened by only one reader at a time, and that > reader is always devd(8). /dev/devctl2 is actually a completely > different device with a totally different interface. Apologies for > the confusing names. But you may not need to run a totally separate > instance of devd. The X server is probably trying to open either > /var/run/devd.pipe or /var/run/devd.seqpacket.pipe. ktrace would tell > you which. If you can bridge those sockets into the jail, then X > would probably run. Apart from using an explicit config of devices instead of HAL / devd,=20=20 if=20this is a X server connecting to a graphics card (instead of just a=20= =20 remote=20accessible framebuffer), the X-in-a-jail patches are needed, as=20= =20 the=20X server needs access to /dev/(k)mem and /dev/io (and /dev/drm). ATTENTION: doing this compromises the complete security of the entire=20=20 machine.=20The jail with the X-server can then access the entire memory=20= =20 of=20the machine, this means circumventing any kernel-level security=20=20 protection=20/ jail restrictions. Using the PR_ALLOW_* flags from current in 11.1 is ok (sys/sys/jail.h): ---snip--- /* Flags for pr_allow */ #define PR_ALLOW_SET_HOSTNAME 0x00000001 #define PR_ALLOW_SYSVIPC 0x00000002 #define PR_ALLOW_RAW_SOCKETS 0x00000004 #define PR_ALLOW_CHFLAGS 0x00000008 #define PR_ALLOW_MOUNT 0x00000010 #define PR_ALLOW_QUOTAS 0x00000020 #define PR_ALLOW_SOCKET_AF 0x00000040 #define PR_ALLOW_MOUNT_DEVFS 0x00000080 #define PR_ALLOW_MOUNT_NULLFS 0x00000100 #define PR_ALLOW_MOUNT_ZFS 0x00000200 #define PR_ALLOW_MOUNT_PROCFS 0x00000400 #define PR_ALLOW_MOUNT_TMPFS 0x00000800 #define PR_ALLOW_MOUNT_FDESCFS 0x00001000 #define PR_ALLOW_MOUNT_LINPROCFS 0x00002000 #define PR_ALLOW_MOUNT_LINSYSFS 0x00004000 #define PR_ALLOW_RESERVED_PORTS 0x00008000 #define PR_ALLOW_KMEM_ACCESS 0x00010000 /* reserved,=20=20 not=20used yet */ #define PR_ALLOW_ALL 0x0001ffff ---snip--- Then kern_jail.c needs a little patch: ---snip--- Index: sys/kern/kern_jail.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/kern/kern_jail.c (revision 321365) +++ sys/kern/kern_jail.c (working copy) @@ -200,6 +200,7 @@ "allow.mount.linprocfs", "allow.mount.linsysfs", "allow.reserved_ports", + "allow.kmem_access", }; const size_t pr_allow_names_size =3D sizeof(pr_allow_names); @@ -220,6 +221,7 @@ "allow.mount.nolinprocfs", "allow.mount.nolinsysfs", "allow.noreserved_ports", + "allow.nokmem_access", }; const size_t pr_allow_nonames_size =3D sizeof(pr_allow_nonames); @@ -3344,6 +3346,27 @@ return (0); /* + * Allow access to /dev/io in a jail if the non-jailed admi= n + * requests this and if /dev/io exists in the jail. This + * allows Xorg to probe a card. + */ + case PRIV_IO: + if (cred->cr_prison->pr_allow & PR_ALLOW_KMEM_ACCESS) + return (0); + else + return (EPERM); + + /* + * Allow low level access to KMEM-like devices (e.g. to + * allow Xorg to use DRI). + */ + case PRIV_KMEM_WRITE: + if (cred->cr_prison->pr_allow & PR_ALLOW_KMEM_ACCESS) + return (0); + else + return (EPERM); + + /* * Allow jailed root to set loginclass. */ case PRIV_PROC_SETLOGINCLASS: ---snip--- For 11.1 one little change is needed to get DRM access... see=20=20 https://svnweb.freebsd.org/changeset/base/320827 The=20jail then needs to be started with "allow.kmem_access" and=20=20 appropriate=20devfs rules (the jail needs rule 15 or 18, you may want to=20= =20 give=20more or less access, depending on your needs, review with care): ---snip--- [devfsrules_unhide_audio=3D5] add path 'audio*' unhide add path 'dsp*' unhide add path midistat unhide add path 'mixer*' unhide add path 'music*' unhide add path 'sequencer*' unhide add path sndstat unhide add path speaker unhide [devfsrules_unhide_input=3D7] add path 'atkbd*' unhide add path 'kbd*' unhide add path 'joy*' unhide add path 'psm*' unhide add path sysmouse unhide add path 'ukbd*' unhide add path 'ums*' unhide [devfsrules_unhide_xorg=3D8] add path agpgart unhide #add path console unhide add path dri unhide add path 'dri/card*' unhide add path nvidiactl unhide add path 'nvidia*' unhide add path io unhide add path mem unhide add path pci unhide add path tty unhide add path ttyv0 unhide add path ttyv1 unhide add path ttyv8 unhide [devfsrules_unhide_kmem=3D11] add path kmem unhide [devfsrules_unhide_zfs=3D12] add path zfs unhide # # This allows to run a desktop system in a jail. Think about what you want= to # achieve before you use this, it opens up the entire machine to access fro= m # this jail to any sophisticated program. # [devfsrules_jail_desktop=3D15] add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login add include $devfsrules_unhide_audio add include $devfsrules_unhide_input add include $devfsrules_unhide_xorg add include $devfsrules_unhide_kmem [devfsrules_jail_desktop_withzfs=3D18] add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login add include $devfsrules_unhide_audio add include $devfsrules_unhide_input add include $devfsrules_unhide_xorg add include $devfsrules_unhide_kmem add include $devfsrules_unhide_zfs ---snip--- Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_OH8BZsQx_mwXwU-Il6ixHNk Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZjMgPAAoJEKrxQhqFIICE3r4QAKRZ13aSrxL61UVR/tVl7Hvc qHINpAVwqRbssMnGrqF1ttCYgFe1K/mRcPTo9IKnDAKlLBMkmSMbmulLUtE1aJ00 EZSfbIXUxBBeZjub4Xp9du3lmuUjRxAajMqLh+HjlpOZkh+C0UY3DmaSfTLpbrR8 81ZB6NE4ZXskwEt6P5waf9X315G8QCs6JlOTCdf3iwKz/MW65MpUp1pOyaAB49ri CA6TVaAEutWxQ9WNAhR2LfblIryFttRWvN16WixQlAYGP1qSCdLqv80k7rgYp/bD sq5R9YOQAsXFIIiDacVCbF+d/1Vn4xz3oOJMVXB7nw4k7uM7DAcYKp6kI3hi070L 5rFT5TtlOl1GFza+sMnwg/kOXLx2j4lVdAr/oKqQQ1Eb26cjcuGyjyWP2Wb39Pqs Km16Xzp1iK0YPY/rTPLZUCW8NnqFec5AxzCFJzgockr6wFvvvFWw0DpA+M20RZNh /nxdxu0mKGaL6V+yoxMw5vqceP7NZWTTl5kQVNf64G5m0OagcgpCbyYsl6POtMAV OSzvAa9U0OYeCAfS4W41sSV5lJd8o3pvPaYmkoQqkcUxP7CUsKpg4O1gK2DG0TBy FxxENrLFP6p8WQ7ywCFRxJF14Y5y4AUi/Jbb6kBIz5H8Uto5uz4IY0y0hGyMSDnh vWVygzKRNaepXqZsArXb =Hj3o -----END PGP SIGNATURE----- --=_OH8BZsQx_mwXwU-Il6ixHNk-- From owner-freebsd-hackers@freebsd.org Fri Aug 11 10:02:06 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 989F5DC246F for ; Fri, 11 Aug 2017 10:02:06 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward106j.mail.yandex.net (forward106j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C2096A817 for ; Fri, 11 Aug 2017 10:02:06 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback10o.mail.yandex.net (mxback10o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::24]) by forward106j.mail.yandex.net (Yandex) with ESMTP id 8B5461804BBC; Fri, 11 Aug 2017 13:01:44 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback10o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id St8HBqhWuB-1ipeP0Vj; Fri, 11 Aug 2017 13:01:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1502445704; bh=XnO1gHdRqkHU9DW9NeXdwolK95iOt1vRCHI9zaSTadw=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=o1AnwcK9Ife21PXteFH/tU+ugaqxI95Qj16fwRMqUYIRcm8qdojIhYLypqzn8AcVK gbFczORnJuVtLVvoSlnm89NoNC1lmnJDL7WLD91DrhXTgk+mh0x15yCPnU1w9oAp6J LVl2Six+1UO/Yevk/9zKnlxGeMW5TSExM6m8GHgc= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 3dyM8vK2hw-1h8Cnv4M; Fri, 11 Aug 2017 13:01:44 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1502445704; bh=XnO1gHdRqkHU9DW9NeXdwolK95iOt1vRCHI9zaSTadw=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=o1AnwcK9Ife21PXteFH/tU+ugaqxI95Qj16fwRMqUYIRcm8qdojIhYLypqzn8AcVK gbFczORnJuVtLVvoSlnm89NoNC1lmnJDL7WLD91DrhXTgk+mh0x15yCPnU1w9oAp6J LVl2Six+1UO/Yevk/9zKnlxGeMW5TSExM6m8GHgc= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: raichoo Cc: freebsd-hackers@freebsd.org References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> Date: Fri, 11 Aug 2017 12:58:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6MqdLMl0xTfo6GaFUBr5lvRV2cGiHfxLq" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 10:02:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6MqdLMl0xTfo6GaFUBr5lvRV2cGiHfxLq Content-Type: multipart/mixed; boundary="UQbhUc9cppqNQJ8sRWmfUlEqK9hhbAJ51"; protected-headers="v1" From: "Andrey V. Elsukov" To: raichoo Cc: freebsd-hackers@freebsd.org Message-ID: <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> Subject: Re: `ifconfig` patch to resolve IPv6 scope names References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> In-Reply-To: --UQbhUc9cppqNQJ8sRWmfUlEqK9hhbAJ51 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10.08.2017 23:02, raichoo via freebsd-hackers wrote: > Oh boy, should have read more code before posting that ^^. >=20 > Thanks a lot for your feedback :) >=20 > I've modified that patch to make it use the macros defined in in6.h. I'= m > also quite > aware that this patch might be rejected since it might break script > depending on `ifconfig` > output. But it's a useful little learning experience anyway :) >=20 > Kind regards, > raichoo >=20 > Here's the new iteration: >=20 > diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c > index e93d94355e..e1d44395c9 100644 > --- a/sbin/ifconfig/af_inet6.c > +++ b/sbin/ifconfig/af_inet6.c > @@ -167,6 +167,35 @@ setip6eui64(const char *cmd, int dummy __unused, i= nt s, > } >=20 > static void > +in6_addr_scope(const struct in6_addr *addr) > +{ > + if (IN6_IS_ADDR_LINKLOCAL(addr)) > + printf("link-local "); > + else if (IN6_IS_ADDR_SITELOCAL(addr)) > + printf("site-local "); > + else if (IN6_IS_ADDR_MULTICAST(addr)) { > + printf("multicast "); > + switch (__IPV6_ADDR_MC_SCOPE(addr)) { > + case __IPV6_ADDR_SCOPE_NODELOCAL: > + printf("node-local "); > + break; > + case __IPV6_ADDR_SCOPE_LINKLOCAL: > + printf("link-local "); > + break; > + case __IPV6_ADDR_SCOPE_SITELOCAL: > + printf("site-local "); > + break; > + case __IPV6_ADDR_SCOPE_ORGLOCAL: > + printf("organization-local "); > + break; > + case __IPV6_ADDR_SCOPE_GLOBAL: > + printf("global "); > + break; > + } > + } > +} Hi, I'm not sure how it is useful configuring multicast addresses on the interface. I think there are only four possible useful cases: 1. loopback address should be marked as link-local 2. link-local addresses should be marked as link-local 3. site-local addresses should be marked as site-local 4. all other non multicast addresses should be marked as global Also, AFAIR, the site-local scope was deprecated a long time ago. --=20 WBR, Andrey V. Elsukov --UQbhUc9cppqNQJ8sRWmfUlEqK9hhbAJ51-- --6MqdLMl0xTfo6GaFUBr5lvRV2cGiHfxLq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmNf8EACgkQAcXqBBDI oXp6MAf+P3hJviN6fDQ9okEFyyqkgEBU7N4q8zCSUlXxpWXUyFIW7iXZAlv9Kjrd WRAsCiPZ0nlotQaE29JuFcBgzmfsilfXQnQLg1nfpkyO4OEWERANaS6zeEGhgLfP Hf4EQ2w0bPfU4prrjTc5mvnDl/tGIEpn0wUUzVl4GV1+yFO0EiiWYOPOCEA3uG1p RE8dADqwwn5+5wM/MEzs+cZBXCegXfjEdPh5tz5rs5fuiuJ2oCXBgPGdYk5yRhJz x2//5qZ75uMl2BjBwnhz9z6TKOFoWD8RoJR+8r0VCxaBaw/mIO47Abm1DGhuqf1x tUM/HPE12RtZ0Ebqwzk9GwPNF4VXsQ== =2xwf -----END PGP SIGNATURE----- --6MqdLMl0xTfo6GaFUBr5lvRV2cGiHfxLq-- From owner-freebsd-hackers@freebsd.org Fri Aug 11 11:15:53 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A62EDC6DA2 for ; Fri, 11 Aug 2017 11:15:53 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout04.t-online.de (mailout04.t-online.de [194.25.134.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 186756D70F for ; Fri, 11 Aug 2017 11:15:52 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd38.aul.t-online.de (fwd38.aul.t-online.de [172.20.26.138]) by mailout04.t-online.de (Postfix) with SMTP id 661E941B1CBE; Fri, 11 Aug 2017 13:15:50 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (r4M5JcZBYhCi1mJr2F0SXFDwG++GWfPWYXxtfssYBUcgFajDcoDU+vF-JNcZ2hqwKX@[84.154.108.129]) by fwd38.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dg7us-23dAPI0; Fri, 11 Aug 2017 13:15:46 +0200 Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: "Andrey V. Elsukov" , raichoo Cc: freebsd-hackers@freebsd.org References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> From: Stefan Esser Message-ID: <2cb5043d-57cb-d0a8-0432-caf72069afe6@freebsd.org> Date: Fri, 11 Aug 2017 13:15:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: r4M5JcZBYhCi1mJr2F0SXFDwG++GWfPWYXxtfssYBUcgFajDcoDU+vF-JNcZ2hqwKX X-TOI-MSGID: 87b06505-3726-4c42-83ee-8554b842210c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 11:15:53 -0000 Am 11.08.17 um 11:58 schrieb Andrey V. Elsukov: > On 10.08.2017 23:02, raichoo via freebsd-hackers wrote: >> Oh boy, should have read more code before posting that ^^. >> >> Thanks a lot for your feedback :) >> >> I've modified that patch to make it use the macros defined in in6.h. I'm >> also quite >> aware that this patch might be rejected since it might break script >> depending on `ifconfig` >> output. But it's a useful little learning experience anyway :) >> >> Kind regards, >> raichoo >> >> Here's the new iteration: >> >> diff --git a/sbin/ifconfig/af_inet6.c b/sbin/ifconfig/af_inet6.c >> index e93d94355e..e1d44395c9 100644 >> --- a/sbin/ifconfig/af_inet6.c >> +++ b/sbin/ifconfig/af_inet6.c >> @@ -167,6 +167,35 @@ setip6eui64(const char *cmd, int dummy __unused, int s, >> } >> >> static void >> +in6_addr_scope(const struct in6_addr *addr) >> +{ >> + if (IN6_IS_ADDR_LINKLOCAL(addr)) >> + printf("link-local "); >> + else if (IN6_IS_ADDR_SITELOCAL(addr)) >> + printf("site-local "); >> + else if (IN6_IS_ADDR_MULTICAST(addr)) { >> + printf("multicast "); >> + switch (__IPV6_ADDR_MC_SCOPE(addr)) { >> + case __IPV6_ADDR_SCOPE_NODELOCAL: >> + printf("node-local "); >> + break; >> + case __IPV6_ADDR_SCOPE_LINKLOCAL: >> + printf("link-local "); >> + break; >> + case __IPV6_ADDR_SCOPE_SITELOCAL: >> + printf("site-local "); >> + break; >> + case __IPV6_ADDR_SCOPE_ORGLOCAL: >> + printf("organization-local "); >> + break; >> + case __IPV6_ADDR_SCOPE_GLOBAL: >> + printf("global "); >> + break; >> + } >> + } >> +} > > Hi, > > I'm not sure how it is useful configuring multicast addresses on the > interface. I think there are only four possible useful cases: > 1. loopback address should be marked as link-local > 2. link-local addresses should be marked as link-local > 3. site-local addresses should be marked as site-local > 4. all other non multicast addresses should be marked as global > > Also, AFAIR, the site-local scope was deprecated a long time ago. Yes, but I think printing this extra information is still useful, at least for an less experienced user who does not have memorized the different scope types. It doesn't matter, if a (possible) configuration makes sense, this patch just reports what's already configured ... If a site-local address is in use, it will be immediately obvious, and thus it makes sense to include it in the scope list, even if it should never be reported ;-) I'd like to see this patch committed ... Regards, STefan From owner-freebsd-hackers@freebsd.org Fri Aug 11 13:24:57 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B23EDCE79D for ; Fri, 11 Aug 2017 13:24:57 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 573E771C3E for ; Fri, 11 Aug 2017 13:24:56 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id v7BDNSA9019483 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 11 Aug 2017 09:23:34 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: `ifconfig` patch to resolve IPv6 scope names To: "Andrey V. Elsukov" , raichoo Cc: freebsd-hackers@freebsd.org References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> From: George Mitchell Message-ID: <8f4a80a1-abd7-9eaa-d472-987383fc98e7@m5p.com> Date: Fri, 11 Aug 2017 09:23:15 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7C9PjUq8p0MNHLhe1ADNKtjX5UjSOK6hd" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Fri, 11 Aug 2017 09:23:35 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:24:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7C9PjUq8p0MNHLhe1ADNKtjX5UjSOK6hd Content-Type: multipart/mixed; boundary="BIspQ6RNEeGMVoS7JndfUHDDGLSnLgkuH"; protected-headers="v1" From: George Mitchell To: "Andrey V. Elsukov" , raichoo Cc: freebsd-hackers@freebsd.org Message-ID: <8f4a80a1-abd7-9eaa-d472-987383fc98e7@m5p.com> Subject: Re: `ifconfig` patch to resolve IPv6 scope names References: <8ebce8ed-5b3f-2b59-5b37-f6af7f3d4c2b@yandex.ru> <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> In-Reply-To: <92290fd6-fa7f-5d62-732a-1353af612297@yandex.ru> --BIspQ6RNEeGMVoS7JndfUHDDGLSnLgkuH Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 08/11/17 05:58, Andrey V. Elsukov wrote: > [...] > Also, AFAIR, the site-local scope was deprecated a long time ago. >=20 -- in a highly contentious discussion I'll never forget, in which one participant was responsible for 90% of the IPng mailing list postings for close to two weeks. -- George --BIspQ6RNEeGMVoS7JndfUHDDGLSnLgkuH-- --7C9PjUq8p0MNHLhe1ADNKtjX5UjSOK6hd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlmNr9AACgkQwRES3m+p 4fm/DBAAmPvC7gn5S69DQOJ1BZSxDWbhkIWv8S8RB8AGAwKLCIOLZWW3I27fzSDe uUoQhuauFtySv/3QvpNRA8ExHPC2lmwIthLsIlbpWSjt95iROf7MC8DGD57O8Sxd bWWU0GTB3M2W5tGX8NiMxkAS1ISOnnvvalYUsBw4rvTbCeuUTjQYNbmqB3uoNqHf RDRJg3IKt24cw1eiIg02kX2RVEtupSA0Kppjsf/GP5hX+6VXEajP5kSXZHAmV63f IRdKmp6RrLEr31Ma1KikIuKThgF2+qFTTboKaLH8QelpJ53CwaME03I3ZJEXgIPd LBul0KO0Uq+hovcR8ZDWEP5ueyW/BnPi7pL7/pSMnf46dcwZAzKx/7V/ocXeHjos Mp11ljO3WFEHB0mjQ5Nui88sI5KSgUArV3qGPoy5GEFzZOcUerxCcDoraJzpHko4 zwltwui4poF4gL/VDxGMibBmxbyu2GYNYfbfD4AHfPAWvaihECcHzISumYFkeynk 8gxNhd5OLtqa9rgl2EdlRykepIdWcZblPNkg/ELjCNI9Q+2ZPF6XXQlhQJym41FK 51l4A9S48Iii1VpmvppxhOamz46WKCToCQ7iBV/RLVLt015yQRifLosI4UhvDshP yJ8Pa3iLsJ8gsdSujU/JDJsP8KkfvcMSQf5iY5rmH3J3miGW8ss= =6sw9 -----END PGP SIGNATURE----- --7C9PjUq8p0MNHLhe1ADNKtjX5UjSOK6hd-- From owner-freebsd-hackers@freebsd.org Sat Aug 12 05:12:28 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF870D933B1 for ; Sat, 12 Aug 2017 05:12:28 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id DFF1D7411D for ; Sat, 12 Aug 2017 05:12:28 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v7C4wrwq070299 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 11 Aug 2017 21:58:53 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: Freebsd hackers list From: Yuri Subject: How can the shared memory object be undeletable when all shared memory segments belong to the same user? Message-ID: Date: Fri, 11 Aug 2017 21:58:52 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 05:12:29 -0000 I got this sequence of shm_* failures that I can't understand: 16151 scsynth CALL shm_unlink(0x803fdb3e0) 16151 scsynth NAMI "/SuperColliderServer_57110" 16151 scsynth RET shm_unlink -1 errno 13 Permission denied ... 16151 scsynth CALL shm_open(0x803fdb3e0,0xa02,0644) 16151 scsynth NAMI "/SuperColliderServer_57110" 16151 scsynth RET shm_open -1 errno 17 File exists ... 16151 scsynth CALL shm_open(0x803fdb3e0,0x2,0644) 16151 scsynth NAMI "/SuperColliderServer_57110" 16151 scsynth RET shm_open -1 errno 13 Permission denied Deletion operation fails with EACCESS, creation operation fails with EEXIST, opening operation fails with EACCESS again. So the object exists, but this user can't delete or open it. At the same time, 'ipcs -m' shows that all active segments belong to the same user. Failures are persistent with application restarts. Only renaming of the shared memory object in the code or reboot helped. Yuri From owner-freebsd-hackers@freebsd.org Sat Aug 12 05:17:57 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB961D939ED for ; Sat, 12 Aug 2017 05:17:57 +0000 (UTC) (envelope-from list@execve.net) Received: from lax012.relay.arandomserver.com (lax012.relay.arandomserver.com [198.252.106.48]) (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 AEC2C7437B for ; Sat, 12 Aug 2017 05:17:57 +0000 (UTC) (envelope-from list@execve.net) Received: from sng001.hawkhost.com ([119.81.196.36]) by se003.arandomserver.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dgOo2-0001hU-74 for freebsd-hackers@freebsd.org; Sat, 12 Aug 2017 00:17:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=execve.net; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References: In-Reply-To:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=lTaEYCbwlprnXImDTDsLhrBgBBsrgr3CBBPwurTv+PM=; b=C+8/t4xVsw39zKpNf4LDZibZYT TlMrx61JkqEK/BUp8vOIJL8eaPGEmLXopYetUtFgRrGFYKQp7e1hLv5yGyqwqPvZ9MJILGdtgDYYR Vn/ESEEfUmPqyMVssGgtUoAYF; Received: from mail-yw0-f170.google.com ([209.85.161.170]:34727) by sng001.hawkhost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dgOnx-004FO7-Go for freebsd-hackers@freebsd.org; Sat, 12 Aug 2017 13:17:45 +0800 Received: by mail-yw0-f170.google.com with SMTP id s143so32650112ywg.1 for ; Fri, 11 Aug 2017 22:17:45 -0700 (PDT) X-Gm-Message-State: AHYfb5hYxmyq+5+clMM50EPfCax1DYmJby9DiJ3Yqzj7tFDJjAkjfWvJ ws4uHih4Wd/4zW76uJ6GR6RC1Z/7zQ== X-Received: by 10.37.53.6 with SMTP id c6mr326127yba.54.1502515063771; Fri, 11 Aug 2017 22:17:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.20.135 with HTTP; Fri, 11 Aug 2017 22:17:43 -0700 (PDT) In-Reply-To: References: <598ADB65.8060701@grosbein.net> From: Gautam Date: Sat, 12 Aug 2017 10:47:43 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: freebsd-hackers Cc: "gautam@execve.net" X-Originating-IP: 119.81.196.36 X-SpamExperts-Domain: sng001.hawkhost.com X-SpamExperts-Username: relay Authentication-Results: arandomserver.com; auth=pass (login) smtp.auth=relay@sng001.hawkhost.com X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.05) X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZiEh/Q2y0dK8jSMLTE55fwqH0Nprjby6XDb qzVlIOQ03kAwPN4M+BNtq20Hh3O6Az9ismS84NPFas3IWADbmzJ9CZryIsNFvaBrlzs70sT7iKmx j3Zz/WM/IwRyPjIHIwDYsQbJYJbL3vFbmnz2PBd2yihJNBzs+iyvG5OI26kP0R5e973vehgRRMJd d1x498R9ApQmzlXa0qe0Fk7psoi5GzcWMr0czofRVh8rMXrt/SyLxLEJIkbWABkyXJwBVLal3W+/ PI81P534n3yak4n7EfJL2hMI4yCDSSr/HxDyN5bD8YyxjFtJAz2loLb4we0tFPPhpWPZ07PAOr0y wYIXuCj9wj08m7429e2ZOl/ZXvNM2/zURZVxzSV/eszOttj6AVIvY+ILsI7br1ka/ZVM5IUy3dIZ HZiQN/y5++vLOhnUf0KG89mNZvFB5dAV53iVu34H+eqH7iWBpUrKGrffGcXZKnwjnRMG9jJ/knTt +XiA50wwIMuM3BDtnoPm4HpIizaH26GaoEDwTtnQE6q4ZRNP3CPS3YZT5ODGEA+uOpLZY+4z/dwR ocCZGdc1cl9f9x/pKLS918QV+MmO1bAAEgjXIny51RJ3yyIOVX71wEukYspuIwswojsoiyB8OuXo nV+E7OMXRvgtdyMlnmWi9uF4/xGeHumbSXx1nykjkg3q5Go+y6UPrDLg9O+nbQFabxWNMr4EFN3D uwz3mGwtQnTIgDfxZ2/WGqYvyOVteVOdo6Dvr8fbMJVJ9/erL6/4IvMfhB2h/z0m0D607pH+pWX8 JH76UCDHe+VBXhtjrZr9RUQzcLUz45TvUuLctG5L8ZHLV0zHQOMuxVjpDkV6 X-Report-Abuse-To: spam@se001.arandomserver.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 05:17:58 -0000 Hi, On Wed, Aug 9, 2017 at 10:23 PM, Gautam wrote: > Hi, > > I just want to comment, that when I tested it there > was absolutely no need for any swap usage. I tried the test on a laptop > with 8GB RAM and > did it from the console mode. But it does seem that there might be some > request (read/write) to swap which > =E2=80=8Bcauses a lock up to the system.=E2=80=8B > > =E2=80=8BOne update on this one. I installed a custom stable/11 kernel an= d world (sched =3D 4BSD was the only change), and the problem is no longer seen. From my untrained eyes, it looks like some kind of swap request starvation causing a hang when ULE is in use.=E2=80=8B =E2=80=8BThanks, Gautam =E2=80=8B From owner-freebsd-hackers@freebsd.org Sat Aug 12 09:03:16 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7FAEDC7C0D for ; Sat, 12 Aug 2017 09:03:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4804D7E16F for ; Sat, 12 Aug 2017 09:03:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v7C93AHs089394 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 12 Aug 2017 12:03:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v7C93AHs089394 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v7C9392N089393; Sat, 12 Aug 2017 12:03:09 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 12 Aug 2017 12:03:09 +0300 From: Konstantin Belousov To: Yuri Cc: Freebsd hackers list Subject: Re: How can the shared memory object be undeletable when all shared memory segments belong to the same user? Message-ID: <20170812090308.GH1700@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 09:03:16 -0000 On Fri, Aug 11, 2017 at 09:58:52PM -0700, Yuri wrote: > I got this sequence of shm_* failures that I can't understand: > > 16151 scsynth CALL shm_unlink(0x803fdb3e0) > 16151 scsynth NAMI "/SuperColliderServer_57110" > 16151 scsynth RET shm_unlink -1 errno 13 Permission denied POSIX specifies that shm_unlink returns EACCES when Permission is denied to unlink the named shared memory object. Rationale for the shm_open() explains that actual interpretation of EACCES for shm_*(2) functions is implementation-defined. FreeBSD requires the caller euid to have read/write permissions to the shared memory segment for the unlink to be allowed. > ... > 16151 scsynth CALL > shm_open(0x803fdb3e0,0xa02,0644) > 16151 scsynth NAMI "/SuperColliderServer_57110" > 16151 scsynth RET shm_open -1 errno 17 File exists > ... > 16151 scsynth CALL > shm_open(0x803fdb3e0,0x2,0644) > 16151 scsynth NAMI "/SuperColliderServer_57110" > 16151 scsynth RET shm_open -1 errno 13 Permission denied > > > Deletion operation fails with EACCESS, creation operation fails with > EEXIST, opening operation fails with EACCESS again. So the object > exists, but this user can't delete or open it. Which is consistent with the euid not having read/write permissions on the segment. > At the same time, 'ipcs > -m' shows that all active segments belong to the same user. Failures are > persistent with application restarts. Why do you think that SysV IPC shared memory, which is displayed by ipcs(8) tool, has any relations to the POSIX shared memory ? > > > Only renaming of the shared memory object in the code or reboot helped. Root should be able to unlink it. From owner-freebsd-hackers@freebsd.org Sat Aug 12 06:03:43 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C31E1DB5BC8 for ; Sat, 12 Aug 2017 06:03:43 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 774CA75899; Sat, 12 Aug 2017 06:03:43 +0000 (UTC) (envelope-from rkg10100@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id x191so30187608qka.5; Fri, 11 Aug 2017 23:03:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zc0iDYNwEhhXDgprc5GnLBAqgiSBS+y5+34OjVyZ0s0=; b=SBebEZ6H/Cyb9Pbv+ib5xesvzlLTsh6bW6c/4GJEGbX99V0ESlmEBc1U+fDNrGgYZ6 h2HrmepWMjYNXaE3tRZOWjM6hp0E7ESib+7/FYiOvgru3Y4pMi6stCfvrcbDAlbBhsdF pXvghPsKq6IuQDjZpOjwdkaZZq1Huoijh7laCDrO9RUF+EfKjufaW+EaUqhdkmb8VImX NMtlutx6rrinPRda2rDiIh2etsJCrF6Wfkc3TjxHKRqrUbRzmJAENrVmxfAeP1D0W9QV M4xsptjUQhzldEy9UAWqeKpN2XiXSO4FjlQFEKjkzHXSnCWh6ZFkgfhw+ZNZuehLMSF8 /K9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zc0iDYNwEhhXDgprc5GnLBAqgiSBS+y5+34OjVyZ0s0=; b=aUA/mO6R2cx79Xb4U/jEqO5Rb4yPquTg7G718HX9PQSRkBzEly7ms2+yHQaL5lDfrr k4dz/PSnh+hO6dT5EYb2bD3xNEpyWI3llpxHlGSW1kEbpl9At58Bj0ihl1xQQLM1gXHU ywX5EToPjySNRaPUZJyh/TP0bjn9VvAd4EDyTXMwIZrQLMWuSFmaK9466otlm0GkMMrG 9g/+H5XTC8E8ZJ7bZqU9cdaJD7STR7XtlEOXYYXB7n8NNBdj4iJ71SDItI74cu4D9lPn 9/utEx1M1TH0WG7zk+sxScbKHaVyAxfMCF9xV9ILg37OHlaL3YVx2TVogWY0Sn3cRzay Vc+Q== X-Gm-Message-State: AHYfb5hsZvwbeHI7yWQogmAteEAnsbXTjIL3Et8GmyrbxhVtVVUXd1zm Z7HIpXCuXlJnV5/r2pTZA/VfLQl6KD63 X-Received: by 10.55.161.13 with SMTP id k13mr21847957qke.168.1502517822227; Fri, 11 Aug 2017 23:03:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.228 with HTTP; Fri, 11 Aug 2017 23:03:41 -0700 (PDT) Received: by 10.140.28.228 with HTTP; Fri, 11 Aug 2017 23:03:41 -0700 (PDT) In-Reply-To: References: From: rahul gupta Date: Sat, 12 Aug 2017 11:33:41 +0530 Message-ID: Subject: Re: Need Help regarding contribution to Free BSD Projects To: Rick Macklem Cc: Shivansh Rai , freebsd-hackers@freebsd.org X-Mailman-Approved-At: Sat, 12 Aug 2017 11:50:51 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 06:03:43 -0000 This is great, thank you so much! On 11-Aug-2017 1:24 AM, "Rick Macklem" wrote: > rahul gupta wrote: > [good stuff snipped] > >>> Hi Team, > >>> Actually I am looking for Some Dev and i keen to work on File system so > >>> please any body assigned me some work related to file system and guide > me > >>> the way that how can start contributing because i am quite beginner to > this > >>> so please help me . > >>> > Well, first off I'll make a few "big picture" comments... > - If you were expecting to hear from someone with a "go work on this", it > won't > happen. > Why? > Well, there isn't anyone. The FreeBSD project doesn't have a CTO or a > committee > of wizards that make technical decisions. It is much more an "anonymous > collective". > - Basically, you find something that interests you. At some point, when > you have a > patch that you think the project will find useful, you propose it > (either on one > of the email lists or reviews.freebsd.org). If others think it is > useful, hopefully > some committer will pick it up and do the commit. > - After a while, the committers get tired of doing this and suggest you > become a > committer and do the commits yourself, etc... > There is a group called "core" which are elected by the committers, but > they mostly > deal with logistics and not technical issues. They are the ones that > decide if an > individual is to become a committer. > > Now, since you mentioned "file systems", I will note that Fuse is in need > of some TLC. > (There is a kernel component, which a few of us know a little about and a > library > that at least I, know nothing about. It also could use a bunch of testing > with different > file systems.) > Here's a recent email thread related to Fuse: > http://docs.FreeBSD.org/cgi/mid.cgi?87y3r0ankb.fsf > > In general, you'll want to join several email lists and what gets > discussed on them > will give you an idea of what people are working on. (If you become a > committer, > you pretty well have to watch these lists, so you might as well start > now;-) > A few I'm on are: freebsd-fs@, freebsd-current@, freebsd-stable@, > freebsd-arch@ > > You will need a system that you can test source changes against head on, > so you should > set up a head/current system. (head/current refers to the src tree found at > repo.freebsd.org/base/head and is where the stable and release branches > are > created from, so that's where source patches go first). I think you can get > read-only anonymous access to the subversion repo, but I haven't done so. > > Good luck and have fun with it, rick From owner-freebsd-hackers@freebsd.org Sat Aug 12 15:23:12 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7867DDD1FC for ; Sat, 12 Aug 2017 15:23:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7DAB64D02 for ; Sat, 12 Aug 2017 15:23:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id c74so28291014iod.4 for ; Sat, 12 Aug 2017 08:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KwO/XVBpOG7QTfik8pt8RmLifkNZKiSd91RRNBg8IRk=; b=PGxIv3SQOznX6n6BcXseYcntjC5r00YadA36o3jWnX7vG4j5jpj5Of7z50jqYiB1rw JM1poHe0mlQ3zW+0ZA6LOIPAdEGFfb4ae+jufb7jQHR71brRB0efMXuEDRny0XUUmkay qCbjM8uAJ0We5k2aZrGmLHRWrdg1YpkOaymjI9BGk1WnL2UttwPBxYLlg5K+IV79ndg6 cNzaUUMXY5iAgzCLcHWdeyziLpVCbg/Gm9LQjyui5kMCyLqH5w1BKqZW0VFjgwVG6bKk TnX9rpWcen9j/iGifvxhMm1xPU0BHYHQU1X5Tw6njZcKLJCdd2NCiOt+M0HZoL0MFsJl 69vQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KwO/XVBpOG7QTfik8pt8RmLifkNZKiSd91RRNBg8IRk=; b=e1ur8n7Ii+vUrwXuDPP+ll6FkiWvjHk9DTQYv1X8HRWylS7BbsTVZe6Vxv4NILUtlD FqEGVzVTIKeTqsHDKt0ODlobPxJuE1PTtV/kensDWTrUqJFETiJyleP9unW7lF3ywY9w eQJtXaxdpY6frf3bhj36akTMRjr7fryfc0SJx0dulbFilyuCE2ZNFDhZaI48j3s7MATX fllnsLozIdEIUa+guWRGqumG/jI3m7o4pLc7fp3JhDKaq8NAuk7Kpq1okof+mACTlk8r D7sWGTEERInwUfoQ2xp7xjJFZLvS9j/1RGbCRT2qtlxqFXSusPI/co0VynBOh9DNMAFi sphA== X-Gm-Message-State: AIVw112j0uoMerlxCwOGfZjUIqUXd2n2Ag+5duaLfoEQ7YPBXDn/4l7T y7VmZYqZrImfxX7t/62qrNfImVvcwxvT X-Received: by 10.107.145.2 with SMTP id t2mr15283396iod.160.1502551391893; Sat, 12 Aug 2017 08:23:11 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Sat, 12 Aug 2017 08:23:11 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:e113:b8b8:d4d8:acf3] In-Reply-To: References: <598ADB65.8060701@grosbein.net> From: Warner Losh Date: Sat, 12 Aug 2017 09:23:11 -0600 X-Google-Sender-Auth: tVgrs3Z4yk1vwvkkwhFAGQejQKI Message-ID: Subject: Re: Freebsd 11.0 - system freeze on intensive I/O To: Gautam Cc: freebsd-hackers , "gautam@execve.net" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 15:23:13 -0000 On Fri, Aug 11, 2017 at 11:17 PM, Gautam wrote: > Hi, > > On Wed, Aug 9, 2017 at 10:23 PM, Gautam wrote: > > > Hi, > > > > I just want to comment, that when I tested it there > > was absolutely no need for any swap usage. I tried the test on a laptop > > with 8GB RAM and > > did it from the console mode. But it does seem that there might be some > > request (read/write) to swap which > > =E2=80=8Bcauses a lock up to the system.=E2=80=8B > > > > =E2=80=8BOne update on this one. I installed a custom stable/11 kernel = and world > (sched =3D 4BSD was the only change), and the problem > is no longer seen. From my untrained eyes, it looks like some kind of swa= p > request starvation causing a hang when ULE is in use.=E2=80=8B > I did some patches a few years ago that separated out geom requests into their own uma map, if you wanted and hacked the swap pager to use that to ensure that it always had BIOs available to do it's I/O. Maybe I should dust them off and see if they help you. They didn't seem to help me too much, but didn't hurt too much either. There's still the issue of some drivers not pre-allocating requests, which is what makes the deadlock possible in the first place. Warner From owner-freebsd-hackers@freebsd.org Sat Aug 12 19:42:42 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8CEADC6F93 for ; Sat, 12 Aug 2017 19:42:42 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CEF16EF67 for ; Sat, 12 Aug 2017 19:42:42 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-pg0-x22a.google.com with SMTP id y129so27267410pgy.4 for ; Sat, 12 Aug 2017 12:42:42 -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=bB6Fyc/yvlFyww0dTbBc2r4JTVfm76eu+nOPGPKnSB8=; b=I/UsEvTZVRQ6oquvyIAndfdhaBv7GWq8Pc1uAep3I7zV/6W0eLseWzmt9p1cOjiLmW NDLwskm06AbgiSaqZNEUp3sjkd9mTSY2UQQSVZA/qY9r+x89jGfcVr76fzoZVYpuIdgT OOOnVZgGPRDsAmtBZ7A1zGy5dkuncSf6cfFCHDBUgkn1ydkl2aS0eBqtEzFosxwk8I4t ddHE76DNz+waY44Xv2OT7LEa96clO4V+/pYg/mOtpZkIJUBUhoMNu0Xcbb4Jkcy1F4M7 L5ZJ7ZKhZfQfhs2Qc/B8LkMZCMUWJFC+k0H1kc1rBxjQO2oOyEyrlk6srSWqQiFoIRuq puXA== 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=bB6Fyc/yvlFyww0dTbBc2r4JTVfm76eu+nOPGPKnSB8=; b=awHIjbauIzrkkr55juSKLPpPewRoxePNb5rwcQge3RtcMhxgtxQUjhxng6H11Dh/nk j8t23gD3VD5EZq4ttyjs4x4tlYwb0AQdS8GW2aaBJNL/CxGeND9wxbUWgvPUZNrkDT5x XIGi1d6xFheB6+bv9LMjQlrPUm8ypgJf815ZvaBTLw6pPW1EyzWWrcy1OYXZq7qDKAKQ OAJfoq33TT8/4+cHYtMp+LnW5UU8WwrcafU7/M3dxojUJKQPc8Rrjvu9Wt3czSHJcdKK l5BNcdspUhS0uRYXPBwrhjQHVQWuRYMQJUAF+CbTgSDAgLk4MkPtU/g+AlCD2yR8lhO6 yeNw== X-Gm-Message-State: AHYfb5hPL4G9Kf9fY5EuQJrqv3SFKGIWtW0lZK9s27Y6v0qBcxPArwi2 43KFoLFbTx0RsU3iFD8tg9fW8rO/G7TSG+E= X-Received: by 10.98.138.22 with SMTP id y22mr20485802pfd.9.1502566961831; Sat, 12 Aug 2017 12:42:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.183.208 with HTTP; Sat, 12 Aug 2017 12:42:21 -0700 (PDT) From: Farhan Khan Date: Sat, 12 Aug 2017 15:42:21 -0400 Message-ID: Subject: Monitor kernel variable with ddb(4) To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 19:42:42 -0000 Hi all, I am trying to figure out where a net80211's vap flags are modified. I see that memory is originally allocated here: http://src.illumos.org/source/xref/freebsd-head/sys/net/if.c#445. However, I cannot figure out where the ifp->if_flags and if->if_drv_flags are ever modified in the kernel. Someone suggested using ddb(4), so I entered the live debugger using sysctl debug.kdb.enter=1 I then set a breakpoint at if_alloc. However, I cannot seem to figure out the next steps to monitor where the ifp->if_flags or if->if_drv_flags are updated. Full explanation - My kernel module is immediately unloading, but I am not certain why. I traced it back in the ieee80211 code to those flags, but not sure where they are updated. Any ideas? Thank you! -- Farhan Khan PGP Fingerprint: 782F 342B 5B08 0D2F F4E8 82C3 FFA1 CAE1 6536 51CA From owner-freebsd-hackers@freebsd.org Sat Aug 12 20:17:02 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BDEDDC7BBB for ; Sat, 12 Aug 2017 20:17:02 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (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 E19CD6FD30 for ; Sat, 12 Aug 2017 20:17:01 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v7CKChPr034191 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 12 Aug 2017 22:12:44 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: khanzf@gmail.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v7CKCcxq028571 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 13 Aug 2017 03:12:38 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Monitor kernel variable with ddb(4) To: Farhan Khan , freebsd-hackers@freebsd.org References: From: Eugene Grosbein Message-ID: <598F6131.3090002@grosbein.net> Date: Sun, 13 Aug 2017 03:12:33 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 20:17:02 -0000 13.08.2017 2:42, Farhan Khan пишет: > Hi all, > > I am trying to figure out where a net80211's vap flags are modified. I see > that memory is originally allocated here: > http://src.illumos.org/source/xref/freebsd-head/sys/net/if.c#445. However, > I cannot figure out where the ifp->if_flags and if->if_drv_flags are ever > modified in the kernel. > > Someone suggested using ddb(4), so I entered the live debugger using sysctl > debug.kdb.enter=1 > > I then set a breakpoint at if_alloc. > > However, I cannot seem to figure out the next steps to monitor where the > ifp->if_flags or if->if_drv_flags are updated. > > Full explanation - My kernel module is immediately unloading, but I am not > certain why. I traced it back in the ieee80211 code to those flags, but not > sure where they are updated. > > Any ideas? Thank you! What driver do you use? There are lots of kernel level files that change ifp->if_flags and if->if_drv_flags: $ grep -lER '\ Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A18B4DC81D1 for ; Sat, 12 Aug 2017 20:33:25 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25701705A3 for ; Sat, 12 Aug 2017 20:33:25 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id m86so27344113lfi.4 for ; Sat, 12 Aug 2017 13:33:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=cc:in-reply-to:references:subject:to:mime-version :content-transfer-encoding:from:date:message-id:user-agent; bh=tLXr13QkGOP+hdS65Zd6TMWiE261FQDaHOJWzEj7FNc=; b=txn8LGP4cAwRBOgfxAeSnk4zWKhc6LQkmfP8odzJBAwO4xkmNvVDFeswB8S1pLXCrZ xtDn9CYvYiNQWxaPFYNvG9EBhfzIP2pKrOGyCpKGaK+gqbuftdlZq0o8loDgMHic9z48 gVbA9GkJNTv0DHia8fr3gfuQLm2uUt6ZH439oo3nRMdv3PICSvLZQ4DhIlAhm4iepqH5 1WOo30uWDT/qhw6PE4L/UmW0q/gATu883ElV14id7zd6koiWMU4qDMwap+J0YpOew8cR Ssqhbr//W8M7ywlBldLzZIMqxzIlx9y/RpfrKntFVCB2/1iOdPIH3uK3o8k4soFEoVNU wmBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:cc:in-reply-to:references:subject:to :mime-version:content-transfer-encoding:from:date:message-id :user-agent; bh=tLXr13QkGOP+hdS65Zd6TMWiE261FQDaHOJWzEj7FNc=; b=NA8JYIn/sxX6WoXLANjlrzgYlxdkbIsJb2b6aHulHINOS23clWoG+/ZmLf2KaSLR4f IewSbHtqq7AFwd7TU0TNBMntSUtiRzNss0FNuyFTprQjUFeTjTo+MbBGOiLVQ/P8IlEU 0GJjNvqK6d3eX0slpJeUPSuvtGa7M/40V0KnWgKUxLrGB98wqi5juA7728EIQ1B+xDSI MDQ7h3mtWbvnoo97uI825lOhP6cvyjDNxgxbRV3cgUNauyE/Gwnrh5UDZlJ230iLiLI1 kGK50vUDfxY9tji75wZAF/hdHPo9Ej0Oaq4gCNbYpWTHuvGzN5OtJxVkSAOcHsLTCRlV IRdw== X-Gm-Message-State: AHYfb5jtzfsSDsvE7/Hph18eZPzu0XOdVEmDjauL5hUL7sSXDxjs3ye7 OODNCMaGbyMcOQ== X-Received: by 10.46.21.71 with SMTP id 7mr6589672ljv.74.1502570002871; Sat, 12 Aug 2017 13:33:22 -0700 (PDT) Received: from thinkpad-x220 (46-133-240-73.dialup.umc.net.ua. [46.133.240.73]) by smtp.gmail.com with ESMTPSA id c89sm730762lfb.78.2017.08.12.13.33.19 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 12 Aug 2017 13:33:22 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Cc: freebsd-hackers@freebsd.org In-Reply-To: References: Subject: Re: Monitor kernel variable with ddb(4) To: "Farhan Khan" MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Date: Sat, 12 Aug 2017 22:56:51 +0300 Message-ID: User-Agent: Opera Mail/12.15 (FreeBSD) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 20:33:25 -0000 Sat, 12 Aug 2017 22:42:21 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Farhan Khan : > Hi all, > > I am trying to figure out where a net80211's vap flags are modified. I= = > see > that memory is originally allocated here: > http://src.illumos.org/source/xref/freebsd-head/sys/net/if.c#445. = > However, > I cannot figure out where the ifp->if_flags and if->if_drv_flags are e= ver > modified in the kernel. > > Someone suggested using ddb(4), so I entered the live debugger using = > sysctl > debug.kdb.enter=3D1 > > I then set a breakpoint at if_alloc. > > However, I cannot seem to figure out the next steps to monitor where t= he > ifp->if_flags or if->if_drv_flags are updated. > > Full explanation - My kernel module is immediately unloading, but I am= = > not > certain why. I traced it back in the ieee80211 code to those flags, bu= t = > not > sure where they are updated. > > Any ideas? Thank you! Hi, You can use 'show all vaps/a' command to show all currently existing vap= s (see ieee80211_ddb(9) for other commands).