All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] cve/meltdown: read *saved_command_line
Date: Tue, 26 Jun 2018 07:22:53 -0400 (EDT)	[thread overview]
Message-ID: <1799109822.29007031.1530012173372.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180626093850.GE24288@rei>



----- Original Message -----
> Hi!
> Looking at kernel git the saved_command_line is allocated dynamically
> since 2.6.21 which I guess is old enough but we may as well mention this
> in the commit message:
> 
> commit 30d7e0d466b3ac0b5ef77e4062bf9385f0d72270
> Author: Alon Bar-Lev <alon.barlev@gmail.com>
> Date:   Mon Feb 12 00:53:52 2007 -0800
> 
>     [PATCH] Dynamic kernel command-line: common

I added this to commit message. It should be old enough,
we run the test on kernels older than 2.6.32 anyway.

> Other than that it looks good, acked.

Thanks, pushed.
Jan

      reply	other threads:[~2018-06-26 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 11:51 [LTP] [PATCH] cve/meltdown: read *saved_command_line Jan Stancek
2018-06-22  8:44 ` Li Wang
2018-06-26  9:38 ` Cyril Hrubis
2018-06-26 11:22   ` Jan Stancek [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=1799109822.29007031.1530012173372.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.