All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: Jeremy Linton <jeremy.linton@arm.com>,
	stable@vger.kernel.org,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Request to backport "Documentation: Document arm64 kpti control"
Date: Mon, 27 Jan 2020 10:47:53 -0800	[thread overview]
Message-ID: <406719bd-1d6f-d19e-fae4-4da3f0f76138@gmail.com> (raw)
In-Reply-To: <20200127155106.GA668073@kroah.com>

On 1/27/20 7:51 AM, Greg Kroah-Hartman wrote:
> On Sun, Jan 26, 2020 at 08:52:33AM -0500, Sasha Levin wrote:
>> On Sat, Jan 25, 2020 at 08:03:25PM -0800, Florian Fainelli wrote:
>>> Hi Greg, Sasha,
>>>
>>> Could you backport upstream commit
>>> de19055564c8f8f9d366f8db3395836da0b2176c ("Documentation: Document arm64
>>> kpti control") to the stable 4.9, 4.14 and 4.19 kernels since they all
>>> support the command line parameter.
>>
>> Hey Florian,
>>
>> We don't normally take documentation patches into stable trees.
> 
> Normally we do not, but this is simple enough I've queued it up for 4.19
> and 4.14.  Are you sure it is ok for 4.9?  If so, Florian, can you
> provide a backported version of it?

Yes, I am positive this parameter is relevant for the stable-4.9 tree, too:

git show linux-stable/linux-4.9.y

static int __init parse_kpti(char *str)
{
        bool enabled;
        int ret = strtobool(str, &enabled);

        if (ret)
                return ret;

        __kpti_forced = enabled ? 1 : -1;
        return 0;
}
early_param("kpti", parse_kpti);

I will be sending you a targeted patch in a short while.
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	stable@vger.kernel.org, Jeremy Linton <jeremy.linton@arm.com>
Subject: Re: Request to backport "Documentation: Document arm64 kpti control"
Date: Mon, 27 Jan 2020 10:47:53 -0800	[thread overview]
Message-ID: <406719bd-1d6f-d19e-fae4-4da3f0f76138@gmail.com> (raw)
In-Reply-To: <20200127155106.GA668073@kroah.com>

On 1/27/20 7:51 AM, Greg Kroah-Hartman wrote:
> On Sun, Jan 26, 2020 at 08:52:33AM -0500, Sasha Levin wrote:
>> On Sat, Jan 25, 2020 at 08:03:25PM -0800, Florian Fainelli wrote:
>>> Hi Greg, Sasha,
>>>
>>> Could you backport upstream commit
>>> de19055564c8f8f9d366f8db3395836da0b2176c ("Documentation: Document arm64
>>> kpti control") to the stable 4.9, 4.14 and 4.19 kernels since they all
>>> support the command line parameter.
>>
>> Hey Florian,
>>
>> We don't normally take documentation patches into stable trees.
> 
> Normally we do not, but this is simple enough I've queued it up for 4.19
> and 4.14.  Are you sure it is ok for 4.9?  If so, Florian, can you
> provide a backported version of it?

Yes, I am positive this parameter is relevant for the stable-4.9 tree, too:

git show linux-stable/linux-4.9.y

static int __init parse_kpti(char *str)
{
        bool enabled;
        int ret = strtobool(str, &enabled);

        if (ret)
                return ret;

        __kpti_forced = enabled ? 1 : -1;
        return 0;
}
early_param("kpti", parse_kpti);

I will be sending you a targeted patch in a short while.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-01-27 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-26  4:03 Request to backport "Documentation: Document arm64 kpti control" Florian Fainelli
2020-01-26  4:03 ` Florian Fainelli
2020-01-26 13:52 ` Sasha Levin
2020-01-26 13:52   ` Sasha Levin
2020-01-27 15:51   ` Greg Kroah-Hartman
2020-01-27 15:51     ` Greg Kroah-Hartman
2020-01-27 18:47     ` Florian Fainelli [this message]
2020-01-27 18:47       ` Florian Fainelli
2020-01-29 19:16     ` Sasha Levin
2020-01-29 19:16       ` Sasha Levin
2020-01-31  3:33       ` Florian Fainelli
2020-01-31  3:33         ` Florian Fainelli

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=406719bd-1d6f-d19e-fae4-4da3f0f76138@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.linton@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sashal@kernel.org \
    --cc=stable@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 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.