[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ad6c3a9-b983-46a5-fc95-f961b636d3fe@gmail.com>
Date: Tue, 29 Jun 2021 05:14:16 +1200
From: Michael Schmitz <schmitzmic@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-arch <linux-arch@...r.kernel.org>,
Jens Axboe <axboe@...nel.dk>, Oleg Nesterov <oleg@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Richard Henderson <rth@...ddle.net>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Matt Turner <mattst88@...il.com>,
alpha <linux-alpha@...r.kernel.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Arnd Bergmann <arnd@...nel.org>, Tejun Heo <tj@...nel.org>,
Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH 0/9] Refactoring exit
Hi Geert,
Am 28.06.2021 um 19:31 schrieb Geert Uytterhoeven:
>> 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.
OK; you take the cake. That ramdisk came to mind when I thought about
where I'd last seen bdflush, but I've not used it in ages (not sure 14
MB are enough for that).
The question then is - will bdflush fail gracefully, or spin retrying
the syscall?
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
Powered by blists - more mailing lists