From owner-svn-src-head@freebsd.org Mon Oct 22 10:10:27 2018 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE57DFF2B53; Mon, 22 Oct 2018 10:10:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83119725E9; Mon, 22 Oct 2018 10:10:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [178.17.145.230]) (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 544CD260174; Mon, 22 Oct 2018 12:10:26 +0200 (CEST) Subject: Re: svn commit: r339582 - head/sys/dev/sound/midi To: Konstantin Belousov Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org References: <201810220858.w9M8wSBZ039042@repo.freebsd.org> <20181022095131.GN5335@kib.kiev.ua> From: Hans Petter Selasky Message-ID: Date: Mon, 22 Oct 2018 12:09:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <20181022095131.GN5335@kib.kiev.ua> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2018 10:10:28 -0000 On 10/22/18 11:51 AM, Konstantin Belousov wrote: > On Mon, Oct 22, 2018 at 08:58:28AM +0000, Hans Petter Selasky wrote: >> Author: hselasky >> Date: Mon Oct 22 08:58:27 2018 >> New Revision: 339582 >> URL: https://svnweb.freebsd.org/changeset/base/339582 >> >> Log: >> Drop sequencer mutex around uiomove() and make sure we don't move more bytes >> than is available, else a panic might happen. > And why it is safe to drop the mutex ? > If it is safe to drop, why do you need the mutex at all ? > The seq mutex protects the queue state, which is entirely computed prior or after uiomove(). --HPS