From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89421C43387 for ; Sat, 12 Jan 2019 08:01:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5418D205F4 for ; Sat, 12 Jan 2019 08:01:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547280089; bh=uL9Gv0wIsynZiTs0HsmGLztNH9dCho/XY7rslNR8gOY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Yt40emu4dUXxBYO70AAAWBaDobfEjag92iXDxKuht6M2qCYXxXR3m6yV8ywl3SxD1 AN4O2TkA7ewCNaFGiN0nhHPRdjGPMYj96CXNCNaFhXN+mYtyeaOsqkPzCY34+Kjgnn ayiyUA4yF+STBKtThd6fxZ/7kWZmUpiyr7cSvoAw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725819AbfALIB2 (ORCPT ); Sat, 12 Jan 2019 03:01:28 -0500 Received: from mail.kernel.org ([198.145.29.99]:35700 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725372AbfALIB2 (ORCPT ); Sat, 12 Jan 2019 03:01:28 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8306A205F4; Sat, 12 Jan 2019 08:01:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547280088; bh=uL9Gv0wIsynZiTs0HsmGLztNH9dCho/XY7rslNR8gOY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jgChRe5zwbMaoAzNZVrIWkPCksc7k4GLtHN+8i8IG/N8CL8AYZaBc616s7GrKB6f5 OueNuxCoc4fMo4H1MedMWd+qJ7t1QczAY/buFr8Wu8JRvvbi9P3jE5PNc/uJNqgpf1 +09xHKKbjwMLbOmCaUjQebasC4GYRSRKhPjLGV/0= Date: Sat, 12 Jan 2019 09:01:25 +0100 From: Greg KH To: Gwendal Grignou Cc: stable@vger.kernel.org, groeck@chromium.org, keescook@chromium.org Subject: Re: [PATCH] FIXUP: proc: Provide details on speculation flaw mitigations Message-ID: <20190112080125.GA17489@kroah.com> References: <20190112003212.103301-1-gwendal@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190112003212.103301-1-gwendal@chromium.org> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Jan 11, 2019 at 04:32:12PM -0800, Gwendal Grignou wrote: > Prevent an empty line in /proc/self/status, allow iotop to work. > > iotop does not like empty lines, fails with: > File "/usr/local/lib64/python2.7/site-packages/iotop/data.py", line > 196, in parse_proc_pid_status > key, value = line.split(':\t', 1) > ValueError: need more than 1 value to unpack > > [reading /proc/self/status] > > Signed-off-by: Gwendal Grignou > --- > fs/proc/array.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Why send this to me? Always use scripts/get_maintainer.pl on a patch to determine who and what lists to send patches to. And is this a new bug? What commit caused this? thanks, greg k-h