From: Brendan Higgins <brendanhiggins@google.com>
To: David Gow <davidgow@google.com>
Cc: Petr Mladek <pmladek@suse.com>,
Shuah Khan <skhan@linuxfoundation.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] kunit: tool: Force the use of the 'tty' console for UML
Date: Sun, 27 Dec 2020 12:00:19 -0800 [thread overview]
Message-ID: <CAFd5g45i-x5itqnLQe1tikSVsycF8HZcJiiKiJ-SRo4D7b9dxQ@mail.gmail.com> (raw)
In-Reply-To: <20201222073900.3490607-1-davidgow@google.com>
On Mon, Dec 21, 2020 at 11:39 PM David Gow <davidgow@google.com> wrote:
>
> kunit_tool relies on the UML console outputting printk() output to the
> tty in order to get results. Since the default console driver could
> change, pass 'console=tty' to the kernel.
>
> This is triggered by a change[1] to use ttynull as a fallback console
> driver which -- by chance or by design -- seems to have changed the
> default console output on UML, breaking kunit_tool. While this may be
> fixed, we should be less fragile to such changes in the default.
>
> [1]:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=757055ae8dedf5333af17b3b5b4b70ba9bc9da4e
>
> Signed-off-by: David Gow <davidgow@google.com>
> Fixes: 757055ae8ded ("init/console: Use ttynull as a fallback when there is no console")
Acked-by: Brendan Higgins <brendanhiggins@google.com>
Thanks for taking care of this!
prev parent reply other threads:[~2020-12-27 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 7:39 [PATCH] kunit: tool: Force the use of the 'tty' console for UML David Gow
2020-12-22 11:11 ` Andy Shevchenko
2021-01-04 16:23 ` Shuah Khan
2021-01-05 16:21 ` Petr Mladek
2021-01-05 16:34 ` Shuah Khan
2021-01-05 18:57 ` Andy Shevchenko
2021-01-05 19:52 ` Shuah Khan
2021-01-06 4:29 ` David Gow
2021-01-07 16:53 ` Petr Mladek
2021-01-07 18:13 ` Shuah Khan
2020-12-27 20:00 ` Brendan Higgins [this message]
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=CAFd5g45i-x5itqnLQe1tikSVsycF8HZcJiiKiJ-SRo4D7b9dxQ@mail.gmail.com \
--to=brendanhiggins@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pmladek@suse.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;
as well as URLs for NNTP newsgroup(s).