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=-0.6 required=3.0 tests=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 A00BDC28CBC for ; Sun, 3 May 2020 09:19:30 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (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 2C1C9206A5 for ; Sun, 3 May 2020 09:19:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="pZdvlcIC"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="S3+1rMQ4" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2C1C9206A5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1jVAlw-0002TJ-FX; Sun, 03 May 2020 05:18:52 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jVAlt-0002T2-R8 for kernelnewbies@kernelnewbies.org; Sun, 03 May 2020 05:18:50 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8356C5C026E; Sun, 3 May 2020 05:18:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 03 May 2020 05:18:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=iPMpuRkMLKEUpFHGRGiBGQPJfJH 65eClsAf+pMYwHY0=; b=pZdvlcICZJFUB6bgR6r5A8BA5Jl6rrlYKwG5C9lQb1k hjrGTDVe7lU0kSQO65UDciMnE8+VF1VIb8chXspWyRdHETTds118RetpCutxXZdr 7l1pc3dJWn63Xszy5pfKVLjq5jZ1G3seXJcUtjBGl/FxMM4DxJLl1xkkWhu6KxM/ avQ9V3LdZF6pY/zpQC/TXxDepgefyzor1SFBCQchWKaBoctHw6Wx5Do62Pt4z+3C jFfrNhhKpvVYS+zTsc49s+qcFH3P82mVLowwu1Emzt1Gm1Cjygttw//sUhumDlNM QSQ0ivGgcHT5AST+6Hg93ORj7T8iN8xRtYDR65kcfyA== 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=iPMpuR kMLKEUpFHGRGiBGQPJfJH65eClsAf+pMYwHY0=; b=S3+1rMQ4aPIkCPYCbQcF/I suwAeb+rLjnRjeLHVICDM6CP2hYb+twm9BunDqc7HkxIRa/jPGp+lwWc/laJjbtk c4VJmli8PijMvzkzofdRdFmNih0nUYAcfcXAmpZVIhOC2FuWiF4mxlL6PgDeHYGw S29hyM0iO9unoI5c2WxoZiPG4haU4er3GjwiyyYPzkZfxaSV6L1T8OnCj18Ulf5s JxPT5vKrEjcR44rr5PWnIZ4keOMCX4Z3KL/iuzftnyz6Bak+5hLfuOF8WlTNDZv7 3+8HYQu9gNBSl6VkbbbpR5m/w3sNJI1cLXLA6j0xdoCWoB5j5DlXuA2CP8tkEr+w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrjedvgdduhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecukfhppeekfedr keeirdekledruddtjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id CB6D73280068; Sun, 3 May 2020 05:18:46 -0400 (EDT) Date: Sun, 3 May 2020 11:18:45 +0200 From: Greg KH To: Jeffrey Walton Subject: Re: SElinux and its own error code? Message-ID: <20200503091845.GA569162@kroah.com> References: <167275.1588492242@turing-police> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: Valdis =?utf-8?Q?Kl=C4=93tnieks?= , kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Sun, May 03, 2020 at 03:59:22AM -0400, Jeffrey Walton wrote: > > Among other things, it means that programs potentially have to have > > special-casing in the error handlers, which are *already* code that doesn't > > get fully tested in most cases. > > Why is that a bad thing? The goal is to not break existing userspace programs. If the kernel started making up new error numbers for every new way it comes up with preventing you from doing something, userspace programs would not like that at all. > SElinux is an addon. I have no problem checking for seerrno or ESEPERM > for its specific errors. And do you want to check for all of the other different security models that Valdis listed? What about the 10 new ones that are coming in the next 2 years? After that? All that matters to your program is you were not allowed access to that resource, it doesn't matter what type of kernel feature/option caused that to happen. thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies