Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4894568ybi; Tue, 28 May 2019 04:23:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqxcyjZ5PO9M/nvNOu5Vm4/wz1p9WfmVY+Mk7B+2esDr/PddwGIaTsTkF9a6/3i50m4p6+V8 X-Received: by 2002:a17:90a:c688:: with SMTP id n8mr5253174pjt.29.1559042605394; Tue, 28 May 2019 04:23:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559042605; cv=none; d=google.com; s=arc-20160816; b=wAqYJcRFLFD+es/ESg/2pZxKYWS+jdxYfry5PE/03PN6n9+/VkQsxYA3Xk5MRzciH7 jxI6yb+8kc1fgJVySL9G5tZyQ/IP7jSLBFU/1GVoyTOSaZzsgpngroJyE0NN+sD1d7tE KHWW3mo1LaUQhiuWyNGy42wGqouMgAu3AOtPPeb3qq9kUMpNh/IsGzjCPJDKkzpnxATM M5Y0R1bANtr3eHYTvAdHC5MDTaYxTcKfzuYPYy4TXjjrHWdeYfgTTfD6v5M2Q9OmD5aH 2MzJManc/P/7antLdD8kfyBSFU9UVsLNI+nLez2Z6PrYS6GN3XwQL88uBXWihY2WBiYZ NOlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=SO8wsj1YfDQ7rCxMXE+90aZdb5g6cWtORfSJopozg5E=; b=LbNIfVNK/kCSYnkuHpdhjJGL3ygGaSPG00GdRBqQpDL0RS9GzQ0BDY7Cu6/0dmlPAH EJ8pPxP4KU4DhyS06YI0jhZAnQubhLcwZ0C8W5mHKlvKgemr74E4NlsqBbmbUiaqlSnu weO3+NK2x7MRYR77np0ArofKpQOBJsBA3srZwyHor2wxsZKCvfhXLkz3CdU8LMR7GtwD pKurLMiItbUVkGW8yeCoEKnCsE0EgKIG/gfCqd/Ii2kIgVuohJHxT1s9r4pkWCPkKEfl WHJ8FCwnV/LPhmbQqZTJyIfLPwXJneF4JDJ4OJ0Of7+xHe2E+/HQRvxPxTI1oWG9ZVM9 gAqA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p96si3745418pjp.31.2019.05.28.04.23.09; Tue, 28 May 2019 04:23:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726608AbfE1LU1 (ORCPT + 99 others); Tue, 28 May 2019 07:20:27 -0400 Received: from mx2.suse.de ([195.135.220.15]:47178 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726313AbfE1LU1 (ORCPT ); Tue, 28 May 2019 07:20:27 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BC855AE3F; Tue, 28 May 2019 11:20:24 +0000 (UTC) Date: Tue, 28 May 2019 13:20:23 +0200 From: Cyril Hrubis To: Florian Weimer Cc: Andreas Schwab , lkml , linux-alpha@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, Michal Simek , linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH] [RFC] Remove bdflush syscall stub Message-ID: <20190528112022.GA16683@rei> References: <20190528101012.11402-1-chrubis@suse.cz> <20190528104017.GA11969@rei> <87ftoyg7t3.fsf@oldenburg2.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ftoyg7t3.fsf@oldenburg2.str.redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > >> > I've tested the patch on i386. Before the patch calling bdflush() with > >> > attempt to tune a variable returned 0 and after the patch the syscall > >> > fails with EINVAL. > >> > >> Should be ENOSYS, doesn't it? > > > > My bad, the LTP syscall wrapper handles ENOSYS and produces skipped > > results based on that. > > > > EINVAL is what you get for not yet implemented syscalls, i.e. new > > syscall on old kernel. > > EINVAL? Is that a bdflush-specific thing, test-specific, or is itmore > general? > > glibc has fallback paths that test for ENOSYS only. EINVAL will be > passed to the application, skipping fallback. For missing system calls, > this is not what we want. The syscall returns ENOSYS after this change, sorry for the confusion. -- Cyril Hrubis chrubis@suse.cz