From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Misc driver fix for 5.15-rc1
Date: Sun, 12 Sep 2021 12:22:39 -0700 [thread overview]
Message-ID: <CAHk-=wiVEEzLPLTkb9U6YB-2qXpbuqP3a1q=gRx8Nkg-dpLeqw@mail.gmail.com> (raw)
In-Reply-To: <202109121213.A47D575@keescook>
On Sun, Sep 12, 2021 at 12:17 PM Kees Cook <keescook@chromium.org> wrote:
>
> This was done to deal with the various mangling of reports (i.e.
> "summaries") I've been getting from CI systems that run LKDTM.
.. and what makes LKDTM so special?
IOW, what about ALL THE OTHER REPORTS?
And no, my argument is most definitely not "ok, everything should do this".
It's the reverse. The CI systems should be the ones that are fixed,
not random messages from random places in the kernel have version
information added.
A CI report that doesn't report the version of the kernel is kind of
fundamentally broken, wouldn't you agree?
The fix is not to add the kernel version string into every single
message you print out.
Linus
next prev parent reply other threads:[~2021-09-12 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 14:03 [GIT PULL] Misc driver fix for 5.15-rc1 Greg KH
2021-09-12 19:03 ` Linus Torvalds
2021-09-12 19:17 ` Kees Cook
2021-09-12 19:22 ` Linus Torvalds [this message]
2021-09-12 19:44 ` Kees Cook
2021-09-12 19:55 ` Linus Torvalds
2021-09-12 22:26 ` Kees Cook
2021-09-12 19:16 ` pr-tracker-bot
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='CAHk-=wiVEEzLPLTkb9U6YB-2qXpbuqP3a1q=gRx8Nkg-dpLeqw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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).