From owner-freebsd-hackers@freebsd.org Sun Mar 27 23:34:39 2016 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 B784EADFF47 for ; Sun, 27 Mar 2016 23:34:39 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 97CEC14A7 for ; Sun, 27 Mar 2016 23:34:38 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id D68A910CF for ; Sun, 27 Mar 2016 23:34:31 +0000 (UTC) Subject: EFI GELI boot update From: Eric McCorkle Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13D15) Message-Id: Date: Sun, 27 Mar 2016 19:34:30 -0400 To: "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2016 23:34:39 -0000 Just to give an update, as I know there were some others looking into GELI s= upport for EFI, I've made modifications to boot1 to support "provider" modul= es, which basically handle subpartitions. You can track my work on this her= e:=20 https://github.com/emc2/freebsd/tree/geli_efi I had considered using the EFI API more for this (creating device nodes, add= ing protocols, and binding device paths), but decided not to in order to kee= p loader working with a GRUB setup. As for actual GELI support, here's the roadmap I'm considering: * Abstract the use of struct dsk out of the core data structures * Abstract the crytpto, password-asking, and key material storage out of the= GELI code into some kind of boot crypto framework. Ideally, this would be s= modules-type framework with BIOS and EFI software crypto modules provided. = Hardware crypto could be supported in the future by adding more modules. * (Possibly) come up with a better way to transfer key material to loader an= d the kernel * Mirror the functionality of the provider modules in loader I welcome any suggestions on any of this.= From owner-freebsd-hackers@freebsd.org Mon Mar 28 16:54:47 2016 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 2065FAE06D6; Mon, 28 Mar 2016 16:54:47 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x242.google.com (mail-vk0-x242.google.com [IPv6:2607:f8b0:400c:c05::242]) (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 BCC151232; Mon, 28 Mar 2016 16:54:43 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x242.google.com with SMTP id a62so15433430vkh.0; Mon, 28 Mar 2016 09:54:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=Y4h4QLpwq0RC117Zi2XZmFA1vaqUXTUApbcLjfbgMW4=; b=mszRGpf7RBgkKSoLInzey/cAmJ3X/5QkinR5U7WgIV7cI1LKbf6o1xNnZ5QPjvDYWJ oJzLh8qwmINTfEXGsk5dQBcFGW3/giwFSxWzMhm8RFdnarVyQSEEuKr0/EVO1V7YQDkg 2OaVRjRRt5D1PR6gqHJRQkxpFWnr9H+BqWKmlgKOO7blyYmpgXmX5tO8rXsl3yNFjna7 HtDJuAnhwnKvfZzrRQ6NFsKzsAVmIFdDQKArIjbVFt1wYY3MwCTNdKTReKWhxM3+jIMh h7a95xzM8wlkBLbJIj5cuUWtXiKSce9jPNj5pJH/WPUTWLlZhNTIJ/PzaCzWrqZ5lpxO 3bzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Y4h4QLpwq0RC117Zi2XZmFA1vaqUXTUApbcLjfbgMW4=; b=kwWxL4a569/nC2ArURnh/ZQ5+PHcUVu453WCVBrotwbtJ37SLEOIhHSO/FtNhSjw5V y0fS5p3Tkq9CdpI38fwMkbZFJNXv6Iuig8dB8z3E/eFXUvFb9X/zk5AMu8Fnrl8uk1ms V/CEf5j1vtr/7LiuI53zYDPA4288ustB2KBqzFT0DF2S3XtBNH8TML91dQcx1jKz9H2M sqfQYCb6jPVsFbLdYc8Lu6AOBhRI/8aRjca4A72uolLQxnzGwLnSUXnW9K4/HBrDcP7o nOKe+K0Vkv1ZO0/8PfOKxft38+o6ioKs4mwxRfzhJsj9jzHR8RrJAbPsuGnShavHJzn2 NpZw== X-Gm-Message-State: AD7BkJJ5vmC4ZtLiWF7H9POB4ELLzsvAYcSTK0yx89PyN0jA6NX49cEZX4W6/gMYtp8ROlYsYy5Kuq0xQJgMsA== MIME-Version: 1.0 X-Received: by 10.176.65.73 with SMTP id j67mr14888929uad.24.1459184082862; Mon, 28 Mar 2016 09:54:42 -0700 (PDT) Received: by 10.103.37.196 with HTTP; Mon, 28 Mar 2016 09:54:42 -0700 (PDT) Date: Mon, 28 Mar 2016 12:54:42 -0400 Message-ID: Subject: Let me try this again From: Joe Nosay To: David Wolfskill , Dru Lavigne , "Donna L. Clark" , info@freebsdfoundation.org, Team Open Source PowerPC Notebook project , Bill Buros , inquiries@un.org, vinux-development@googlegroups.com, vinux-support@googlegroups.com, vinux-documentation@googlegroups.com, Theo de Raadt , Eric Oyen , Tomasz CEDRO , Ngie Cooper , Ngie Cooper , Ngie Cooper , FreeBSD PowerPC ML , FreeBSD Hackers , "SELCommunityAffairs@am.sony.com" X-Mailman-Approved-At: Mon, 28 Mar 2016 17:05:17 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2016 16:54:47 -0000 I propose a project of building upon the idea of the Open Source PowerPC laptop project. The original project idea had the following: Accessibility for visually impaired. Accessibility for audio impaired should be added. Multi-system boot with work on the Grub bootloader for PowerPC systems. BSD and Linux cross reference and participation. Introduction of the Cherokee syllabary and Guarani alphabet along with language and keyboard design. The laptop would be available to schools to purchase in order to aid and assist the local communities around the school in projects beneficial to all humanity and the planet. The email records should have this, along with mailing lists posts. I am presenting this again before the different mailing lists, the UN, and the general public. Yes, I am presenting this project idea before the UN; so, you now know that I am absolutely serious about this. And anyone who wishes to complain about an idea beneficial to others should rethink about themselves. To Vinux and others: The project idea was thought/misunderstood to be a blatant plagiarism of the Open Source PowerPC laptop Project, it is not. The idea was to join the Open Source community in this project for the benefit of others. I will continue to bring this project idea before as many groups as possible. This is also brought before Sony and IBM. I ask that the FreeBSD foundation reconsider the project idea and work with others to make this possible. Theo de Raadt: No one on any forum nor anyone on any mailing list provides for my needs. I am homeless and my needs are food, water, supplies. From owner-freebsd-hackers@freebsd.org Tue Mar 29 02:33:10 2016 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 605A5AE1541; Tue, 29 Mar 2016 02:33:10 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (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 D8DA01119; Tue, 29 Mar 2016 02:33:09 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-5cbff7000000769f-64-56f9e95e0049 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id E0.C5.30367.E59E9F65; Mon, 28 Mar 2016 22:33:02 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id u2T2X1e8003419; Mon, 28 Mar 2016 22:33:01 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u2T2WwBx031177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Mar 2016 22:33:00 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u2T2Wvt7011668; Mon, 28 Mar 2016 22:32:57 -0400 (EDT) Date: Mon, 28 Mar 2016 22:32:57 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Second call for 2016Q1 quarterly status report submissions Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCIsWRmVeSWpSXmKPExsUixCmqrRv38meYwZ8JPBa7rp1mt5jz5gOT xfbN/xgdmD1mfJrPEsAYxWWTkpqTWZZapG+XwJVxfsIR5oKnXBUnb09jaWD8w9HFyMkhIWAi sf/nDJYuRi4OIYE2JonXZ7eygySEBDYySvSc1YdIHGKSeP7vPxOE08Ao8WnOYyCHg4NFQFvi z51QkAY2ATWJ9SuuMUNMVZTYfGoSmC0iIC+xr+k92FBmIHvL6slsILawgLPErTvbwWxeAUeJ kz9+MIHYogI6Eqv3T2GBiAtKnJz5hAWiV0ti+fRtLBMY+WchSc1CklrAyLSKUTYlt0o3NzEz pzg1Wbc4OTEvL7VI10gvN7NELzWldBMjOPAkeXcw/rvrdYhRgINRiYc3YtHPMCHWxLLiytxD jJIcTEqivH1zgEJ8SfkplRmJxRnxRaU5qcWHGCU4mJVEeLteAOV4UxIrq1KL8mFS0hwsSuK8 MTePhgkJpCeWpGanphakFsFkZTg4lCR4U0AaBYtS01Mr0jJzShDSTBycIMN5gIYHgA0vLkjM Lc5Mh8ifYlSUEucteg6UEABJZJTmwfWCE8NuJtVXjOJArwjzVoC08wCTClz3K6DBTECDpay+ gQwuSURISTUwumxVKfluuW9L07uVmvfCVzyfoHpK67/4q9a7cxI/vz3mc6BetdZ1cbjzF/4M 8TmbeU/c9u/WMubtZ3rW9rLlyG7Lra9f6OwPWnc/0qT/lMvh4N/ZEzuyjEovC+TeVnog/Eun 9YxB6z7Oby/VbpztYt72IPurtee3MO/pHvMNTxSdYfZYceyDqBJLcUaioRZzUXEiAARVS0nn AgAA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2016 02:33:10 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2016, for work done in January through March -- less than two weeks away! Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at FreeBSD.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2016Q1 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2015-07-2015-09.html [5] http://www.freebsd.org/news/status/report-2015-10-2015-12.html From owner-freebsd-hackers@freebsd.org Tue Mar 29 06:30:02 2016 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 61D3EAE1C47 for ; Tue, 29 Mar 2016 06:30:02 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2E6FA1B2B for ; Tue, 29 Mar 2016 06:30:01 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from [192.168.1.155] (unknown [86.125.33.32]) by mail.rdsor.ro (Postfix) with ESMTP id 9F554DB1F for ; Tue, 29 Mar 2016 09:29:54 +0300 (EEST) From: Dan Partelly Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: DTRACE statically compiled in kernel Message-Id: <0537D9E4-C1C0-407E-BA30-DC4B7B3235EB@rdsor.ro> Date: Tue, 29 Mar 2016 09:29:54 +0300 To: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2016 06:30:02 -0000 Heya, Is there any supported way to build dtrace statically linked in kernel = and use it to probe=20 early boot APIs ? Dan From owner-freebsd-hackers@freebsd.org Tue Mar 29 12:45:08 2016 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 D638CAE082C for ; Tue, 29 Mar 2016 12:45:08 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: from mail.embedded-brains.de (mail.embedded-brains.de [82.135.62.35]) (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 879081D10 for ; Tue, 29 Mar 2016 12:45:07 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id F038C2A1835; Tue, 29 Mar 2016 14:45:00 +0200 (CEST) Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id PHfRDGqy6B_E; Tue, 29 Mar 2016 14:44:58 +0200 (CEST) Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 851B52A1858; Tue, 29 Mar 2016 14:44:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at zimbra.eb.localhost Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TDKvmJT_p-Dh; Tue, 29 Mar 2016 14:44:58 +0200 (CEST) Received: from [192.168.96.129] (unknown [192.168.96.129]) by mail.embedded-brains.de (Postfix) with ESMTPSA id 613EB2A1835; Tue, 29 Mar 2016 14:44:58 +0200 (CEST) Subject: Re: Code Formatter for STYLE(9)? To: Hans Petter Selasky , freebsd-hackers@freebsd.org References: <56F3EBB1.1060603@embedded-brains.de> <56F44D23.6090405@selasky.org> From: Sebastian Huber Message-ID: <56FA78C8.9000105@embedded-brains.de> Date: Tue, 29 Mar 2016 14:44:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56F44D23.6090405@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2016 12:45:08 -0000 On 24/03/16 21:25, Hans Petter Selasky wrote: > On 03/24/16 14:29, Sebastian Huber wrote: >> Hello, >> >> is there a ready to use C code formatter available that honours >> STYLE(9)? I tried clang-format, but it knows only LLVM, Google, >> Chromium, Mozilla by default. The GNU indent --original seems to produ= ce >> nothing usable. Same problem with astyle --style=3Dbsd. >> > > Hi, > > Maybe you want to contribute to: > > https://svnweb.freebsd.org/base/head/tools/tools/indent_wrapper > > It also supports diffs.=20 I tried to use the FreeBSD indent with your configuration on a pretty=20 badly formatted file, but it didn't work well. My hope was that someone=20 has a configuration for the clang-format. The uncrustify program seems to be quite capable, but would require=20 additional support to cope with STYLE(9). At least using https://github.com/freebsd/pkg/blob/master/freebsd.cfg didn't yield a good result. --=20 Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.huber@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine gesch=E4ftliche Mitteilung im Sinne des EHUG. From owner-freebsd-hackers@freebsd.org Wed Mar 30 09:31:20 2016 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 86AC8AE0F9E for ; Wed, 30 Mar 2016 09:31:20 +0000 (UTC) (envelope-from mail@eax.me) Received: from relay16.nicmail.ru (relay16.nicmail.ru [195.208.5.134]) (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 3E1301182 for ; Wed, 30 Mar 2016 09:31:19 +0000 (UTC) (envelope-from mail@eax.me) Received: from [109.70.25.215] (port=48796 helo=fujitsu) by f17.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1alCT5-000Kkr-48 for freebsd-hackers@freebsd.org; Wed, 30 Mar 2016 12:31:15 +0300 Received: from [93.174.131.138] (account mail@eax.me HELO fujitsu) by proxy02.mail.nic.ru (Exim 5.55) with id 1alCT5-000766-4Z for freebsd-hackers@freebsd.org; Wed, 30 Mar 2016 12:31:15 +0300 Date: Wed, 30 Mar 2016 12:30:48 +0300 From: Aleksander Alekseev To: freebsd-hackers@freebsd.org Subject: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160330123048.3361a9e4@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 09:31:20 -0000 Hello Today I found a way to crash CURRENT kernel. I'm a full-time *nix C developer but I never did kernel development before. I read "FreeBSD Device Drivers" and "FreeBSD Developer's Handbook" recently. Also I learned how to use DDB and KGDB. Discovered problem doesn't seem to be too complicated and I hope you could guide me a little bit through fixing it. I'm using TP-LINK TL-WN725N USB Wi-Fi adapter. When I do: sudo ifconfig wlan0 down sudo ifconfig wlan0 up ... and then pull Wi-Fi adapter out of USB kernel crashes like this: http://pastebin.com/raw/LkuE6Y7s It reproduces in 100% of cases. Here is a code that causes a problem (ieee80211_scan_sw.c:765): ``` static void scan_end(struct ieee80211_scan_state *ss, int scandone) { struct scan_state *ss_priv = SCAN_PRIVATE(ss); struct ieee80211vap *vap = ss->ss_vap; struct ieee80211com *ic = ss->ss_ic; IEEE80211_LOCK_ASSERT(ic); IEEE80211_DPRINTF(vap, IEEE80211_MSG_SCAN, "%s: out\n", __func__); if (ss_priv->ss_iflags & ISCAN_ABORT) { scan_done(ss, scandone); return; } IEEE80211_UNLOCK(ic); ic->ic_scan_end(ic); /* notify driver */ IEEE80211_LOCK(ic); /* <--- HERE */ ``` So as I understand some code acquired a mutex and didn't release it. And naturally it has something to do with USB. Now how can I figure out what code acquired this lock? Best approach I can think of currently is to find all places where this lock is accessed and add a debug logging. But perhaps there is a better way? -- Best regards, Aleksander Alekseev http://eax.me/ From owner-freebsd-hackers@freebsd.org Wed Mar 30 09:44:42 2016 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 C58C6AE17CE for ; Wed, 30 Mar 2016 09:44:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 9142A1E0C; Wed, 30 Mar 2016 09:44:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 888FE1FE023; Wed, 30 Mar 2016 11:44:40 +0200 (CEST) Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT To: Aleksander Alekseev , freebsd-hackers@freebsd.org, Adrian Chadd References: <20160330123048.3361a9e4@fujitsu> From: Hans Petter Selasky Message-ID: <56FBA0C0.8030809@selasky.org> Date: Wed, 30 Mar 2016 11:47:44 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160330123048.3361a9e4@fujitsu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 09:44:42 -0000 On 03/30/16 11:30, Aleksander Alekseev wrote: > So as I understand some code acquired a mutex and didn't release it. > And naturally it has something to do with USB. Now how can I figure out > what code acquired this lock? Best approach I can think of currently is > to find all places where this lock is accessed and add a debug logging. > But perhaps there is a better way? Looks like the USB driver or WLAN stack needs to drain this taskqueue before detaching. Maybe Adrian knows? --HPS From owner-freebsd-hackers@freebsd.org Wed Mar 30 10:42:00 2016 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 BE3A9AE2DB8 for ; Wed, 30 Mar 2016 10:42:00 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 878FB1DE7 for ; Wed, 30 Mar 2016 10:42:00 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 2329E15340A for ; Wed, 30 Mar 2016 12:41:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XI2OT7UakbHN; Wed, 30 Mar 2016 12:41:44 +0200 (CEST) Received: from [192.168.101.107] (vpn.ecoracks.nl [31.223.170.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 8E527153430 for ; Wed, 30 Mar 2016 12:41:44 +0200 (CEST) To: freebsd-hackers@freebsd.org From: Willem Jan Withagen Subject: Getting a thread name Message-ID: <56FBAD69.908@digiware.nl> Date: Wed, 30 Mar 2016 12:41:45 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 10:42:00 -0000 Hi, pthread_np has a call: pthread_set_name(tid, str). Now I'm looking for a way of retrieving that name. But there is no: pthread_get_name() in the same set. But I see top actually displaying the threadnames. So can somebody give me a hint where to look? Other than going thru top... Thanx, --WjW From owner-freebsd-hackers@freebsd.org Wed Mar 30 11:30:42 2016 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 0A06BAE3792 for ; Wed, 30 Mar 2016 11:30:42 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8540D1383 for ; Wed, 30 Mar 2016 11:30:41 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id k79so33571397lfb.2 for ; Wed, 30 Mar 2016 04:30:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:references:date:mime-version:content-transfer-encoding :from:message-id:in-reply-to:user-agent; bh=iXKAuCVaUQuyBZH3LVzq46VYj7s0zS/xYiaZ/7dQESk=; b=f7L78B4SfNhDSOZpMhBquvbfjwAwHmmOQfs12PfqreRHxUK69+CQp2L5zuzDydxFmy W0n8xc9CCngFbgiVGXpS2d0xqJAYsdKdamjI9Twn6L+5BHfVM45NhAsgNqd4UOTXebH7 GxkOWwmj8BEv8KoSNJVhd7I6bXvC2H9Cs+a5WAYaE5DekQyGkUkfxI+MNFs+hna/+qeS 8pL7PQPjSTVyMWPq9wHHVg7hXG3FT559CMyB0LH9pnQeLNcFvxvwlf9tR6dTteyqcObd otBzUrR6P2MazY3sRcdxBTWJHWIVZL8qY5ednmH156bwOj5YMZfMyL+bE2j6B6cOVb60 pTVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=iXKAuCVaUQuyBZH3LVzq46VYj7s0zS/xYiaZ/7dQESk=; b=O4WZt7J7KbUzJwr5WDbZfElV1/awq6IroKGTxr0XXcrtlpMGQBZsjOkmKfHeysEc0T WWjYvmBqCDPbXgQCwlt9gP1llSpWmIAEysOcNiAd+Z+ow7vrsc/D5SbQda5+MbQbS5A7 QpRtf5g4gZZdWOvgfUYI/8z6ltWza26LAnYlsoOYiZ5OkihFR9uW3aOzs/hkIl8owiv8 CR1P/zjJCxTpR50uc5uNEwRBLAuu9p2SvmhBFxE+yCd3K537HxihvL2aUCG1mVDSEjMw gcSu1VucYv85THT+rPSBpjwJnJZueH4MM2Cmoxo2fo3bXCATGKPBJft0sAt50kSjEjP6 HTJg== X-Gm-Message-State: AD7BkJIAqRTR5wabFPt7oNg/hEXVtSxjkkfMbmpkGgck7/OXkV93+Wob4/czyTGOj1OpyQ== X-Received: by 10.25.15.75 with SMTP id e72mr3580989lfi.148.1459337439870; Wed, 30 Mar 2016 04:30:39 -0700 (PDT) Received: from localhost ([77.91.171.160]) by smtp.gmail.com with ESMTPSA id i2sm490034lfd.43.2016.03.30.04.30.38 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 30 Mar 2016 04:30:39 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-hackers@freebsd.org, "Aleksander Alekseev" Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT References: <20160330123048.3361a9e4@fujitsu> Date: Wed, 30 Mar 2016 14:30:41 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <20160330123048.3361a9e4@fujitsu> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 11:30:42 -0000 Wed, 30 Mar 2016 12:30:48 +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 Aleksander Alekseev = : > and then pull Wi-Fi adapter out of USB Here (it's not the only driver which does detach incorrectly). > Hello > > Today I found a way to crash CURRENT kernel. I'm a full-time *nix C > developer but I never did kernel development before. I read "FreeBSD > Device Drivers" and "FreeBSD Developer's Handbook" recently. Also I > learned how to use DDB and KGDB. Discovered problem doesn't seem to be= > too complicated and I hope you could guide me a little bit through > fixing it. > > I'm using TP-LINK TL-WN725N USB Wi-Fi adapter. When I do: > > sudo ifconfig wlan0 down > sudo ifconfig wlan0 up > > ... and then pull Wi-Fi adapter out of USB kernel crashes like this: > > http://pastebin.com/raw/LkuE6Y7s > > It reproduces in 100% of cases. > > Here is a code that causes a problem (ieee80211_scan_sw.c:765): > > ``` > static void > scan_end(struct ieee80211_scan_state *ss, int scandone) > { > struct scan_state *ss_priv =3D SCAN_PRIVATE(ss); > struct ieee80211vap *vap =3D ss->ss_vap; > struct ieee80211com *ic =3D ss->ss_ic; > > IEEE80211_LOCK_ASSERT(ic); > > IEEE80211_DPRINTF(vap, IEEE80211_MSG_SCAN, "%s: out\n", > __func__); > > if (ss_priv->ss_iflags & ISCAN_ABORT) { > scan_done(ss, scandone); > return; > } > > IEEE80211_UNLOCK(ic); > ic->ic_scan_end(ic); /* notify driver */ > IEEE80211_LOCK(ic); /* <--- HERE */ > ``` > > So as I understand some code acquired a mutex and didn't release it. > And naturally it has something to do with USB. Now how can I figure ou= t > what code acquired this lock? Best approach I can think of currently i= s > to find all places where this lock is accessed and add a debug logging= . > But perhaps there is a better way? From owner-freebsd-hackers@freebsd.org Wed Mar 30 11:35:43 2016 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 1E57BAE39B3 for ; Wed, 30 Mar 2016 11:35:43 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c: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 AE7F518F4 for ; Wed, 30 Mar 2016 11:35:42 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id 20so66528623wmh.1 for ; Wed, 30 Mar 2016 04:35:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=/CeTBM5XI0FTXseYPkwf9nTPGF/H/Hof/DyEliGKYIE=; b=qvEdRTpvvv74JpRvRg1r6gp4WabXK8/CtiQhlhqN4EhI9hxgNHS8FRAfuHduWpzKAY 8aixwL+iaVW4176cAakx9DWWQ71m7y0kus1qqxb2EtIXcR4ruL/Y2AMJLMRDRRK252yy IqrpsQu3ylfgRtuWBeVSeBq0kZLo334gOcySATpHI0MHcgUVqY9eR8XsgnrdSDY5HuKf Gw6SdNkQ2gvUUrirx2rfqkkBV1saltC1w60US9uL3crrdiJB9RGo73TSvEaNMCH9kfk9 Rx9JzKZ+hpFX1gDVWJFgaiBvKKnX1QC99wHuH9VjcOTt+n0qwXOLpNocfmT8dLXG+Ldb KV6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=/CeTBM5XI0FTXseYPkwf9nTPGF/H/Hof/DyEliGKYIE=; b=SoNIEbIJPqkiETX9ydDPaW/58hrqn1jS+OqnXo1Bact5bAT815xMavrDhHBLmNzyXN aIVIYb6A+kSc/COZh6VSuOpvZO5qzRa6CPNvwSP+Jr/zp2nfg1aI96kQ7Ivy5DE0jJeL Zq70hjg7qMRqkAhP4DJaZdp3Pyysm4DJq7o6Q/U9lG0cg7/dko7qRZWaWlpJeRkXvtj/ Ga8gwxa4c8xzavSyunrlH9HyJvvo8fzSmvDS4Y63TdHliJML6dZFPTcKIByciiGrhS4J rnEjg5UKr0Xg6c5UBXDXWiOlPZbMafTH1X60Mhl3AuXnv6zvZjrbdUm6JhxlDL8S5qZ6 iOkg== X-Gm-Message-State: AD7BkJJHMFkZvRFDWGldc9HIhhgpdxMoi2EKfsjWpj08vlJf+F47HwTQDGcTXopk/mRsAbog3b2Kpj2jgP4SoQ== MIME-Version: 1.0 X-Received: by 10.194.58.169 with SMTP id s9mr9017851wjq.52.1459337741311; Wed, 30 Mar 2016 04:35:41 -0700 (PDT) Received: by 10.194.57.133 with HTTP; Wed, 30 Mar 2016 04:35:41 -0700 (PDT) In-Reply-To: <56FBAD69.908@digiware.nl> References: <56FBAD69.908@digiware.nl> Date: Wed, 30 Mar 2016 14:35:41 +0300 Message-ID: Subject: Re: Getting a thread name From: Sergey Kandaurov To: Willem Jan Withagen Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 11:35:43 -0000 On 30 March 2016 at 13:41, Willem Jan Withagen wrote: > Hi, > > pthread_np has a call: pthread_set_name(tid, str). > > Now I'm looking for a way of retrieving that name. But there is no: > pthread_get_name() in the same set. > > But I see top actually displaying the threadnames. So can somebody give > me a hint where to look? Other than going thru top... > It's extracted either over kvm(3) or sysctl(3) interface depending on your needs. Search for kvm_getprocs() and KERN_PROC respectively. You can also use libprocstat(3) that is a wrapper. -- wbr, pluknet From owner-freebsd-hackers@freebsd.org Wed Mar 30 11:42:39 2016 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 C8159AE3BF0 for ; Wed, 30 Mar 2016 11:42:39 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 936E21DB5 for ; Wed, 30 Mar 2016 11:42:39 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2DA9A1FE023; Wed, 30 Mar 2016 13:42:35 +0200 (CEST) Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT To: Andriy Voskoboinyk , freebsd-hackers@freebsd.org, Aleksander Alekseev References: <20160330123048.3361a9e4@fujitsu> From: Hans Petter Selasky Message-ID: <56FBBC62.6040905@selasky.org> Date: Wed, 30 Mar 2016 13:45:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 11:42:39 -0000 On 03/30/16 13:30, Andriy Voskoboinyk wrote: > Wed, 30 Mar 2016 12:30:48 +0300 було написано Aleksander Alekseev > : > >> and then pull Wi-Fi adapter out of USB > > Here (it's not the only driver which does detach incorrectly). Is this something which you can fix? --HPS From owner-freebsd-hackers@freebsd.org Wed Mar 30 11:44:19 2016 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 E5297AE3C66 for ; Wed, 30 Mar 2016 11:44:19 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (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 AD5FA1EE3 for ; Wed, 30 Mar 2016 11:44:19 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id A21C515340D; Wed, 30 Mar 2016 13:44:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlbwncJVqwof; Wed, 30 Mar 2016 13:44:00 +0200 (CEST) Received: from [192.168.101.107] (vpn.ecoracks.nl [31.223.170.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id EF9A0153416; Wed, 30 Mar 2016 13:43:59 +0200 (CEST) Subject: Re: Getting a thread name To: Sergey Kandaurov References: <56FBAD69.908@digiware.nl> Cc: FreeBSD Hackers From: Willem Jan Withagen Message-ID: <56FBBC00.6000901@digiware.nl> Date: Wed, 30 Mar 2016 13:44:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 11:44:20 -0000 On 30-3-2016 13:35, Sergey Kandaurov wrote: > On 30 March 2016 at 13:41, Willem Jan Withagen wrote: >> Hi, >> >> pthread_np has a call: pthread_set_name(tid, str). >> >> Now I'm looking for a way of retrieving that name. But there is no: >> pthread_get_name() in the same set. >> >> But I see top actually displaying the threadnames. So can somebody give >> me a hint where to look? Other than going thru top... >> > > It's extracted either over kvm(3) or sysctl(3) interface depending on > your needs. Search for kvm_getprocs() and KERN_PROC respectively. > You can also use libprocstat(3) that is a wrapper. First 2 sounds rather convoluted.... I have a thread ID and want the string with the threadname back, as set by pthread_set_name(). Fortunately is the place where I need it atm. is in process wrapup. So performance is not a real issue. I'll check your hints, thanx, --WjW From owner-freebsd-hackers@freebsd.org Wed Mar 30 15:00:45 2016 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 B5246AE295D for ; Wed, 30 Mar 2016 15:00:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 75A6C1442 for ; Wed, 30 Mar 2016 15:00:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x236.google.com with SMTP id a129so68878098ioe.0 for ; Wed, 30 Mar 2016 08:00:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=e8c8hLsBrm3j106Rw48FcZES7iqL8kfLUR1VJwWu0HI=; b=gEWn4j+YfSpYMcMuidwH77B8Qz3ctdGjCBig3+qawqDjEo7/pfZ+ktCKeG0e4rm/LC gxKZTyDRxxOqU6PP6JBaU4bwXp78rlflDlOaTCp9u+PF9sf4/ihw+nxWGxaRDWpwwDLN Wp1VvW8R/9gsNqlGtFncikBM/XR/szYRrCF0Dp2PdSYr1T3OQ2Is8uqi4nDppaVU3bET MRnv122RdwFqZ3F2d1R4Qag0UoHa8mQ9Pd+jV4plCzGWaz08zki2eL61FqZ0TKUhITqN nu4tDrV3jWId6oG2uc/dZsnsQOnkVi8qHX9vPq7uD3Bqts9SFyUl6neLKzy//I0YjN2J 703w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=e8c8hLsBrm3j106Rw48FcZES7iqL8kfLUR1VJwWu0HI=; b=i0P9i7Dpp5ZN9n6XAlwUhy7pa5J8Rvd22Y9HsVB1KsUCjQokhluz8zMwzJe8NPQflr SII7TuiRsWAbl87qBRNhoNvglldDv1jgZ/iQawAkLeCgB5eh63MTqBMR9hHgXpkZFy2Q 8boSpo5X6cWWnskOAc0qHWtXkBJYOsrPXkx5lGpNdWvn8n4L9xinx5MtwGTXpMuYWrwJ lLPzvsaoER9ErKU13iv4a37lnyXIKbfJ4W9ZvT+uEk0WAjCBPqv9fzRml+k4ZHFU7jWn Obcb76wQYmqg314/qei/orwijOZfyrtb7NkDcGiSxkbqg6ypns8c2ZbxGyDhmIPSiAOT fa8Q== X-Gm-Message-State: AD7BkJK1cnb0N4o8z7ZoTICbc4gNnGOKHL4dTiCe/9FuYNqgOQLIqbvqLBUSAbrTQ3LCsh3Zq8703mXsvnICTQ== MIME-Version: 1.0 X-Received: by 10.107.11.162 with SMTP id 34mr9611122iol.165.1459350043417; Wed, 30 Mar 2016 08:00:43 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Wed, 30 Mar 2016 08:00:43 -0700 (PDT) In-Reply-To: <56FBBC62.6040905@selasky.org> References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> Date: Wed, 30 Mar 2016 08:00:43 -0700 Message-ID: Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT From: Adrian Chadd To: Hans Petter Selasky Cc: Andriy Voskoboinyk , "freebsd-hackers@freebsd.org" , Aleksander Alekseev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 30 Mar 2016 16:41:58 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 15:00:45 -0000 We really need some kind of device refcounting for things that be hotplugged (ie, most things these days) so we don't end up freeing driver state before all the driver / stack entry points are done. For net80211 drivers, they need to (a) not finish detach until all entry points are done, and (b) this includes ioctls and net80211 entry points, as net80211 may be doing something with the ic (eg an ioctl, etc) that hasn't yet finished. So yeah, it's not /just/ draining taskqueues, it's actually "we need an actual device lifecycle management thing". -adrian On 30 March 2016 at 04:45, Hans Petter Selasky wrote: > On 03/30/16 13:30, Andriy Voskoboinyk wrote: >> >> Wed, 30 Mar 2016 12:30:48 +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 Aleksander Alekseev >> : >> >>> and then pull Wi-Fi adapter out of USB >> >> >> Here (it's not the only driver which does detach incorrectly). > > > Is this something which you can fix? > > --HPS > > _______________________________________________ > 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 Mar 30 21:03:28 2016 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 7C518AE3A46 for ; Wed, 30 Mar 2016 21:03:28 +0000 (UTC) (envelope-from vbatts@gmail.com) Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::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 440B3176C for ; Wed, 30 Mar 2016 21:03:28 +0000 (UTC) (envelope-from vbatts@gmail.com) Received: by mail-ob0-x235.google.com with SMTP id fp4so8468762obb.2 for ; Wed, 30 Mar 2016 14:03:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=b3iGBa4+WgKUFdJpat3W0crCK2Za/Y8sJDcvvFd8HZE=; b=kJ5triuuaUZkgPC4qe1bqiv0DV8gUHDrmfCGngzHv1pMh3zu4VORH6yalZ+OBqZFFX r1e6KmLn8zbCyBg8h2zFdFXv1lThcnYQbQX1WJvCMQgOdfZQquBu7vL4WlLiVWGKQIVc +/m4bbGuZjwWPIgSBUNK3UtfSYV+VXOlNDKwwcOIrfCymW/s54dGQjYEwB25Kk08zccC Z/ePtakD2AHxEtVLaf/2JqrWhJCTx3MaHOHU1SuVd57QtplwTEr/kcBjl3Z6K1LZM9ip Mjf2AIPIgTpHi7mTdMDJTF7OPLMneQfK3tiEqScF/op3CIm5H9Swxpxe6iv4Ym9ZOsGK HxEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=b3iGBa4+WgKUFdJpat3W0crCK2Za/Y8sJDcvvFd8HZE=; b=LEaFp4a4AoKMcQUJQClg8vTjCbTAeAqItp5xy22k/ttnfCWNxmydIoywpzO9zEos3C a3ZP8u8ULZzaZYeQpSzqXjxmVVj46yMpoYz61U6PM7d1pEW/UdnZH8gO27hgEjFRfOw8 itZQb10EZlWarzERQ5iIC5uVxO/pk03xeY007A+O7Vp45McI/LxIeM1JVHq4MEuBj+Gp KKF+cO+DR+rPkVdyVMezPIQ2aooUBoV1iV/AjsNOgDVEF2QU4QrpIO8CbeW3u2fdAqAB 1PWJ26wnUnboIFOFNmgdzu1X7oxFo3rkMxd8HNONflhE22pUo6Srw3GXTxL+5EO7NG7e +TqQ== X-Gm-Message-State: AD7BkJLgxICEBv0BQ59D0uySb3rGb5Rpv2gl69dLGAoY8kNb0MEvJPx3R7hE4JJoPWdDz2RN6PjufSxTkUbmcg== MIME-Version: 1.0 X-Received: by 10.60.176.100 with SMTP id ch4mr6381826oec.7.1459371807553; Wed, 30 Mar 2016 14:03:27 -0700 (PDT) Sender: vbatts@gmail.com Received: by 10.182.109.228 with HTTP; Wed, 30 Mar 2016 14:03:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Mar 2016 17:03:27 -0400 X-Google-Sender-Auth: i8xrGD8rlB6FUQJbvDZOzkDw7-I Message-ID: Subject: Re: [RFE] mtree support for extattr? From: Vincent Batts To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 21:03:28 -0000 On Wed, Mar 9, 2016 at 10:17 AM, Vincent Batts wrote: > Hello all, > > This is a first post from me. The `mtree` utility (./contrib/mtree/) > and the specs that it produces and validates has found it's way into > projects that I am involved in. While the projects are initially very > Linux focused, they are not limited to such. There is an mtree-port > that has been started for Linux, but is not widely packaged yet. Also, > libarchive has support for parsing and creating mtree specs. > > On most Linux filesystems, extend attributes are used commonly for > storing ACLs, capabilities, etc. These attributes are something that > most definitely would be interesting keywords to include in the spec > of a directory hierarchy. > From my researching, it seems that extattr support for mtree on > freebsd is not present, while the sys/extattr.h and UFS could support > it. > > It seems this is a valuable feature to add and would be widely useful. > Some of the mechanics would be interesting to handle the collation of > the extattr data into the keywords for files in the mtree spec. As the > key/values are namespaced, perhaps the mtree keyword would use the > namespace.key and prefix it with 'extattr.' or 'xattr' or similar. > Such that the entry in the mtree spec looks like > ``` > my.file \ > mode=0644 size=24542 time=1455996582.000000000 \ > extattr.system.mykey=myvalue \ > > sha512digest=f758e6d04b527cc024aa70ffaaa75b4899429498d246f41a057753dc51b7d49e0f6b512c1f1920435585067209863c529b2038101ce0576138c7eee7ca359b7c > ``` > Some issues that I have with this is the information leak of the > values of the extended attributes. Also, on Linux xattrs are expected > to be ascii strings, it is not uncommon to find binary content in the > value. > For these two cases, it seems nicer to just include a checksum of the > value of each extended attribute. This then requires an election to > which hash to use for the checksum digest. > > I look forward to your response and next steps! Hello all, In update, I have recently opened the project "go-mtree" ( https://github.com/vbatts/go-mtree ). It is a go programming language library for interacting with the mtree specification. It has a simple cli, which is largely for testing and not intended to replace the `mtree` executable. I did include the xattr support as I mentioned. It's design ought to be consistent with how FreeBSD extattr work. It would be great to here from anyone on extended attribute support making its way into the FreeBSD mtree and specification. Thoughts? vb From owner-freebsd-hackers@freebsd.org Thu Mar 31 17:43:07 2016 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 B5437AE3891; Thu, 31 Mar 2016 17:43:07 +0000 (UTC) (envelope-from mail@eax.me) Received: from relay12.nicmail.ru (relay12.nicmail.ru [195.208.5.7]) (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 69B0F106F; Thu, 31 Mar 2016 17:43:06 +0000 (UTC) (envelope-from mail@eax.me) Received: from [109.70.25.214] (port=50579 helo=portege) by f06.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1algch-000Ln7-0H; Thu, 31 Mar 2016 20:43:11 +0300 Received: from [188.123.231.37] (account mail@eax.me HELO portege) by proxy01.mail.nic.ru (Exim 5.55) with id 1algcT-0007Et-8Q; Thu, 31 Mar 2016 20:42:57 +0300 Date: Thu, 31 Mar 2016 20:42:56 +0300 From: Aleksander Alekseev To: Adrian Chadd Cc: Hans Petter Selasky , "freebsd-hackers@freebsd.org" , Andriy Voskoboinyk , freebsd-dtrace@freebsd.org Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160331204256.5cb1fdaf@portege> In-Reply-To: References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 17:43:07 -0000 > So as I understand some code acquired a mutex and didn't release it. > And naturally it has something to do with USB. Now how can I figure > out what code acquired this lock? Best approach I can think of > currently is to find all places where this lock is accessed and add a > debug logging. But perhaps there is a better way? By any chance is it possible to trace mtx_lock / mtx_unlock calls using DTrace? I see number of probes in `dtrace -l` which look like something I need. Unfortunately they are named like knlist_mtx_lock or do_lock_umutex so I can't figure out whether these are probes I looking for or not. cc: freebsd-dtrace@ -- Best regards, Aleksander Alekseev http://eax.me/ From owner-freebsd-hackers@freebsd.org Thu Mar 31 18:00:30 2016 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 26FE5AE3FF6; Thu, 31 Mar 2016 18:00:30 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (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 E9FCD18AC; Thu, 31 Mar 2016 18:00:29 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x229.google.com with SMTP id fe3so71266638pab.1; Thu, 31 Mar 2016 11:00:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=8FZTPvShhj+3LK7LHN9fNMQK6zadYVqSOepvY9OlhkE=; b=0Rvk+i5fTf4txXNnjnlLNg+0edxdsk7YiAhFwnpH8zZYY3omCqFi/B+5CLSK5awtOS buRH1zawhPg/IaH8JMC8XSaefxp7BNkWyIDmUNthT3HuLynAtRWsJ+U/0sXSemArAdc1 63ZBIo0CVwxI53r9MiN8YIr40IbOHmJO2BCBVWx1V5eZ3MiySCaMgdzq45wVV+5yM7zC wbcZLFHesj4b2fpqtM8Xz4Mevww2pcHHbowan9yynXZv5ed/MRi1vnPH6qihdCqKOZ/L 1QAkpRHY0H0qii2Y7lHtYQZbgznQ3qFO2vuGPRKw4JkipBpiU+CWPq+YRip44kxIeW8G khmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=8FZTPvShhj+3LK7LHN9fNMQK6zadYVqSOepvY9OlhkE=; b=Wd2qO8hiuoAZbD5YrCT+39/Dwhm+yTxnw0n1yw+oTaKpsnJ9JOzQMXF8gyljwhgi8c T9rU2Hf0UK1UJUiCkqdb2IaVoWjFeg8/MyLYrEna+XcCJ1cXKXi9U12QGU04FR5o2qq/ 5ZRZ84Gwe8+cdYe1utXjTNah3y/kTvbEaWkmBWbZL2EjWFAwggtbesjk5690/oZShVC7 5T37UI6PBd4+j8/VL2G69O6MBRrXey/76DgyHygj8HBohhusNqyXNKdjDvXb42mO1QIG GmnkJe+tVPdWuHSoSIlnTpnUeMFBd/SF7IOmp//Zka3bvdzOcdRCFEKpdwIpSh3eC8is TOig== X-Gm-Message-State: AD7BkJJ/LS4fY+t/pfEJ1Svk5LSE3XCB1wYzViTqNG6TxaH3ps+I9vB9Noff+FEPcKwAUQ== X-Received: by 10.67.30.163 with SMTP id kf3mr24023412pad.45.1459447229402; Thu, 31 Mar 2016 11:00:29 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-67-182-131-225.hsd1.wa.comcast.net. [67.182.131.225]) by smtp.gmail.com with ESMTPSA id e12sm14976613pat.19.2016.03.31.11.00.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Mar 2016 11:00:28 -0700 (PDT) Sender: Mark Johnston Date: Thu, 31 Mar 2016 11:03:33 -0700 From: Mark Johnston To: Aleksander Alekseev Cc: Adrian Chadd , Hans Petter Selasky , "freebsd-hackers@freebsd.org" , Andriy Voskoboinyk , freebsd-dtrace@freebsd.org Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> <20160331204256.5cb1fdaf@portege> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160331204256.5cb1fdaf@portege> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 18:00:30 -0000 On Thu, Mar 31, 2016 at 08:42:56PM +0300, Aleksander Alekseev wrote: > > So as I understand some code acquired a mutex and didn't release it. > > And naturally it has something to do with USB. Now how can I figure > > out what code acquired this lock? Best approach I can think of > > currently is to find all places where this lock is accessed and add a > > debug logging. But perhaps there is a better way? > > By any chance is it possible to trace mtx_lock / mtx_unlock calls using > DTrace? I see number of probes in `dtrace -l` which look like > something I need. Unfortunately they are named like knlist_mtx_lock or > do_lock_umutex so I can't figure out whether these are probes I looking > for or not. Yes. You can use the lockstat provider to trace lock events: "dtrace -l -P lockstat". Predicates can be used to isolate events related to a specific lock. For example: # dtrace -n 'lockstat:::adaptive-acquire /args[0]->lock_object.lo_name == "so_snd"/{stack();}' will print a stack every time a socket send buffer lock is acquired. In general, the lock name is specified as an initialization parameter. In your case it'll be "urtwn0_com_lock". lockstat(1) is a command-line program that's good at aggregating data collected from lockstat probes; for the type of debugging you're doing it's probably not very useful. Note that DTrace probably isn't very helpful here if the panic occurs immediately after the event you're interested in occurs, since dtrace(1) won't have time to retrieve the trace record and print it. From owner-freebsd-hackers@freebsd.org Thu Mar 31 21:23:49 2016 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 F29ADAE38D0; Thu, 31 Mar 2016 21:23:48 +0000 (UTC) (envelope-from mail@eax.me) Received: from relay15.nicmail.ru (relay15.nicmail.ru [195.208.5.161]) (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 A6EC61873; Thu, 31 Mar 2016 21:23:47 +0000 (UTC) (envelope-from mail@eax.me) Received: from [109.70.25.187] (port=48124 helo=portege) by f19.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1alk41-000AjB-CT; Fri, 01 Apr 2016 00:23:37 +0300 Received: from [188.123.231.37] (account mail@eax.me HELO portege) by proxy08.mail.nic.ru (Exim 5.55) with id 1alk41-0007vx-QO; Fri, 01 Apr 2016 00:23:37 +0300 Date: Fri, 1 Apr 2016 00:23:37 +0300 From: Aleksander Alekseev To: Mark Johnston Cc: Adrian Chadd , Hans Petter Selasky , Andriy Voskoboinyk , freebsd-dtrace@freebsd.org, "freebsd-hackers@freebsd.org" Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160401002337.36700d9b@portege> In-Reply-To: <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> <20160331204256.5cb1fdaf@portege> <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 21:23:49 -0000 > > By any chance is it possible to trace mtx_lock / mtx_unlock calls > > using DTrace? I see number of probes in `dtrace -l` which look like > > something I need. Unfortunately they are named like knlist_mtx_lock > > or do_lock_umutex so I can't figure out whether these are probes I > > looking for or not. > > Yes. You can use the lockstat provider to trace lock events: > "dtrace -l -P lockstat". Predicates can be used to isolate events > related to a specific lock. For example: > > # dtrace -n > 'lockstat:::adaptive-acquire /args[0]->lock_object.lo_name == > "so_snd"/{stack();}' > > will print a stack every time a socket send buffer lock is acquired. > In general, the lock name is specified as an initialization parameter. > In your case it'll be "urtwn0_com_lock". > > lockstat(1) is a command-line program that's good at aggregating data > collected from lockstat probes; for the type of debugging you're doing > it's probably not very useful. > > Note that DTrace probably isn't very helpful here if the panic occurs > immediately after the event you're interested in occurs, since > dtrace(1) won't have time to retrieve the trace record and print it. Thanks, Mark. Here is a funny thing. I thought that by writing debug.witness.watch=0 to /etc/sysctl.conf and rebooting I will give DTrace some time to report who acquired a lock and didn't released it. But in this case kernel crashed differently (I checked twice): http://pastebin.com/raw/f08Fd70B And here is saved DTrace log for lock "urtwn0_com_lock": http://pastebin.com/raw/0X9zgeiY If I'm not wrong everything is OK. No missing mtx_unlock this time. Not sure what to do next so far. And it's pretty late here in UTC+3 already so I will think about this tomorrow. Any advices would be appreciated. -- Best regards, Aleksander Alekseev http://eax.me/ From owner-freebsd-hackers@freebsd.org Thu Mar 31 22:56:00 2016 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 0277CAE4CBB; Thu, 31 Mar 2016 22:56:00 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C55481D85; Thu, 31 Mar 2016 22:55:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x230.google.com with SMTP id td3so75467517pab.2; Thu, 31 Mar 2016 15:55:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=wF0ojhRAoZ5w6Cg97vdSCdVmt2jf573b43JF3MITYZE=; b=IUpiKC9cfS2pT2URcOU4xGneXxMGcgBvBhD2Ceaz66nkT0OjJnJth59MP5P+jKApiz DSr/GxjfmVOfI1IRzFgg8RqoIOZ7ldxWgBUTGWAbqqknsACpGWRNPFmIpAv/qK2EOKl1 WRNRiIIi96ca7YQe/FzvIJNWq3qK3ZQd+MIM5gNWcoZqIVFRexBnQo7O5vrPGYFtr4pa 9cLWaMDPALZUdcb+CTFds2sX9ypxJhBiHMQFtwj+SHpcD4mdmpm3lirruTqh/dlO+DWN uparZ6T9VkQg5l3fxL7IpG6ZlOXR3tHLyYZZ/XP40SuO4wkpAi8p9REu+z3mr0TLAnxm eSFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=wF0ojhRAoZ5w6Cg97vdSCdVmt2jf573b43JF3MITYZE=; b=H4uQBITO+uTc1iPiz664UKKY6+nCi7wRqLqhJfIsqMq28Jzg2XNrYGZbj5rFAECo0F Wa6Ghla36Y9XNFQog870nmezRd2eDcdbqBXuSJBsPKb3nbBB7BJhrezphYaDvjesnQno EIwyI4/hwXjUhIQ77dDGja34cjIs9FL/Dy+GghNpnDD1xDKELNUdPcQDun0/bSLvthcC tknO50pLMzmcZEPRdZH/Q/nLtrA3j6TMOP/7FfTc373sRCMgoRX+/q8KthhLPHXOogHd UHTiMUoDiGFSDn6wN56z0R91nw0UZc+/zi7FajSV1UchqHTSkIa04vuyePK0CCPBkscX SbCg== X-Gm-Message-State: AD7BkJLC7Wqo//Du/I++zDJWeYpza/nv4qamIwTwsoEqZov+Bz5cXChcrL6ye4SY0BHpCg== X-Received: by 10.66.254.168 with SMTP id aj8mr25866829pad.18.1459464959409; Thu, 31 Mar 2016 15:55:59 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-67-182-131-225.hsd1.wa.comcast.net. [67.182.131.225]) by smtp.gmail.com with ESMTPSA id d12sm15709164pfj.85.2016.03.31.15.55.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Mar 2016 15:55:58 -0700 (PDT) Sender: Mark Johnston Date: Thu, 31 Mar 2016 15:59:02 -0700 From: Mark Johnston To: Aleksander Alekseev Cc: Adrian Chadd , Hans Petter Selasky , Andriy Voskoboinyk , freebsd-dtrace@freebsd.org, "freebsd-hackers@freebsd.org" Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com> References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> <20160331204256.5cb1fdaf@portege> <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> <20160401002337.36700d9b@portege> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160401002337.36700d9b@portege> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 22:56:00 -0000 On Fri, Apr 01, 2016 at 12:23:37AM +0300, Aleksander Alekseev wrote: > > > By any chance is it possible to trace mtx_lock / mtx_unlock calls > > > using DTrace? I see number of probes in `dtrace -l` which look like > > > something I need. Unfortunately they are named like knlist_mtx_lock > > > or do_lock_umutex so I can't figure out whether these are probes I > > > looking for or not. > > > > Yes. You can use the lockstat provider to trace lock events: > > "dtrace -l -P lockstat". Predicates can be used to isolate events > > related to a specific lock. For example: > > > > # dtrace -n > > 'lockstat:::adaptive-acquire /args[0]->lock_object.lo_name == > > "so_snd"/{stack();}' > > > > will print a stack every time a socket send buffer lock is acquired. > > In general, the lock name is specified as an initialization parameter. > > In your case it'll be "urtwn0_com_lock". > > > > lockstat(1) is a command-line program that's good at aggregating data > > collected from lockstat probes; for the type of debugging you're doing > > it's probably not very useful. > > > > Note that DTrace probably isn't very helpful here if the panic occurs > > immediately after the event you're interested in occurs, since > > dtrace(1) won't have time to retrieve the trace record and print it. > > Thanks, Mark. > > Here is a funny thing. I thought that by writing debug.witness.watch=0 > to /etc/sysctl.conf and rebooting I will give DTrace some time to > report who acquired a lock and didn't released it. But in this case > kernel crashed differently (I checked twice): > > http://pastebin.com/raw/f08Fd70B > > And here is saved DTrace log for lock "urtwn0_com_lock": > > http://pastebin.com/raw/0X9zgeiY > > If I'm not wrong everything is OK. No missing mtx_unlock this time. Looking at your original post, the problem isn't related to a missing unlock. The attempt to lock the ieee80211com is triggering a fault, presumably because it was freed while the lock was dropped. So DTrace isn't going to help much here. From owner-freebsd-hackers@freebsd.org Fri Apr 1 02:38:40 2016 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 3AB27AE5A56 for ; Fri, 1 Apr 2016 02:38:40 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0F7C1222 for ; Fri, 1 Apr 2016 02:38:39 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-yw0-x22d.google.com with SMTP id g3so128813048ywa.3 for ; Thu, 31 Mar 2016 19:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=cFKMRXJuGXILG+pMXgjcdDO0PBy/Y/FVlm0rsePylfA=; b=LWfpfzO/cjvkPiQ01G6Gn8YPomRjLBu3sxqeQ1CWUIlM6Z64JRU5H5IdP5ZJS+vMxQ ibFh/jVVURw0sja+bQPFuHGZbzUwjVgzPL0BB31CgaKzwXhmq+tQnLZrDpytCJl997O6 QV2wegWeUZRMitYW3aR/n7PnHew3s+g/20JtqbHWHofDZ4RUzWhQlZlMBJrcF9M3iFW+ uY7u7Age4b9u5FBWOt5A7Vm/IQ0sdU5B643TbObpl8f3muNJ8uh4MQsAXPrIo/sQgXko tS7kYBuIH6Z+7UVr238q9PC8JZZj5lHxaCLmj3TrUqRQ5ZjGFFBtZ62O8b/7mecluqmf JBMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cFKMRXJuGXILG+pMXgjcdDO0PBy/Y/FVlm0rsePylfA=; b=jGr49BRonHnbv6GCoZ0JDCxxC9YhlaYttndytDGXEhY2tnf4zIsL/HoGbggIh4YA6X tWi49j4l4T6kgzQB5oSQCNXhswp1XOQiptQJKl3xFhJz3TJUsR4XvHux/GxiMx6LDN4v /cjaE+xWDFz4M9nngJV4NSTtUGi3LZwlCoDW/dO3NPl1r+0QzPYgcrV/utr/JzcO7Uhy ejNATBrVdo4j7HG9Cgk3hlywlmE94X5wA0jgEnjzhL+UVHbfrLHUcmHvD6p6c3/Pv7PK 0hYDJvLKKPhX3FmVtm8Rhqckqu87Ui8gYTurSSYNG2UDFc9zDWLOuSO09OOqDjEVdDBS eGKA== X-Gm-Message-State: AD7BkJIkBQ1X4yX7QJORO/EZ8QEAYnag4ptlBnk2TzFqVTLAxwbGeIc269wkgo2Gtmh66Ulzw/qoddPfM9SnUVTdMFt15FJkD9XtcQK+Rh5xfN0bjU/K4/lGeaRRhbwC+0RMuvLWHnIsXirx2KXyQVaX0Wc= X-Received: by 10.176.1.16 with SMTP id 16mr1061580uak.56.1459478318490; Thu, 31 Mar 2016 19:38:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.36.136 with HTTP; Thu, 31 Mar 2016 19:38:24 -0700 (PDT) From: "Lundberg, Johannes" Date: Thu, 31 Mar 2016 19:38:24 -0700 Message-ID: Subject: Zero copy data transfer from Linuxulator to FreeBSD? To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 02:38:40 -0000 SGkNCg0KSSBoYXZlIGEgVVNCIGRyaXZlciB0aGF0IHJ1bnMgaW4gTGludXggbW9kZSBhbmQgSSB3 YW50IHRvIHRyYW5zZmVyIGRhdGEgdG8NCmEgbmF0aXZlIHByb2dyYW0gZm9yIHByb2Nlc3Npbmcu DQoNCkkgdGhpbmsgdGhhdCBzaGFyZWQgbWVtb3J5IGlzIG5vdCBwb3NzaWJsZSwgd2hhdCBhcmUg b3RoZXIgKHplcm8gY29weSkNCm9wdGlvbnM/DQoNClRoYW5rcyENCgotLSAKPS09LT0tPS09LT0t PS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tCuenmOWvhuS/neaMgeOB q+OBpOOBhOOBpu+8muOBk+OBrumbu+WtkOODoeODvOODq+OBr+OAgeWQjeWum+S6uuOBq+mAgeS/ oeOBl+OBn+OCguOBruOBp+OBguOCiuOAgeenmOWMv+eJueaoqeOBruWvvuixoeOBqOOBquOCi+aD heWgseOCkuWQq+OCk+OBp+OBhOOBvuOBmeOAggrjgoLjgZfjgIHlkI3lrpvkurrku6XlpJbjga7m lrnjgYzlj5fkv6HjgZXjgozjgZ/loLTlkIjjgIHjgZPjga7jg6Hjg7zjg6vjga7noLTmo4TjgIHj gYrjgojjgbPjgZPjga7jg6Hjg7zjg6vjgavplqLjgZnjgovkuIDliIfjga7plovnpLrjgIEK6KSH 5YaZ44CB6YWN5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv6KiY6LyJ5YaF5a65 44Gr5Z+644Gl44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE44KI44GG44GK6aGY 44GE55Sz44GX5LiK44GS44G+44GZ44CCCi0tLQpDT05GSURFTlRJQUxJVFkgTk9URTogVGhlIGlu Zm9ybWF0aW9uIGluIHRoaXMgZW1haWwgaXMgY29uZmlkZW50aWFsCmFuZCBpbnRlbmRlZCBzb2xl bHkgZm9yIHRoZSBhZGRyZXNzZWUuCkRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiBv ciBhbnkgb3RoZXIgYWN0aW9uIG9mIHVzZSBvZiB0aGlzCmVtYWlsIGJ5IHBlcnNvbiBvdGhlciB0 aGFuIGludGVuZGVkIHJlY2lwaWVudCwgaXMgcHJvaGliaXRlZC4KSWYgeW91IGFyZSBub3QgdGhl IGludGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluCmVycm9y LCBwbGVhc2UgZGVzdHJveSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4K From owner-freebsd-hackers@freebsd.org Fri Apr 1 04:45:20 2016 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 B9A7DAE5E80; Fri, 1 Apr 2016 04:45:20 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9057311C5; Fri, 1 Apr 2016 04:45:20 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id g185so140048178ioa.2; Thu, 31 Mar 2016 21:45:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to :content-transfer-encoding; bh=R2jE2RZ3Pi3IujN0GvHfVVdsNMGr29VRqCAw9KaoBIQ=; b=wM+9rR8z7DYdVfSYnEKggRbFMM3nvm7onqHXnG484l5tEeiFsaRwdfQA5NdZKw8wjw PIDIpy+tSYMUejevK36gutqw3Hj7mjO9qmlTlxqTHdQ8G/Ust8LB6WgI015hJaJdcjJM Jmi/E63nWIICAL3jUr0KthEVTOff5sMbry5aialExTbfmm5nAa8oQUZC6Su9DxUPhZJz akibAWVYxMbrmY2EVxNHK6xhHNXH037dnSxO9kD9yM4iRnU+7wRVRcMiBn2cbNrDYYiS pcStgvYob99QWCAxLH4wp6NdboBZwQEg4uVvk5B9iQ7YO0IK40D2Mip6SG+Dh9eIiOXl wxJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:content-transfer-encoding; bh=R2jE2RZ3Pi3IujN0GvHfVVdsNMGr29VRqCAw9KaoBIQ=; b=AAgcEyAVb/BtEixgXidl46lxAw8MZsm4NcuJSLNFpa3x4rhnJS9Hmo2D6HInGnYbUn fcMGGiF6mNPQcpIuj0OmDAi92QCmwG4gYDw7uEJ5AnqHcR8s9n6ffgcXRy5kKwzEZogB HXYq6UZ1NZQmUR2P2SdVEnzouxF7J0z5KMkqrwuX7kxxXQG8jMiqWSjlhUGXcLLgwGps l/u3UYGLlYIh0TWmMwSe9xp11PG7rRi8AzMEaNzeLew3Meq8xVa7UZj2brSPkrwe8sNF 1RRUzGQzmsvvqG+i78Kb2Muvz7VZ+g91Aj8bCfMWogfONByE0hJY6WSH2JCYogbWmXpt DsJg== X-Gm-Message-State: AD7BkJKZsnYuzdvUHSrM6WiH8IFExJIwZ1j+crQSoG9Vt4wqcmpOsUdjUsORNBgyRNRryCxcr9XKEGmTGUUJTg== MIME-Version: 1.0 X-Received: by 10.107.41.211 with SMTP id p202mr8644693iop.4.1459485919817; Thu, 31 Mar 2016 21:45:19 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.130.130 with HTTP; Thu, 31 Mar 2016 21:45:19 -0700 (PDT) Date: Fri, 1 Apr 2016 00:45:19 -0400 X-Google-Sender-Auth: l69pvbFhzeRFManpfDLdEDmTP2g Message-ID: Subject: Catching core files in read-only jails From: J David To: "freebsd-questions@freebsd.org" , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 04:45:20 -0000 If an application is running on a production server in a read-only jail for security purposes, and it crashes occasionally due to some unknown bug, is there any way to catch a core file? Setting kern.corefile seems to still be relative to the jail. (Or, at least, no corefile is generated.) There are a lot of these processes and they don=E2=80=99t crash very often,= so leaving gdb attached isn=E2=80=99t really feasible either. (It=E2=80=99s b= een tried, but apparently requires a bit more luck than is currently in evidence.) Thusfar all attempts to get it to crash in a controlled/test environment have also been unsuccessful. Does anyone have any ideas for how to find out what=E2=80=99s causing the c= rash? Thanks for any advice! From owner-freebsd-hackers@freebsd.org Fri Apr 1 06:23:09 2016 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 31597AE9483 for ; Fri, 1 Apr 2016 06:23:09 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (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 DE1FB113E for ; Fri, 1 Apr 2016 06:23:08 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 0CC3E47BD for ; Fri, 1 Apr 2016 06:22:58 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/0CC3E47BD; dkim=none; dkim-atps=neutral Subject: Re: Catching core files in read-only jails To: freebsd-hackers@freebsd.org References: From: Matthew Seaman Message-ID: <56FE13BA.4060500@FreeBSD.org> Date: Fri, 1 Apr 2016 07:22:50 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xN6LuKVf1X6LFI63vppRJhwFfvSBMkQUv" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=1.0 required=5.0 tests=SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 06:23:09 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xN6LuKVf1X6LFI63vppRJhwFfvSBMkQUv Content-Type: multipart/mixed; boundary="c7dtCl3gXjXeMeHIX7LNQu2RBRE0W8Ljp" From: Matthew Seaman To: freebsd-hackers@freebsd.org Message-ID: <56FE13BA.4060500@FreeBSD.org> Subject: Re: Catching core files in read-only jails References: In-Reply-To: --c7dtCl3gXjXeMeHIX7LNQu2RBRE0W8Ljp Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/04/2016 05:45, J David wrote: > If an application is running on a production server in a read-only > jail for security purposes, and it crashes occasionally due to some > unknown bug, is there any way to catch a core file? You'll have to mount a read-write filesystem somewhere in your jail and configure core dumps to be written to that filesystem. Something like this example from core(5): sysctl kern.corefile=3D/var/coredumps/%U/%N.core This should have minimal security implications if the r/w filesystem is only used for recording coredumps. You could mark it noexec and nosuid as well. Cheers, Matthew --c7dtCl3gXjXeMeHIX7LNQu2RBRE0W8Ljp-- --xN6LuKVf1X6LFI63vppRJhwFfvSBMkQUv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJW/hPBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATGzAP/2MVvbAaJh+Tbnl2uXC+rUVz EwcAAwbqivFHl/hWp2f1xgov8QlbP0D0PajqDtQnSwjrfwfdmVcR+9Nr49BkRmj+ t3XWBrAgb8R00UCxQaG9Y+6G115IiJm+yTEWOJP01FHNPtb/e6GP5TQmwZXm6Cd5 zK+hww4/G2tRDBrJ5QZP/OPg4drPrA8jJIKGBtWf/aTeG7Clv5sv8/bwbkY1AWzL yURVygbaX47gDn0pAtmBwMR12PQ8cKowEQZMAxCaFt1k2ssQJht2qytWTKoQsms3 jUuzowDldGYw2O6FFB8gqj2NiAdLejp+VJqzQGGIxzYoNBJ20Q4j7e4V8i0Mrniy /il8sCCjtbcoreVdZNhiy23I+MhMp1iUuKL3zhKvMN6eChl2hDnWmRjAlQzGjFzH tQCsOD5d93ZbaNwHuy8Dim5QZEtolbGq3jisOiqAVycduGDzXZ9RbkPPCDYC5zy/ qx72Vms6Co8W19wqorwjtXsbgrh3vc6P2gHuOkaIbi6lfI4xYk7cnzwXLWBNHIgt Qb5/GOyydPry72eQRARE0sAJuxpaZQEYyAQpG9i1nYEGk9HBKGof/Kd+op5N9EX6 O6AVGHvJhmW09XABxOm0xCtOuZHKyGmQza3L7lu0Hii9AExWjOF2r7PEBRA2neJz PCHq/xenttxhq3Y2pDSO =wneZ -----END PGP SIGNATURE----- --xN6LuKVf1X6LFI63vppRJhwFfvSBMkQUv-- From owner-freebsd-hackers@freebsd.org Fri Apr 1 08:15:47 2016 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 53B7CAE6B9C for ; Fri, 1 Apr 2016 08:15:47 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 1E3C81BD3 for ; Fri, 1 Apr 2016 08:15:46 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A0CF31FE023; Fri, 1 Apr 2016 10:15:44 +0200 (CEST) From: Hans Petter Selasky Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? To: "Lundberg, Johannes" , freebsd-hackers@freebsd.org References: Message-ID: <56FE2EE8.8000301@selasky.org> Date: Fri, 1 Apr 2016 10:18:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 08:15:47 -0000 On 04/01/16 04:38, Lundberg, Johannes wrote: > Hi > > I have a USB driver that runs in Linux mode and I want to transfer data to > a native program for processing. > > I think that shared memory is not possible, what are other (zero copy) > options? > > Thanks! > Can you explain a bit how the current program moves data around? --HPS From owner-freebsd-hackers@freebsd.org Fri Apr 1 05:35:00 2016 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 6965DAE81F9; Fri, 1 Apr 2016 05:35:00 +0000 (UTC) (envelope-from terje@elde.net) Received: from rand.keepquiet.net (keepquiet.net [144.76.43.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "keepquiet.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 330341AF1; Fri, 1 Apr 2016 05:34:59 +0000 (UTC) (envelope-from terje@elde.net) Received: from [10.130.11.109] (cm-84.210.87.28.getinternet.no [84.210.87.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: terje@elde.net) by rand.keepquiet.net (Postfix) with ESMTPSA id BE8DF811; Fri, 1 Apr 2016 05:26:25 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Catching core files in read-only jails From: Terje Elde X-Mailer: iPhone Mail (13E238) In-Reply-To: Date: Fri, 1 Apr 2016 07:26:24 +0200 Cc: "freebsd-questions@freebsd.org" , "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <16281C09-B7D2-43C4-B2E1-98AF02DAB24A@elde.net> References: To: J David X-Mailman-Approved-At: Fri, 01 Apr 2016 11:14:33 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 05:35:00 -0000 > On 01 Apr 2016, at 06:45, J David wrote: >=20 > If an application is running on a production server in a read-only > jail for security purposes, and it crashes occasionally due to some > unknown bug, is there any way to catch a core file? Wherever you allow it to write core files, would be writable by the jail, at= least those files. It's tempting to recommend a single writable, but no-exe= c and no-suid dir inside the jail, and point cores there. It's an easy fix, a= nd the alternative - allow writes outside the jail - probably isn't any bett= er. If you're concerned about something being persisted in the jail, you can wip= e or even recreate that dir whenever you're starting the jail.=20 Terje From owner-freebsd-hackers@freebsd.org Fri Apr 1 09:41:55 2016 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 889AAAEBE40 for ; Fri, 1 Apr 2016 09:41:55 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 54CF8194C; Fri, 1 Apr 2016 09:41:55 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 00BE04FB03; Fri, 1 Apr 2016 09:32:40 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u319WdeB009588; Fri, 1 Apr 2016 09:32:40 GMT (envelope-from phk@phk.freebsd.dk) To: Matthew Seaman cc: freebsd-hackers@freebsd.org Subject: Re: Catching core files in read-only jails In-reply-to: <56FE13BA.4060500@FreeBSD.org> From: "Poul-Henning Kamp" References: <56FE13BA.4060500@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9586.1459503159.1@critter.freebsd.dk> Date: Fri, 01 Apr 2016 09:32:39 +0000 Message-ID: <9587.1459503159@critter.freebsd.dk> X-Mailman-Approved-At: Fri, 01 Apr 2016 11:22:06 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 09:41:55 -0000 -------- In message <56FE13BA.4060500@FreeBSD.org>, Matthew Seaman writes: >> If an application is running on a production server in a read-only >> jail for security purposes, and it crashes occasionally due to some >> unknown bug, is there any way to catch a core file? > >You'll have to mount a read-write filesystem somewhere in your jail and >configure core dumps to be written to that filesystem. Something like >this example from core(5): It would be really nice if instead of coredumps one could select to just get a stack backtrace. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@freebsd.org Fri Apr 1 14:44:09 2016 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 E46ABAEBC81; Fri, 1 Apr 2016 14:44:09 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (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 B36AC1679; Fri, 1 Apr 2016 14:44:09 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ob0-x233.google.com with SMTP id kf9so123245437obc.1; Fri, 01 Apr 2016 07:44:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=7ItE0+PZnkAJQBDFY4KoxWZAaC0Y7DeYRxRaDhqltX8=; b=OII/GaVMxGPORIZseJzwVpFt//g/Shm+weKM9X4F0CfQgHDj95rA51TGbu4vykhqMR VtkdtGhvNaCOeUq9Qu3uCXHgG7TlHrJj+GwzQixSb1CiGj+cvMw8TEuHx0yD0u1o276n TxiqbPDN4VHacJ1OlDgivSUzdko2Af0BxzWOmmAgOxrdSw2GkV+v0vpz65vq3WTLkImp D+NQUXCTDlRyX+BOV1stx2rKOcuyKwl9sU20i3QpJtwNHelPqjccrgYW5bNgLphqegqQ VWtE/AkWsSKtuwy3khjjCIBGnF0pIvhrnJQFQ3fnLfGEFSiuhXGezDaI62I1k+1SOm+S xQPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=7ItE0+PZnkAJQBDFY4KoxWZAaC0Y7DeYRxRaDhqltX8=; b=UCFwVh2rW3ucZF2bDviv8DYv0L8MN3rF4dpnxGuT27/AU5guI/o1TArlJ1rwMU8F1C e+9gNgf+MVHDWS4RGFOTdNX9GCGV0r8zNv+HhTUb/CTlNnR6Bgsx1/4UE1Kut0rRxyQf GWtUzGUNLmP0j5bm+z6LFJg16MkoTlDuFw3ieJVbC4Mo4VaiOdDZRB8nri/ebEc6ia/x vR/ViqzuDdxmL+E6vbDPrwUZP1Jz9xdm6ruevxmNJAbZpKgVbSqeZ2i+j5uPN9D65Qpv JHqZKpVe4acXS+rzFr7HqhyWmpO0F0uDxeHiAWuomjwXNZzYUHCguOWuzWZgjXxIxOzp O0tw== X-Gm-Message-State: AD7BkJJ0DKFStvbPnCGhrQ5FZMAnu3B3c4DauHzUrA8fISuTHymYkhSvpIF/HsFGCXu9XODLqiBTn0INDexjjw== MIME-Version: 1.0 X-Received: by 10.182.66.169 with SMTP id g9mr3154787obt.49.1459521848870; Fri, 01 Apr 2016 07:44:08 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Fri, 1 Apr 2016 07:44:08 -0700 (PDT) In-Reply-To: <16281C09-B7D2-43C4-B2E1-98AF02DAB24A@elde.net> References: <16281C09-B7D2-43C4-B2E1-98AF02DAB24A@elde.net> Date: Fri, 1 Apr 2016 08:44:08 -0600 X-Google-Sender-Auth: -tKk89pHfji5EqFiWKpcuBcNQGc Message-ID: Subject: Re: Catching core files in read-only jails From: Alan Somers To: Terje Elde Cc: J David , "freebsd-hackers@freebsd.org" , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 14:44:10 -0000 On Thu, Mar 31, 2016 at 11:26 PM, Terje Elde wrote: > > > > On 01 Apr 2016, at 06:45, J David wrote: > > > > If an application is running on a production server in a read-only > > jail for security purposes, and it crashes occasionally due to some > > unknown bug, is there any way to catch a core file? > > Wherever you allow it to write core files, would be writable by the jail, > at least those files. It's tempting to recommend a single writable, but > no-exec and no-suid dir inside the jail, and point cores there. It's an > easy fix, and the alternative - allow writes outside the jail - probably > isn't any better. > > If you're concerned about something being persisted in the jail, you can > wipe or even recreate that dir whenever you're starting the jail. > > Terje > > And if you are using ZFS, then you should set a quota on /var/coredumps to prevent a frequently crashing program from filling your hard disk. From owner-freebsd-hackers@freebsd.org Fri Apr 1 15:02:16 2016 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 96EAEAEC4CF for ; Fri, 1 Apr 2016 15:02:16 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57C5812CC for ; Fri, 1 Apr 2016 15:02:16 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-yw0-x234.google.com with SMTP id d68so27882594ywe.1 for ; Fri, 01 Apr 2016 08:02:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4QwwOpkgym8MJowuE6GhCgqZoN1nV9XNZGXDLxUGZuo=; b=gP8JPuEa2NQKAqevsKxU5QR0CJk+01IVhAM9+cZzyCR9PJ/nUYZ92lchAjbFbGida0 dEXvXExMT/vf3vevF4NVnqIPUSezXlwetN43rZ8p9KuUVlP9gmnctNa7b99U0vsgk0Bw tFqKHOLyvXZozgDCRUFdfX0lolPMguCSHu0fnMlFl8smgCdqbvo5opMhaUdtFLglqAXZ 8GvhmMAx9mSvvt0pwHCNNwuSmb7LbGmiVByVMuQ/3hAw+SfzKJHA5yC3syJ5nNCBTyau 3WiRrv4IB+PiBJZvPCkGUqurID0s6blPJmFZdLNqEG4fjoQUnPrvOM1KUt2oomLwKydX 95FQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4QwwOpkgym8MJowuE6GhCgqZoN1nV9XNZGXDLxUGZuo=; b=LqtROiTJWvHva22OwxDLn8dV+NPvfKw02kGqH+S9rjADAZ4N3FwUnYyAR2xdD/mOI0 yLZ/yBzRbEYMHfSLTjLkksjPi7JWvOuI6cQXdGZ9zEgSFYg+uQnzrpzQz1lRXuoy4A5m giA5ZqFIE/mpQjcFNRLZyI9mb7ia7uXCxwNlGr+8kcep1CQqbvMvK/NvGPTXeJHGQyFa Cp6lpgGNyPyUWM3B/xFz/6vzSHtRaq9LEMA2Wtno1kpmHL+g/gzGf4K4gI7aqjOJ14ku XivYK/Sz7mQfpvJgYoNtkUP/PXFOtVQ4dtVX5KQYfHLBoUtUXObHePTjtvBJC4+cYAaA B9Mw== X-Gm-Message-State: AD7BkJKrodOrG1gSApZbcaJbnbMpB6bvZt3HGVflIYCq8U9jPoCTSr+/a2H65ejN+b2QZW4ptS/1f3ewyo3mdIOoY7LmUzAoxhfCPrDQ7lIz0LnqmwVGiCU7aMckcMUgHI4lFI6CmCNgCjIwISAO9Zoo5fE= X-Received: by 10.37.95.9 with SMTP id t9mr3042477ybb.29.1459522935225; Fri, 01 Apr 2016 08:02:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.145.11 with HTTP; Fri, 1 Apr 2016 08:02:00 -0700 (PDT) In-Reply-To: <56FE2E87.9090806@selasky.org> References: <56FE2E87.9090806@selasky.org> From: "Lundberg, Johannes" Date: Fri, 1 Apr 2016 08:02:00 -0700 Message-ID: Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? To: Hans Petter Selasky Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 15:02:16 -0000 V2VsbCwgSSBkaWQgc29tZXRoaW5nIHNpbWlsYXIgYSBjb3VwbGUgb2YgeWVhcnMgYWdvIHdoZXJl IEkgZ3JhYiByYXcgZGF0YQ0KZnJvbSBhIHNwZWNpYWwgaW5mcmFyZWQgY2FtZXJhIHdpdGggcHJv cHJpZXRhcnkgVVNCIGRyaXZlci4gSSBzZW50IHRoZSByYXcNCmRhdGEgdG8gYSBGcmVlQlNEIHBy b2Nlc3MgdXNpbmcgc29ja2V0cyB3aGVyZSBpdCBpcyBwcm9jZXNzZWQgYW5kIGJlY29tZXMNCnRo ZSBpbnB1dCBkYXRhIGZvciB0aGUgZ2VzdHVyZSByZWNvZ25pdGlvbiBzb2Z0d2FyZSBBUEkuIEl0 IHdhcyBraW5kIG9mDQp1bnN0YWJsZSBkdWUgdG8gcG9vcmx5IHdyaXR0ZW4gcHJvcHJpZXRhcnkg ZHJpdmVyIHNvIEkgY291bGRuJ3QgdXNlIGl0IHRoYXQNCm11Y2guDQoNCk5vdyB0aGVyZSdzIGEg bmV3IGRldmljZSB3aXRoIHRvdGFsbHkgbmV3IGRyaXZlciBhbmQgSSB0aG91Z2h0IEknZCBnaXZl IGl0DQphIHRyeSBhZ2Fpbi4gRnJvbSBteSBwcmV2aW91cyBhdHRlbXB0cyBJIHRoaW5rIEkgY2Ft ZSB0byB0aGUgY29uY2x1c2lvbg0KdGhhdCBzaG0gY2FuIG5vdCBiZSB1c2VkIGJldHdlZW4gYSBM aW51eCBhbmQgYSBuYXRpdmUgcHJvY2Vzcy4uLg0KDQpSYXcgZGF0YSB0cmFuc2ZlciByYXRlIGlz IHNvbWV0aGluZyBsaWtlIDEwMCBNYml0L3NlYyAoMi40IE1iaXQgYXQgNDUgZnBzKS4NCg0KSSB0 aGluayB0aGUgZHJpdmVyIGFsbG9jYXRlcyBtZW1vcnkgZm9yIHRoZSBkYXRhIGFuZCB0cmFuc2Zl cnMgaXQgdGhlcmUNCmZyb20gdGhlIFVTQiBkZXZpY2Ugc28gSSBndWVzcyB6ZXJvIGNvcHkgd291 bGQgYmUgaW1wb3NzaWJsZS4uIEF0IGxlYXN0IGlmDQpJIGNvdWxkIGRvIGl0IHdpdGggb25lIGNv cHkgd291bGQgYmUgbmljZS4uDQoNClNvbWV0aGluZyBsaWtlOg0KDQpVU0IgZGV2aWNlIC0+IExp bnV4IGRyaXZlcidzIG1lbW9yeSAtPiBbSVBDXSAtPiBuYXRpdmUgcHJvY2Vzcw0KDQoNCk9uIEZy aSwgQXByIDEsIDIwMTYgYXQgMToxNyBBTSwgSGFucyBQZXR0ZXIgU2VsYXNreSA8aHBAc2VsYXNr eS5vcmc+IHdyb3RlOg0KDQo+IE9uIDA0LzAxLzE2IDA0OjM4LCBMdW5kYmVyZywgSm9oYW5uZXMg d3JvdGU6DQo+DQo+PiBIaQ0KPj4NCj4+IEkgaGF2ZSBhIFVTQiBkcml2ZXIgdGhhdCBydW5zIGlu IExpbnV4IG1vZGUgYW5kIEkgd2FudCB0byB0cmFuc2ZlciBkYXRhIHRvDQo+PiBhIG5hdGl2ZSBw cm9ncmFtIGZvciBwcm9jZXNzaW5nLg0KPj4NCj4+IEkgdGhpbmsgdGhhdCBzaGFyZWQgbWVtb3J5 IGlzIG5vdCBwb3NzaWJsZSwgd2hhdCBhcmUgb3RoZXIgKHplcm8gY29weSkNCj4+IG9wdGlvbnM/ DQo+Pg0KPj4gVGhhbmtzIQ0KPj4NCj4+DQo+IENhbiB5b3UgZXhwbGFpbiBhIGJpdCBob3cgdGhl IGN1cnJlbnQgcHJvZ3JhbSBtb3ZlcyBkYXRhIGFyb3VuZD8NCj4NCj4gLS1IUFMNCj4NCgotLSAK PS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tCuen mOWvhuS/neaMgeOBq+OBpOOBhOOBpu+8muOBk+OBrumbu+WtkOODoeODvOODq+OBr+OAgeWQjeWu m+S6uuOBq+mAgeS/oeOBl+OBn+OCguOBruOBp+OBguOCiuOAgeenmOWMv+eJueaoqeOBruWvvuix oeOBqOOBquOCi+aDheWgseOCkuWQq+OCk+OBp+OBhOOBvuOBmeOAggrjgoLjgZfjgIHlkI3lrpvk urrku6XlpJbjga7mlrnjgYzlj5fkv6HjgZXjgozjgZ/loLTlkIjjgIHjgZPjga7jg6Hjg7zjg6vj ga7noLTmo4TjgIHjgYrjgojjgbPjgZPjga7jg6Hjg7zjg6vjgavplqLjgZnjgovkuIDliIfjga7p lovnpLrjgIEK6KSH5YaZ44CB6YWN5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv 6KiY6LyJ5YaF5a6544Gr5Z+644Gl44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE 44KI44GG44GK6aGY44GE55Sz44GX5LiK44GS44G+44GZ44CCCi0tLQpDT05GSURFTlRJQUxJVFkg Tk9URTogVGhlIGluZm9ybWF0aW9uIGluIHRoaXMgZW1haWwgaXMgY29uZmlkZW50aWFsCmFuZCBp bnRlbmRlZCBzb2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUuCkRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRp c3RyaWJ1dGlvbiBvciBhbnkgb3RoZXIgYWN0aW9uIG9mIHVzZSBvZiB0aGlzCmVtYWlsIGJ5IHBl cnNvbiBvdGhlciB0aGFuIGludGVuZGVkIHJlY2lwaWVudCwgaXMgcHJvaGliaXRlZC4KSWYgeW91 IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVt YWlsIGluCmVycm9yLCBwbGVhc2UgZGVzdHJveSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4K From owner-freebsd-hackers@freebsd.org Fri Apr 1 15:10:24 2016 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 BF4FEAEC771 for ; Fri, 1 Apr 2016 15:10:24 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 308B81823 for ; Fri, 1 Apr 2016 15:10:24 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id k79so83875150lfb.2 for ; Fri, 01 Apr 2016 08:10:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=Y1/UIfqKsQhYsd3jfB1AWU8pr+5353Lfl38MnW5+1Vc=; b=rIyKZFGKAtDq41FtUTd9I/HWa64Xr/UU7sMLN9WSFqzLe6UDrizQgpNMSrD+PNusb5 wNlALeRdiHNCNxzs7vi2e5JR2O9enYja2X2JvuUv/3zFwz0MFdGNJIUSAVm40NRaEMUX EXUEBWOF+YPTEmZZLaW4BUQfL5Uxjg9Q2vqJwCTGUYgYAWFj6vOAgmLGJ4XKgFdzbsTa 4Byd3SRYvC38uow2CGfr2OMcnbcVRYJ72Ed4O8/3CWn8NME6q73OQYBrt0eDd6PZ4Rdi MTlCjVgsoEZT2YBZFnTngKm0E3vKV8G1DHL41nVQMnz/YWgRK8TYich4W1aV2Y3A0uSx bnUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Y1/UIfqKsQhYsd3jfB1AWU8pr+5353Lfl38MnW5+1Vc=; b=L9nJxklHxdzyEyutM1KC5JgID8Ew836Jx6Kay+0BEpuxbdlqozpijpzkakEJZnadwz ezLVnnb9HfZoT3AKWWitOHDdDQ1o20DBeWdwoDOb9YdK4ygrruMB480JxEVFsLAraEuP LPwMtg2oe3c+snA7MBUdAPHYkPtlQqLsPsn0oGVNkCZCwZKxJvsU7UH4M4OR7vDg1bsy /3PwxjZfEEmkmQXJ6es9fGPyx3FgzgRlqB5WeFih/YZTexDD21lAOBh+pbAt4AuxrB6/ n1LagLcIR68iUWkw5+kY1CMAlWzhubty4GCVHdSj3beh1mcfPE4VRIMOfQ7spcCekJpZ MklQ== X-Gm-Message-State: AD7BkJJpGBozr9kFoYxNWgLvxpq03ntr3nUi9cnLK/9Wdsea05kDI+VjJfYgm/l9g/VVcKnyKb67nkhBcCkicw== MIME-Version: 1.0 X-Received: by 10.25.153.15 with SMTP id b15mr723681lfe.136.1459523422433; Fri, 01 Apr 2016 08:10:22 -0700 (PDT) Sender: rizzo.unipi@gmail.com Received: by 10.114.199.19 with HTTP; Fri, 1 Apr 2016 08:10:22 -0700 (PDT) In-Reply-To: References: <56FE2E87.9090806@selasky.org> Date: Fri, 1 Apr 2016 17:10:22 +0200 X-Google-Sender-Auth: JrV6F3DY-T83ZznPUEewoTsdz4I Message-ID: Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? From: Luigi Rizzo To: "Lundberg, Johannes" Cc: Hans Petter Selasky , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 15:10:24 -0000 On Fri, Apr 1, 2016 at 5:02 PM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Well, I did something similar a couple of years ago where I grab raw data > from a special infrared camera with proprietary USB driver. I sent the ra= w > data to a FreeBSD process using sockets where it is processed and becomes > the input data for the gesture recognition software API. It was kind of > unstable due to poorly written proprietary driver so I couldn't use it th= at > much. > > Now there's a new device with totally new driver and I thought I'd give i= t > a try again. From my previous attempts I think I came to the conclusion > that shm can not be used between a Linux and a native process... > > Raw data transfer rate is something like 100 Mbit/sec (2.4 Mbit at 45 fps= ). > > I think the driver allocates memory for the data and transfers it there > from the USB device so I guess zero copy would be impossible.. At least i= f > I could do it with one copy would be nice.. > =E2=80=8BWith those low data rates the number of copies is completely irrelevant=E2=80=8B =E2=80=8Bon modern hardware. Save yourself the trouble of unnecessary optimizations and just privilege simplicity. cheers luigi > Something like: > > USB device -> Linux driver's memory -> [IPC] -> native process > > > On Fri, Apr 1, 2016 at 1:17 AM, Hans Petter Selasky > wrote: > > > On 04/01/16 04:38, Lundberg, Johannes wrote: > > > >> Hi > >> > >> I have a USB driver that runs in Linux mode and I want to transfer dat= a > to > >> a native program for processing. > >> > >> I think that shared memory is not possible, what are other (zero copy) > >> options? > >> > >> Thanks! > >> > >> > > Can you explain a bit how the current program moves data around? > > > > --HPS > > > > -- > =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- > =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 > =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 > =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 > --- > CONFIDENTIALITY NOTE: The information in this email is confidential > and intended solely for the addressee. > Disclosure, copying, distribution or any other action of use of this > email by person other than intended recipient, is prohibited. > If you are not the intended recipient and have received this email in > error, please destroy the original message. > _______________________________________________ > 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 -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2217533 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-hackers@freebsd.org Fri Apr 1 15:18:22 2016 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 C3764AECB5F for ; Fri, 1 Apr 2016 15:18:22 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 897851EA6 for ; Fri, 1 Apr 2016 15:18:22 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-yw0-x22c.google.com with SMTP id g127so166185923ywf.2 for ; Fri, 01 Apr 2016 08:18:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L8ZIUJ2Qnd2qjq9aKXDYN5fClLXCrHn4BLcVJc9DlBU=; b=JRnkUFQsvs2X/6jVEjMt7m8q+chkqMcznMayGT4MYNNXehgHNc5bNPBZZ+Wa6ZVJWM Go7eND9RFjouZbnRDlD4UvkYSp3llpvqlGQi1bnScI0lQmcVl7f0ul0fFUMN9GbAWeRV vOBEq1hHEhDSdw12S1mD6lIdTkcQ4DqmnzwnXALb59U2TkQ/WudbQARoHpPNMLF4+L8u 9NlE0xfxFIA8peXSVOqryDfFSzmRDBswnFQGoA+TA1G6EOhMTi3jbyzNTqgRCfHRGxB1 jTJyCweWU1lWnjPKpFfRDqfbuNK08cHv17iJrWU/gXBBEYk1subV/JD8aA+/qU1RKGWm YvdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L8ZIUJ2Qnd2qjq9aKXDYN5fClLXCrHn4BLcVJc9DlBU=; b=akkFfQiAnHvXWF8uXlb/IsMGhUrWFeqqQOHdXyCEo9vXGV7RA5vxqFoAW96MiCavXq ZUixJTvV2RTETdZZIPXhPl8bU+nWspIJGiV41+Ch2e86SQcpPcpJFZtA1lBD/VJsWf6K 873l+wFuZ3+hGPNXIfMu5bczTLrip8GeHKnTWQ/uz+9co+7pVuMuqpFe9wTPBQFFty6U GRU6N6r15lu1MZV7yI7ns0aEJxP97jDfqBLeVCwaNhYAtW+VbOllMHCepziwtCiclEr5 MswmFz07mOIJFG1cpztINpik1Dd7SyXo2hPW2xgloiJKtYGjLx+Wsd5vNmSrGAqD8IQn /+Hg== X-Gm-Message-State: AD7BkJKGNP7Nx4axaranBKRxPNhPQS2vd+jUK7q5cQ9YZhS2ZeYqNB2LFNQ5XRwRy3zZZuHYUI2doVfaj7lKUwGdpOiPJGa5rpCs2FtuzYePfg3oYJ94LcV3OnWnVlcbBGmyJbsvQ2L4qkXMlu3BYHSElR0= X-Received: by 10.37.97.148 with SMTP id v142mr6012317ybb.71.1459523900167; Fri, 01 Apr 2016 08:18:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.145.11 with HTTP; Fri, 1 Apr 2016 08:18:05 -0700 (PDT) In-Reply-To: References: <56FE2E87.9090806@selasky.org> From: "Lundberg, Johannes" Date: Fri, 1 Apr 2016 08:18:05 -0700 Message-ID: Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? To: Luigi Rizzo Cc: Hans Petter Selasky , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 15:18:22 -0000 SGkgTHVpZ2kNCg0KU2luY2UgdGhpcyBpcyBhbiBlbWJlZGRlZCBkZXZpY2UgcnVubmluZyBvbiBi YXR0ZXJ5IGV2ZXJ5IGJpdCBjb3VudHMuDQpIb3dldmVyLCB0aGlzIGlzIGtpbmQgb2YgYSB0ZW1w b3Jhcnkgc29sdXRpb24gc28gSSdtIGNvbnNpZGVyaW5nIGFjY2VwdGluZw0KaXQuLg0KDQpBdCBh bnkgcmF0ZSwgSSBhbSBnZW5lcmFsbHkgY3VyaW91cyB3aGF0IG1lY2hhbmlzbSB0aGVyZSBhcmUg Zm9yDQp0cmFuc2ZlcnJpbmcgZGF0YSBiZXR3ZWVuIExpbnV4IGFuZCBuYXRpdmUgcHJvY2VzcyBp biBGcmVlQlNELi4NCg0KDQpPbiBGcmksIEFwciAxLCAyMDE2IGF0IDg6MTAgQU0sIEx1aWdpIFJp enpvIDxyaXp6b0BpZXQudW5pcGkuaXQ+IHdyb3RlOg0KDQo+DQo+DQo+IE9uIEZyaSwgQXByIDEs IDIwMTYgYXQgNTowMiBQTSwgTHVuZGJlcmcsIEpvaGFubmVzIDwNCj4gam9oYW5uZXNAYnJpbGxp YW50c2VydmljZS5jby5qcD4gd3JvdGU6DQo+DQo+PiBXZWxsLCBJIGRpZCBzb21ldGhpbmcgc2lt aWxhciBhIGNvdXBsZSBvZiB5ZWFycyBhZ28gd2hlcmUgSSBncmFiIHJhdyBkYXRhDQo+PiBmcm9t IGEgc3BlY2lhbCBpbmZyYXJlZCBjYW1lcmEgd2l0aCBwcm9wcmlldGFyeSBVU0IgZHJpdmVyLiBJ IHNlbnQgdGhlIHJhdw0KPj4gZGF0YSB0byBhIEZyZWVCU0QgcHJvY2VzcyB1c2luZyBzb2NrZXRz IHdoZXJlIGl0IGlzIHByb2Nlc3NlZCBhbmQgYmVjb21lcw0KPj4gdGhlIGlucHV0IGRhdGEgZm9y IHRoZSBnZXN0dXJlIHJlY29nbml0aW9uIHNvZnR3YXJlIEFQSS4gSXQgd2FzIGtpbmQgb2YNCj4+ IHVuc3RhYmxlIGR1ZSB0byBwb29ybHkgd3JpdHRlbiBwcm9wcmlldGFyeSBkcml2ZXIgc28gSSBj b3VsZG4ndCB1c2UgaXQNCj4+IHRoYXQNCj4+IG11Y2guDQo+Pg0KPj4gTm93IHRoZXJlJ3MgYSBu ZXcgZGV2aWNlIHdpdGggdG90YWxseSBuZXcgZHJpdmVyIGFuZCBJIHRob3VnaHQgSSdkIGdpdmUg aXQNCj4+IGEgdHJ5IGFnYWluLiBGcm9tIG15IHByZXZpb3VzIGF0dGVtcHRzIEkgdGhpbmsgSSBj YW1lIHRvIHRoZSBjb25jbHVzaW9uDQo+PiB0aGF0IHNobSBjYW4gbm90IGJlIHVzZWQgYmV0d2Vl biBhIExpbnV4IGFuZCBhIG5hdGl2ZSBwcm9jZXNzLi4uDQo+Pg0KPj4gUmF3IGRhdGEgdHJhbnNm ZXIgcmF0ZSBpcyBzb21ldGhpbmcgbGlrZSAxMDAgTWJpdC9zZWMgKDIuNCBNYml0IGF0IDQ1DQo+ PiBmcHMpLg0KPj4NCj4+IEkgdGhpbmsgdGhlIGRyaXZlciBhbGxvY2F0ZXMgbWVtb3J5IGZvciB0 aGUgZGF0YSBhbmQgdHJhbnNmZXJzIGl0IHRoZXJlDQo+PiBmcm9tIHRoZSBVU0IgZGV2aWNlIHNv IEkgZ3Vlc3MgemVybyBjb3B5IHdvdWxkIGJlIGltcG9zc2libGUuLiBBdCBsZWFzdCBpZg0KPj4g SSBjb3VsZCBkbyBpdCB3aXRoIG9uZSBjb3B5IHdvdWxkIGJlIG5pY2UuLg0KPj4NCj4NCj4NCj4g 4oCLV2l0aCB0aG9zZSBsb3cgZGF0YSByYXRlcyB0aGUgbnVtYmVyIG9mIGNvcGllcyBpcyBjb21w bGV0ZWx5DQo+IGlycmVsZXZhbnTigIsNCj4NCj4g4oCLb24gbW9kZXJuIGhhcmR3YXJlLiBTYXZl IHlvdXJzZWxmIHRoZSB0cm91YmxlIG9mDQo+IHVubmVjZXNzYXJ5IG9wdGltaXphdGlvbnMgYW5k IGp1c3QgcHJpdmlsZWdlIHNpbXBsaWNpdHkuDQo+DQo+IGNoZWVycw0KPiBsdWlnaQ0KPg0KPg0K Pj4gU29tZXRoaW5nIGxpa2U6DQo+Pg0KPj4gVVNCIGRldmljZSAtPiBMaW51eCBkcml2ZXIncyBt ZW1vcnkgLT4gW0lQQ10gLT4gbmF0aXZlIHByb2Nlc3MNCj4+DQo+Pg0KPj4gT24gRnJpLCBBcHIg MSwgMjAxNiBhdCAxOjE3IEFNLCBIYW5zIFBldHRlciBTZWxhc2t5IDxocEBzZWxhc2t5Lm9yZz4N Cj4+IHdyb3RlOg0KPj4NCj4+ID4gT24gMDQvMDEvMTYgMDQ6MzgsIEx1bmRiZXJnLCBKb2hhbm5l cyB3cm90ZToNCj4+ID4NCj4+ID4+IEhpDQo+PiA+Pg0KPj4gPj4gSSBoYXZlIGEgVVNCIGRyaXZl ciB0aGF0IHJ1bnMgaW4gTGludXggbW9kZSBhbmQgSSB3YW50IHRvIHRyYW5zZmVyDQo+PiBkYXRh IHRvDQo+PiA+PiBhIG5hdGl2ZSBwcm9ncmFtIGZvciBwcm9jZXNzaW5nLg0KPj4gPj4NCj4+ID4+ IEkgdGhpbmsgdGhhdCBzaGFyZWQgbWVtb3J5IGlzIG5vdCBwb3NzaWJsZSwgd2hhdCBhcmUgb3Ro ZXIgKHplcm8gY29weSkNCj4+ID4+IG9wdGlvbnM/DQo+PiA+Pg0KPj4gPj4gVGhhbmtzIQ0KPj4g Pj4NCj4+ID4+DQo+PiA+IENhbiB5b3UgZXhwbGFpbiBhIGJpdCBob3cgdGhlIGN1cnJlbnQgcHJv Z3JhbSBtb3ZlcyBkYXRhIGFyb3VuZD8NCj4+ID4NCj4+ID4gLS1IUFMNCj4+ID4NCj4+DQo+PiAt LQ0KPj4gPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09 LT0tDQo+PiDnp5jlr4bkv53mjIHjgavjgaTjgYTjgabvvJrjgZPjga7pm7vlrZDjg6Hjg7zjg6vj ga/jgIHlkI3lrpvkurrjgavpgIHkv6HjgZfjgZ/jgoLjga7jgafjgYLjgorjgIHnp5jljL/nibnm qKnjga7lr77osaHjgajjgarjgovmg4XloLHjgpLlkKvjgpPjgafjgYTjgb7jgZnjgIINCj4+IOOC guOBl+OAgeWQjeWum+S6uuS7peWkluOBruaWueOBjOWPl+S/oeOBleOCjOOBn+WgtOWQiOOAgeOB k+OBruODoeODvOODq+OBruegtOajhOOAgeOBiuOCiOOBs+OBk+OBruODoeODvOODq+OBq+mWouOB meOCi+S4gOWIh+OBrumWi+ekuuOAgQ0KPj4g6KSH5YaZ44CB6YWN5biD44CB44Gd44Gu5LuW44Gu 5Yip55So44CB44G+44Gf44Gv6KiY6LyJ5YaF5a6544Gr5Z+644Gl44GP44GE44GL44Gq44KL6KGM 5YuV44KC44GV44KM44Gq44GE44KI44GG44GK6aGY44GE55Sz44GX5LiK44GS44G+44GZ44CCDQo+ PiAtLS0NCj4+IENPTkZJREVOVElBTElUWSBOT1RFOiBUaGUgaW5mb3JtYXRpb24gaW4gdGhpcyBl bWFpbCBpcyBjb25maWRlbnRpYWwNCj4+IGFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSBhZGRy ZXNzZWUuDQo+PiBEaXNjbG9zdXJlLCBjb3B5aW5nLCBkaXN0cmlidXRpb24gb3IgYW55IG90aGVy IGFjdGlvbiBvZiB1c2Ugb2YgdGhpcw0KPj4gZW1haWwgYnkgcGVyc29uIG90aGVyIHRoYW4gaW50 ZW5kZWQgcmVjaXBpZW50LCBpcyBwcm9oaWJpdGVkLg0KPj4gSWYgeW91IGFyZSBub3QgdGhlIGlu dGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluDQo+PiBlcnJv ciwgcGxlYXNlIGRlc3Ryb3kgdGhlIG9yaWdpbmFsIG1lc3NhZ2UuDQo+PiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gZnJlZWJzZC1oYWNrZXJzQGZy ZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPj4gaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWls bWFuL2xpc3RpbmZvL2ZyZWVic2QtaGFja2Vycw0KPj4gVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55 IG1haWwgdG8gImZyZWVic2QtaGFja2Vycy11bnN1YnNjcmliZUBmcmVlYnNkLm9yZw0KPj4gIg0K Pg0KPg0KPg0KPg0KPiAtLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ICBQcm9mLiBMdWlnaSBSSVpa Tywgcml6em9AaWV0LnVuaXBpLml0ICAuIERpcC4gZGkgSW5nLiBkZWxsJ0luZm9ybWF6aW9uZQ0K PiAgaHR0cDovL3d3dy5pZXQudW5pcGkuaXQvfmx1aWdpLyAgICAgICAgLiBVbml2ZXJzaXRhYCBk aSBQaXNhDQo+ICBURUwgICAgICArMzktMDUwLTIyMTc1MzMgICAgICAgICAgICAgICAuIHZpYSBE aW90aXNhbHZpIDINCj4gIE1vYmlsZSAgICszOS0zMzgtNjgwOTg3NSAgICAgICAgICAgICAgIC4g NTYxMjIgUElTQSAoSXRhbHkpDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4NCgotLSAKPS09LT0tPS09 LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tCuenmOWvhuS/neaM geOBq+OBpOOBhOOBpu+8muOBk+OBrumbu+WtkOODoeODvOODq+OBr+OAgeWQjeWum+S6uuOBq+mA geS/oeOBl+OBn+OCguOBruOBp+OBguOCiuOAgeenmOWMv+eJueaoqeOBruWvvuixoeOBqOOBquOC i+aDheWgseOCkuWQq+OCk+OBp+OBhOOBvuOBmeOAggrjgoLjgZfjgIHlkI3lrpvkurrku6XlpJbj ga7mlrnjgYzlj5fkv6HjgZXjgozjgZ/loLTlkIjjgIHjgZPjga7jg6Hjg7zjg6vjga7noLTmo4Tj gIHjgYrjgojjgbPjgZPjga7jg6Hjg7zjg6vjgavplqLjgZnjgovkuIDliIfjga7plovnpLrjgIEK 6KSH5YaZ44CB6YWN5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv6KiY6LyJ5YaF 5a6544Gr5Z+644Gl44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE44KI44GG44GK 6aGY44GE55Sz44GX5LiK44GS44G+44GZ44CCCi0tLQpDT05GSURFTlRJQUxJVFkgTk9URTogVGhl IGluZm9ybWF0aW9uIGluIHRoaXMgZW1haWwgaXMgY29uZmlkZW50aWFsCmFuZCBpbnRlbmRlZCBz b2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUuCkRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlv biBvciBhbnkgb3RoZXIgYWN0aW9uIG9mIHVzZSBvZiB0aGlzCmVtYWlsIGJ5IHBlcnNvbiBvdGhl ciB0aGFuIGludGVuZGVkIHJlY2lwaWVudCwgaXMgcHJvaGliaXRlZC4KSWYgeW91IGFyZSBub3Qg dGhlIGludGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluCmVy cm9yLCBwbGVhc2UgZGVzdHJveSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4K From owner-freebsd-hackers@freebsd.org Fri Apr 1 15:43:06 2016 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 6C095AEB46A for ; Fri, 1 Apr 2016 15:43:06 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001: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 36AC21BFD; Fri, 1 Apr 2016 15:43:06 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: by mail-ig0-x22a.google.com with SMTP id f1so4789069igr.1; Fri, 01 Apr 2016 08:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=wEeO+kqqnrlztQHkjLrfO8KSRw9NALAqv4PnIAdcEVg=; b=FE6s9BeGGRSw+Gnq3q1Iam8CTyWWY6Y/Hy86RI6FNVeei1pE1+KpnI/dDRWoiAzUrp Iqq+tdIt5zuRv9fhRRC/zB8sE47QpabgfWigOJ+L3gnO/DPJWfudCfBlDlTJI4ecZPVf 0AsbYYcb5pxCZSeqwGQDJnu4bYaRGLY2qD8iwRqAw+tS1Mg8tlrSy3wBlGcfRz0t+tQt X+Loj0eVkkTnVw0hshwVmueLcRVkH7CQ74V1dQJ5vqKNGdBBqJpaSGzaqRcOLBeHdN3v wAt5XRstEIZhoe4iCG9Yhy0OnQD/8ZpBavxq/XECXUpYAGEomda9Wqycy63xtGqvgB7o D1cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=wEeO+kqqnrlztQHkjLrfO8KSRw9NALAqv4PnIAdcEVg=; b=JMOaPJ90nftXqdNDXa6QifH+N88TmqLNfBWlqUviXAc1RDpkXuvm812peKbwnIwcgH 4l0QVVbKHvBy/usQvNp88IHOiDTERs5alnLF9GytqnkQPbPULIokyOXhOlCn2hRTE3aX 5WJxEYrlqtUabOv3Jv410rIE5xLYo8JAvgFs87g24iInoopCJdVEAZG8aVKENG5FRVrC aUYDXuvU93M5r2B4Rboy8r0FHCV1M9ZS6R5K9wixQRpi6zbcanvh22tdn5mA5uqZ44A7 Oxp9yBgwvltAs8H7Ok9HQ37dWwP6uijYnrzGt7Ra7oc+BIh0E4s6h/eg2i6It1TiLABO jfzg== X-Gm-Message-State: AD7BkJKnbhOTjsP5PDRxCCySqS2jWUOeV8uENzONTPuC/6ExOZJOQBca8NPCqeFh0DFXX/rnGfkkoG+8UYWA2w== MIME-Version: 1.0 X-Received: by 10.50.65.8 with SMTP id t8mr4381908igs.60.1459525385550; Fri, 01 Apr 2016 08:43:05 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.130.130 with HTTP; Fri, 1 Apr 2016 08:43:05 -0700 (PDT) In-Reply-To: <9587.1459503159@critter.freebsd.dk> References: <56FE13BA.4060500@FreeBSD.org> <9587.1459503159@critter.freebsd.dk> Date: Fri, 1 Apr 2016 11:43:05 -0400 X-Google-Sender-Auth: 5jX-uD0HZbKod2lyqSlIO8eONZ0 Message-ID: Subject: Re: Catching core files in read-only jails From: J David To: Poul-Henning Kamp Cc: Matthew Seaman , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 15:43:06 -0000 On Fri, Apr 1, 2016 at 5:32 AM, Poul-Henning Kamp wrot= e: > It would be really nice if instead of coredumps one could select to > just get a stack backtrace. Ah, yes, that would be great! Especially if it could automatically go into the dmesg or syslog. Or stderr for that matter. (That last would be kind of ugly, but we could make it work.) It looks like there=E2=80=99s a FreeBSD port of libsegfault now (https://github.com/stass/libsegfault ). Maybe we can wedge that in there as a medium-term solution. For the short term, we=E2=80=99ll try wedging a noexec tmpfs in there and s= ee if we can get what we need that way. Thanks for the suggestions! From owner-freebsd-hackers@freebsd.org Fri Apr 1 23:57:16 2016 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 EFCF5B008E5 for ; Fri, 1 Apr 2016 23:57:16 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E314F1E8C for ; Fri, 1 Apr 2016 23:57:16 +0000 (UTC) (envelope-from bright@mu.org) Received: from AlfredMacbookAir.local (unknown [IPv6:2601:645:8003:a4d6:4947:40d:837c:d120]) by elvis.mu.org (Postfix) with ESMTPSA id EC74F346DDE2 for ; Fri, 1 Apr 2016 16:57:09 -0700 (PDT) Subject: Re: Catching core files in read-only jails To: freebsd-hackers@freebsd.org References: <16281C09-B7D2-43C4-B2E1-98AF02DAB24A@elde.net> From: Alfred Perlstein Message-ID: <56FF0AD6.8000500@mu.org> Date: Fri, 1 Apr 2016 16:57:10 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 23:57:17 -0000 I believe you can also use a predicable name with corefiles now by using %I in the corefilename. -Alfred On 4/1/16 7:44 AM, Alan Somers wrote: > On Thu, Mar 31, 2016 at 11:26 PM, Terje Elde wrote: > >> >>> On 01 Apr 2016, at 06:45, J David wrote: >>> >>> If an application is running on a production server in a read-only >>> jail for security purposes, and it crashes occasionally due to some >>> unknown bug, is there any way to catch a core file? >> Wherever you allow it to write core files, would be writable by the jail, >> at least those files. It's tempting to recommend a single writable, but >> no-exec and no-suid dir inside the jail, and point cores there. It's an >> easy fix, and the alternative - allow writes outside the jail - probably >> isn't any better. >> >> If you're concerned about something being persisted in the jail, you can >> wipe or even recreate that dir whenever you're starting the jail. >> >> Terje >> >> > And if you are using ZFS, then you should set a quota on /var/coredumps to > prevent a frequently crashing program from filling your hard disk. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Sat Apr 2 09:19:11 2016 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 B8EEEB006AA for ; Sat, 2 Apr 2016 09:19:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 825621D89 for ; Sat, 2 Apr 2016 09:19:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id DA58A1FE023; Sat, 2 Apr 2016 11:19:08 +0200 (CEST) Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? To: "Lundberg, Johannes" , Luigi Rizzo References: <56FE2E87.9090806@selasky.org> Cc: "freebsd-hackers@freebsd.org" From: Hans Petter Selasky Message-ID: <56FF8F46.3040301@selasky.org> Date: Sat, 2 Apr 2016 11:22:14 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 09:19:11 -0000 On 04/01/16 17:18, Lundberg, Johannes wrote: > Hi Luigi > > Since this is an embedded device running on battery every bit counts. > However, this is kind of a temporary solution so I'm considering accepting > it.. > > At any rate, I am generally curious what mechanism there are for > transferring data between Linux and native process in FreeBSD.. > Hi, libusb has only one copy to/from userspace. libusb v1.0 and v0.1 has some allocation during operation, while libusb v2.0 API doesn't. There was an optimisation done recently about IOCTLs allocating memory for the data argument. Maybe that is what is causing the problem you saw? Refer to SYS_IOCTL_SMALL_SIZE in sys/kern/ . --HPS From owner-freebsd-hackers@freebsd.org Sat Apr 2 15:15:51 2016 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 5B23BB0018B for ; Sat, 2 Apr 2016 15:15:51 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9D91AD9 for ; Sat, 2 Apr 2016 15:15:50 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-vk0-x230.google.com with SMTP id e6so135400206vkh.2 for ; Sat, 02 Apr 2016 08:15:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=t5pCZQ3Zria0pna9q5pWDc00TtF5hLq9/+a/h9YGavA=; b=rUVdYT9vviqvyRn1AlLQzb2wwigekFtslTeov0AhLwLscN+Grr8voAqgE91V30yPAZ 1i1zIc6c8xCxMsOXM9bX7F0R4dxGXp6GWDBhHIoRXklYKKGG+1l5OrVnkDSSC//qtb2i NZc9zsCcO/Dy5gNEFm3X41DAK+ywg8nPINlzqo+hmxU/UOzJv+huxAnkqXbDgCJsWdRW C6gnXy6/GL2MsSsVUlp+NIZgVhBI/QjlM19e83+WHvDAbpYP9YC0+w4ACT0E8WGNqkKD kf/B/Lw/y4BiThEdKnMIQqbXnm+tQDcW8ri65Ek6RL24WiZzEq+c4KnZbVvr6X+l8/8Q y9dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t5pCZQ3Zria0pna9q5pWDc00TtF5hLq9/+a/h9YGavA=; b=WTyLIkf3PnFwL3Hhc02FjZVHlxitbDTR7YJCvBEBfAVEvXukSz9bbaj/fkPVwrjhSa mDKx80smcuPV7r9mdvJL65QPyIJbF8bl/navOwJDix/4tEdGOzvWGvysyVgFgWf4/pTs QA8soKOW+3wgFSghLHgr1VvES88tovTKtEGiXX5hNqvw7cwuwXZQxizoyoMO4MQBJFJd I/+KI6CwW1ntAJy60DK6POx24krs+SCnQvuvBWim79aMoDCTM1p4Un/mhQBUHaUOTG3C Vvw9iviQiFaqZbo0wtbb5wwAVThuO29dLXNiI7z9OATHIrwXQb7JCpp7ZzCOCIMF5DRj LNPQ== X-Gm-Message-State: AD7BkJJ9wA1u1TAaWtvhF7BqICppF5aTWfpY/TTwVzBbNAN13Qy3IbBL5MyfvMq91jDzc3Z3XlqZmHX2h6pVIWSRA8urQdnjrbPshB9onEctAQNncy6ercpOXVQxmtdIwqlPqXq52W4APYno9Xt3tgEhuhs= X-Received: by 10.176.2.240 with SMTP id 103mr3647223uah.122.1459610149761; Sat, 02 Apr 2016 08:15:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.36.136 with HTTP; Sat, 2 Apr 2016 08:15:35 -0700 (PDT) In-Reply-To: <56FF8F46.3040301@selasky.org> References: <56FE2E87.9090806@selasky.org> <56FF8F46.3040301@selasky.org> From: "Lundberg, Johannes" Date: Sat, 2 Apr 2016 08:15:35 -0700 Message-ID: Subject: Re: Zero copy data transfer from Linuxulator to FreeBSD? To: Hans Petter Selasky Cc: Luigi Rizzo , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 15:15:51 -0000 SGkgSGFucw0KDQpJIGNyZWF0ZWQgYSB1bml4IHNvY2tldCBhbmQgaW5jcmVhc2VkIHNlbmQgYnVm ZmVyIHRvIDEgTUIgdG8gYXZvaWQgcGFydGlhbA0KdHJhbnNmZXJzIChub3Qgc3VyZSBob3cgbXVj aCBvZiBhIGJlbmVmaXQgdGhlcmUgaXMgb2YgdGhhdCB0aG91Z2gpLg0KSXQgc2VlbXMgdG8gcnVu bmluZyB2ZXJ5IG5pY2VseS4gTm90IHN0YWxscyBvciBhbnl0aGluZyBsaWtlIGEgY291cGxlIG9m DQp5ZWFycyBhZ28uDQoNCg0KT24gU2F0LCBBcHIgMiwgMjAxNiBhdCAyOjIyIEFNLCBIYW5zIFBl dHRlciBTZWxhc2t5IDxocHNAc2VsYXNreS5vcmc+IHdyb3RlOg0KDQo+IE9uIDA0LzAxLzE2IDE3 OjE4LCBMdW5kYmVyZywgSm9oYW5uZXMgd3JvdGU6DQo+DQo+PiBIaSBMdWlnaQ0KPj4NCj4+IFNp bmNlIHRoaXMgaXMgYW4gZW1iZWRkZWQgZGV2aWNlIHJ1bm5pbmcgb24gYmF0dGVyeSBldmVyeSBi aXQgY291bnRzLg0KPj4gSG93ZXZlciwgdGhpcyBpcyBraW5kIG9mIGEgdGVtcG9yYXJ5IHNvbHV0 aW9uIHNvIEknbSBjb25zaWRlcmluZyBhY2NlcHRpbmcNCj4+IGl0Li4NCj4+DQo+PiBBdCBhbnkg cmF0ZSwgSSBhbSBnZW5lcmFsbHkgY3VyaW91cyB3aGF0IG1lY2hhbmlzbSB0aGVyZSBhcmUgZm9y DQo+PiB0cmFuc2ZlcnJpbmcgZGF0YSBiZXR3ZWVuIExpbnV4IGFuZCBuYXRpdmUgcHJvY2VzcyBp biBGcmVlQlNELi4NCj4+DQo+Pg0KPiBIaSwNCj4NCj4gbGlidXNiIGhhcyBvbmx5IG9uZSBjb3B5 IHRvL2Zyb20gdXNlcnNwYWNlLiBsaWJ1c2IgdjEuMCBhbmQgdjAuMSBoYXMgc29tZQ0KPiBhbGxv Y2F0aW9uIGR1cmluZyBvcGVyYXRpb24sIHdoaWxlIGxpYnVzYiB2Mi4wIEFQSSBkb2Vzbid0Lg0K Pg0KPiBUaGVyZSB3YXMgYW4gb3B0aW1pc2F0aW9uIGRvbmUgcmVjZW50bHkgYWJvdXQgSU9DVExz IGFsbG9jYXRpbmcgbWVtb3J5IGZvcg0KPiB0aGUgZGF0YSBhcmd1bWVudC4gTWF5YmUgdGhhdCBp cyB3aGF0IGlzIGNhdXNpbmcgdGhlIHByb2JsZW0geW91IHNhdz8NCj4NCj4gUmVmZXIgdG8gU1lT X0lPQ1RMX1NNQUxMX1NJWkUgaW4gc3lzL2tlcm4vIC4NCj4NCj4gLS1IUFMNCj4NCj4NCgotLSAK PS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tCuen mOWvhuS/neaMgeOBq+OBpOOBhOOBpu+8muOBk+OBrumbu+WtkOODoeODvOODq+OBr+OAgeWQjeWu m+S6uuOBq+mAgeS/oeOBl+OBn+OCguOBruOBp+OBguOCiuOAgeenmOWMv+eJueaoqeOBruWvvuix oeOBqOOBquOCi+aDheWgseOCkuWQq+OCk+OBp+OBhOOBvuOBmeOAggrjgoLjgZfjgIHlkI3lrpvk urrku6XlpJbjga7mlrnjgYzlj5fkv6HjgZXjgozjgZ/loLTlkIjjgIHjgZPjga7jg6Hjg7zjg6vj ga7noLTmo4TjgIHjgYrjgojjgbPjgZPjga7jg6Hjg7zjg6vjgavplqLjgZnjgovkuIDliIfjga7p lovnpLrjgIEK6KSH5YaZ44CB6YWN5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv 6KiY6LyJ5YaF5a6544Gr5Z+644Gl44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE 44KI44GG44GK6aGY44GE55Sz44GX5LiK44GS44G+44GZ44CCCi0tLQpDT05GSURFTlRJQUxJVFkg Tk9URTogVGhlIGluZm9ybWF0aW9uIGluIHRoaXMgZW1haWwgaXMgY29uZmlkZW50aWFsCmFuZCBp bnRlbmRlZCBzb2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUuCkRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRp c3RyaWJ1dGlvbiBvciBhbnkgb3RoZXIgYWN0aW9uIG9mIHVzZSBvZiB0aGlzCmVtYWlsIGJ5IHBl cnNvbiBvdGhlciB0aGFuIGludGVuZGVkIHJlY2lwaWVudCwgaXMgcHJvaGliaXRlZC4KSWYgeW91 IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVt YWlsIGluCmVycm9yLCBwbGVhc2UgZGVzdHJveSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4K