From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42D2BC47082 for ; Mon, 24 May 2021 00:40:32 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BDD0E61132 for ; Mon, 24 May 2021 00:40:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BDD0E61132 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=aj.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4FpJKB2d4jz3092 for ; Mon, 24 May 2021 10:40:30 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=aj.id.au header.i=@aj.id.au header.a=rsa-sha256 header.s=fm2 header.b=ojua7Mlz; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm2 header.b=WKANcriZ; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=aj.id.au (client-ip=66.111.4.224; helo=new2-smtp.messagingengine.com; envelope-from=andrew@aj.id.au; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=aj.id.au header.i=@aj.id.au header.a=rsa-sha256 header.s=fm2 header.b=ojua7Mlz; dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm2 header.b=WKANcriZ; dkim-atps=neutral Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4FpJJc2YG4z2yXl; Mon, 24 May 2021 10:40:00 +1000 (AEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 30FAF5803CE; Sun, 23 May 2021 20:39:58 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute3.internal (MEProxy); Sun, 23 May 2021 20:39:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm2; bh=5sJHMuDvNvV7pHRcupj6QN39aMOCxdc KSDsfy4XDr6I=; b=ojua7Mlz3qgeIZbbZumpj7T7jyN+s55eFPhuStyBHdgk/CV wo5DiB1u8wBL6CVKfMRYijetTBDzvIPZ3TgakzOM8T5dpHNbhQ5sWLY4hhxvRjrD mwOTpof5nzRyKtetT6YiGDzT04LCO7GWLrWBRTHluKPVv/Nu+JwbRiS2Cfv/EDQ7 947/GGP6Lk4Z6/KL30TLuG0lPZ7pUwsrjWPjfm0N8dHfIJbiiwL0GmNiFvwlu1Y2 P7+KgcSLLf5RHrokkLWhWWS2Y475TX4oVCqo9fG7WzQxMnqMVhz1OxjeTu66IH7T qeY8y25pR3e28l4+jkH3aTE4Qimn9V6CgIqFbYA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=5sJHMu DvNvV7pHRcupj6QN39aMOCxdcKSDsfy4XDr6I=; b=WKANcriZt27VBFBijYR5F1 1550UhiqtynvZmOvUbdRSZsJyXl8TAC9JYHKdMblZZpfLYMupncWt2UBq13Ia787 GjcSR4YTbrp+O8Tu/A1uPJcvq6hmhUloepfkcQ1EsZDnpy+rx2NWcH/iv5kHsII8 Se2MMfEE0QDHDb28tDqhBU8hZGUPbYurDaLbRQ2HVnubfO6xtC/sdUpQWPIXo0mH H6NKiAFDOcFGwXIwzxrPPq9xIJCBS8ZhTvYqjuWjLZx4kR1YI/nakEjIXxFNfssn Ex7y3VM3gDSiYCTjnuwR5Ix9pkBo6PUr00vAGJJ1CGY6dAl/uadeYFIm4yqxGfAw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdejkedgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdetnhgu rhgvficulfgvfhhfvghrhidfuceorghnughrvgifsegrjhdrihgurdgruheqnecuggftrf grthhtvghrnhepuddttdekueeggedvtddtueekiedutdfguedutdefieeuteefieelteet vddthfeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvgifsegrjhdrihgurdgruh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 06E6DA004B1; Sun, 23 May 2021 20:39:55 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-448-gae190416c7-fm-20210505.004-gae190416 Mime-Version: 1.0 Message-Id: <0ea513bc-f8c8-43c5-969f-b9db9fdb15d7@www.fastmail.com> In-Reply-To: <20210521173007.GJ2921206@minyard.net> References: <20210510054213.1610760-1-andrew@aj.id.au> <20210510054213.1610760-11-andrew@aj.id.au> <20210521173007.GJ2921206@minyard.net> Date: Mon, 24 May 2021 10:09:22 +0930 From: "Andrew Jeffery" To: "Corey Minyard" Subject: =?UTF-8?Q?Re:_[PATCH_v3_10/16]_ipmi:_kcs=5Fbmc:_Don't_enforce_single-ope?= =?UTF-8?Q?n_policy_in_the_kernel?= Content-Type: text/plain X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, Tomer Maimon , linux-aspeed@lists.ozlabs.org, Avi Fishman , Patrick Venture , openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org, Tali Perry , Rob Herring , Arnd Bergmann , openipmi-developer@lists.sourceforge.net, Zev Weiss , "Chia-Wei, Wang" , linux-arm-kernel@lists.infradead.org, Benjamin Fair Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" On Sat, 22 May 2021, at 03:00, Corey Minyard wrote: > On Mon, May 10, 2021 at 03:12:07PM +0930, Andrew Jeffery wrote: > > Soon it will be possible for one KCS device to have multiple associated > > chardevs exposed to userspace (for IPMI and raw-style access). However, > > don't prevent userspace from: > > > > 1. Opening more than one chardev at a time, or > > 2. Opening the same chardev more than once. > > > > System behaviour is undefined for both classes of multiple access, so > > userspace must manage itself accordingly. > > I don't understand why you want to allow this. If the second open won't > work right, then why allow it? Why remove code that causes the second > open to error? Really I was just shifting the problem to userspace so it wasn't something I needed to address in the kernel. It seems I'm alone in thinking this is a good idea, as yourself, Zev, William and Joel (privately) have pushed back against it. Initially the idea was tied up in how I was doing some interrupt handling, but in revising the code that problem has gone away. I'll just drop this patch and save everyone the heartburn of arguing about it :) Andrew