Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Sasha Levin <Alexander.Levin@microsoft.com>
To:     Steven Rostedt <rostedt@goodmis.org>
CC:     "stable@vger.kernel.org" <stable@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Erica Bugden <erica.bugden@linutronix.de>
Subject: Re: [PATCH AUTOSEL 4.18 037/131] ftrace: Add missing check for
 existing hwlat thread
Thread-Topic: [PATCH AUTOSEL 4.18 037/131] ftrace: Add missing check for
 existing hwlat thread
Thread-Index: AQHUQr1gBE/wJ8UrN0ygaxjXaATxC6TgV3YAgAOlLQA=
Date:   Fri, 7 Sep 2018 00:23:55 +0000
Message-ID: <20180907002353.GC16300@sasha-vm>
References: <20180902064601.183036-1-alexander.levin@microsoft.com>
 <20180902064601.183036-37-alexander.levin@microsoft.com>
 <20180904124356.4a2f3dbc@gandalf.local.home>
In-Reply-To: <20180904124356.4a2f3dbc@gandalf.local.home>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: microsoft.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <36E93CD4188AE34CA197836BEF73CA71@namprd21.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a735278-f5f8-4ebd-5e99-08d614583268
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Sep 2018 00:23:55.3000
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0168
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Sep 04, 2018 at 12:43:56PM -0400, Steven Rostedt wrote:
>On Sun, 2 Sep 2018 13:03:43 +0000
>Sasha Levin <Alexander.Levin@microsoft.com> wrote:
>
>> [
>>  Note, this only fixes the symptom. The real fix was not to call
>>  this function when tracing_on was already one. But this still makes
>>  the code more robust, so we'll add it.
>> ]
>
>This patch really didn't need to be backported (which is why I didn't
>mark it for stable), because the real fix was backported.

Out it goes, thanks!=