Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3650076pxv; Mon, 28 Jun 2021 09:23:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBhVR5wxsobeY0bsolZ7IdWjjZlPyUMIpl0I3OYfmdMblmBsASJ3L1a28kJuZsa2ZbWxVP X-Received: by 2002:a17:907:2bfa:: with SMTP id gv58mr25350773ejc.529.1624897385323; Mon, 28 Jun 2021 09:23:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624897385; cv=none; d=google.com; s=arc-20160816; b=OJghYecRuhed5KZvRvZ+MiAGrRgxKmAiLCMfhK5Ma+63yXpjG0VPzt7DQ72OD8+5IC sEisyVSZxR0Q9i8wMj1byhEsifKKrFioClXnvMHQU+Dmxjm+O027dnYM4kspKIskQlPX GyNz1wcVFQvaE6Ig9R9yr/cr5htzXSNWmrCDhSYesFCtpjQcFDVAUUXvFrOljgEv88a3 2qX+f9Lpkd/IiKmMiEjdxE6k/Ko7oFHPvCwNWWMzqaiSd5JgyvMOK29dIoU3KS3JrcYd SD7WLhSQ3l2cbWFPLFqLAae2Ia5esNZD0mCEfFzd8UeVNgvAk7HfG8/y9xb/uJa+sA1F /qvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:mime-version:user-agent:message-id :in-reply-to:date:references:cc:to:from; bh=g9jW7xOdEs0HuNX0nvRPjo+ueaHqREhUKQ8aOtalw5s=; b=vURDynxGK69Q/S5qRsUZtNhdUivVcD04Fx8sqEwxYubj0K7YtrMEYZUYklV/bc4Rhc idwxDaofLOVxB17bh1SIX9bIuC0oiwWwzQcpMU34XTIXuJd89jYFCFahtvfWtMy0X6Mz v3MDZ/c29dDHndRBf9wZfUxTZD8TDqpeRAitcE7+dgZk+yLN6lKI+GjaSoIou9ZPMKGG ie1PwQSYnyW5aBefn+i+b+DDbZ9calewc5DCGQeMFCTIpNqN4huk5ObMkPRpwt2AUcdl eBvc2nY4Hy0kMn6WIW/aVuWp1KFxni3zfqNnAviRKi4LahkIw56xvc4vNwjnRGpyXe31 OWSA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id by25si13665103ejc.235.2021.06.28.09.22.41; Mon, 28 Jun 2021 09:23:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233450AbhF1QXH (ORCPT + 99 others); Mon, 28 Jun 2021 12:23:07 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:44410 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233368AbhF1QXG (ORCPT ); Mon, 28 Jun 2021 12:23:06 -0400 Received: from in02.mta.xmission.com ([166.70.13.52]) by out02.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1lxtzw-005KQR-Lg; Mon, 28 Jun 2021 10:20:36 -0600 Received: from ip68-227-160-95.om.om.cox.net ([68.227.160.95]:35662 helo=email.xmission.com) by in02.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1lxtzu-00FZAh-9G; Mon, 28 Jun 2021 10:20:36 -0600 From: ebiederm@xmission.com (Eric W. Biederman) To: Geert Uytterhoeven Cc: Michael Schmitz , Al Viro , Linus Torvalds , linux-arch , Jens Axboe , Oleg Nesterov , Linux Kernel Mailing List , Richard Henderson , Ivan Kokshaysky , Matt Turner , alpha , linux-m68k , Arnd Bergmann , Tejun Heo , Kees Cook References: <87a6njf0ia.fsf@disp2133> <87tulpbp19.fsf@disp2133> <87zgvgabw1.fsf@disp2133> <875yy3850g.fsf_-_@disp2133> <6e283d24-7121-ae7c-d5ad-558f85858a09@gmail.com> Date: Mon, 28 Jun 2021 11:20:03 -0500 In-Reply-To: (Geert Uytterhoeven's message of "Mon, 28 Jun 2021 09:31:36 +0200") Message-ID: <87pmw6yn9o.fsf@disp2133> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1lxtzu-00FZAh-9G;;;mid=<87pmw6yn9o.fsf@disp2133>;;;hst=in02.mta.xmission.com;;;ip=68.227.160.95;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1/RdRCKClJS+touOsX/B9XRKKgr5ULM6Cg= X-SA-Exim-Connect-IP: 68.227.160.95 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa03.xmission.com X-Spam-Level: * X-Spam-Status: No, score=1.3 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,T_TM2_M_HEADER_IN_MSG,XMNoVowels autolearn=disabled version=3.4.2 X-Spam-Virus: No X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * 1.5 XMNoVowels Alpha-numberic number with no vowels * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa03 1397; Body=1 Fuz1=1 Fuz2=1] X-Spam-DCC: XMission; sa03 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: *;Geert Uytterhoeven X-Spam-Relay-Country: X-Spam-Timing: total 1762 ms - load_scoreonly_sql: 0.03 (0.0%), signal_user_changed: 3.7 (0.2%), b_tie_ro: 2.5 (0.1%), parse: 1.15 (0.1%), extract_message_metadata: 21 (1.2%), get_uri_detail_list: 2.0 (0.1%), tests_pri_-1000: 24 (1.4%), tests_pri_-950: 1.39 (0.1%), tests_pri_-900: 1.23 (0.1%), tests_pri_-90: 158 (8.9%), check_bayes: 150 (8.5%), b_tokenize: 12 (0.7%), b_tok_get_all: 9 (0.5%), b_comp_prob: 3.1 (0.2%), b_tok_touch_all: 122 (6.9%), b_finish: 0.77 (0.0%), tests_pri_0: 292 (16.6%), check_dkim_signature: 0.41 (0.0%), check_dkim_adsp: 1.85 (0.1%), poll_dns_idle: 1242 (70.5%), tests_pri_10: 1.65 (0.1%), tests_pri_500: 1255 (71.2%), rewrite_mail: 0.00 (0.0%) Subject: Re: [PATCH 0/9] Refactoring exit X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Geert Uytterhoeven writes: > Hi Michael, > > On Mon, Jun 28, 2021 at 1:00 AM Michael Schmitz wrote: >> On 28/06/21 10:13 am, Al Viro wrote: >> > On Thu, Jun 24, 2021 at 10:45:23PM +0000, Al Viro wrote: >> > >> >> 13) there's bdflush(1, whatever), which is equivalent to exit(0). >> >> IMO it's long past the time to simply remove the sucker. >> > Incidentally, calling that from ptraced process on alpha leads to >> > the same headache for tracer. _If_ we leave it around, this is >> > another candidate for "hit yourself with that special signal" - >> > both alpha and m68k have that syscall, and IMO adding an asm >> > wrapper for that one is over the top. >> > >> > Said that, we really ought to bury that thing: >> > >> > commit 2f268ee88abb33968501a44368db55c63adaad40 >> > Author: Andrew Morton >> > Date: Sat Dec 14 03:16:29 2002 -0800 >> > >> > [PATCH] deprecate use of bdflush() >> > >> > Patch from Robert Love >> > >> > We can never get rid of it if we do not deprecate it - so do so and >> > print a stern warning to those who still run bdflush daemons. >> > >> > Deprecated for 18.5 years by now - I seriously suspect that we have >> > some contributors younger than that... >> >> Haven't found that warning in over 7 years' worth of console logs, and >> I'm a good candidate for running the oldest userland in existence for m68k. >> >> Time to let it go. > > The warning is printed when using filesys-ELF-2.0.x-1400K-2.gz, > which is a very old ramdisk from right after the m68k a.out to ELF > transition: > > warning: process `update' used the obsolete bdflush system call > Fix your initscripts? > > I still boot it, once in a while. The only thing left in bdflush is func == 1 calls do_exit(0); Which is a hack introduced in 2.3.23 aka October of 1999 to force the userspace process calling bdflush to exit, instead of repeatedly calling sys_bdflush. Can you try deleting that func == 1 call and seeing if your old ramdisk works? I suspect userspace used to get into a tight spin calling bdflush func == 1, when that function stopped doing anything. That was back in 1999 so we are probably safe with out it. Eric