From: Petr Mladek <pmladek@suse.com>
To: David Gow <davidgow@google.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>,
linux-um <linux-um@lists.infradead.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Guenter Roeck <linux@roeck-us.net>,
KUnit Development <kunit-dev@googlegroups.com>
Subject: Re: kunit stopped working
Date: Tue, 5 Jan 2021 17:17:07 +0100 [thread overview]
Message-ID: <X/SRA1P8t+ONZFKb@alley> (raw)
In-Reply-To: <CABVgOS=tz-611qhrn-pcgokyJeS_NStfxPRBnT60KpPhBVPGpA@mail.gmail.com>
On Tue 2020-12-22 09:43:48, David Gow wrote:
> On Tue, Dec 22, 2020 at 4:02 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Mon, Dec 21, 2020 at 09:40:08PM +0200, Andy Shevchenko wrote:
> > > +Cc people from culprit commit
> >
> > Guys, revert helps. I am open to test any solution you may propose, thanks!
> >
> > ...
> >
> > > # first bad commit: [757055ae8dedf5333af17b3b5b4b70ba9bc9da4e] init/console: Use ttynull as a fallback when there is no console
> >
> > --
>
> +CC linux-um
>
> There appear to be two problems here:
> 1. UML now no longer has console output by default (which KUnit needs
> to get results)
> This can be worked around for KUnit by passing console=tty to the
> kernel. I don't think this is a "correct" fix
It is rather a workaround. ttynull was supposed to be an ultimate
fallback to provide a "valid" stdin, stdout, and stderr for
the init process. ttyX still should be used by default when
there is no console defined on the command line.
So the question is why ttyX was not registered with this patch.
I see the problem even when I revert the commit
757055ae8dedf5333af ("init/console: Use ttynull as a fallback when
there is no console") and enable the ttynull driver as built in:
CONFIG_NULL_TTY=y
By other words, the problem existed even before. The commit only
made it visible by default.
I am still trying to understand arch/um and kunit code. I wonder
if it is somehow related to stdiocons implemented in
arch/um/drivers/stdio_console.c.
Best Regards,
Petr
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-01-05 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201221144302.GR4077@smile.fi.intel.com>
[not found] ` <20201221144510.GS4077@smile.fi.intel.com>
[not found] ` <2d4b8148-48ca-290f-1d66-33e302e7571d@linuxfoundation.org>
[not found] ` <20201221192757.GZ4077@smile.fi.intel.com>
[not found] ` <20201221194008.GA4077@smile.fi.intel.com>
[not found] ` <20201221200332.GB4077@smile.fi.intel.com>
2020-12-22 1:43 ` kunit stopped working David Gow
2020-12-22 7:26 ` David Gow
2020-12-22 13:34 ` Andy Shevchenko
2020-12-27 19:58 ` Brendan Higgins
2021-01-05 16:17 ` Petr Mladek [this message]
2021-01-05 16:49 ` Petr Mladek
2021-01-06 4:04 ` Sergey Senozhatsky
2021-01-06 13:10 ` Petr Mladek
2021-01-07 7:15 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X/SRA1P8t+ONZFKb@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox