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=-6.6 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 CF943C43387 for ; Fri, 18 Jan 2019 16:11:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9796B20896 for ; Fri, 18 Jan 2019 16:11:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547827861; bh=xQPBemzCdByIu+2uZhQ+3Eoi9e/6KBjeikyjr/EppZo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=MFXsTCjGMtGj3a6k/eC1l2o/XgkgzcJSveJH6LWwR9+UgXIozHzCclqLDOtwfFvWz zKf9RN3Y1RtSt692XWpJOLNtgrjDEu0WlTLnxjXfANNujtT2dtLBf2qGMpabpVgGCx qdE5z4mS0JFqG200OdM3FsC1xljLmFLmoRF9AAQs= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727490AbfARQLB (ORCPT ); Fri, 18 Jan 2019 11:11:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:54488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727241AbfARQLB (ORCPT ); Fri, 18 Jan 2019 11:11:01 -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 0ED662086D; Fri, 18 Jan 2019 16:10:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547827860; bh=xQPBemzCdByIu+2uZhQ+3Eoi9e/6KBjeikyjr/EppZo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=a7SrJKxpMdva1ok0RkKT4GOQ12nJkcfZ5MF7119kOphr/Y4iUIxFovrr6FYc6zdv6 QUPt38qkMVyS9cp88nJTm3qYPUxkdN+UDZCUlTp0YiQGXvoEQqFoN5KhzYK8W/ccuN Vm5pXkAuYmfk0IbLGotxnuz286TidDtKcRbl9b7M= Date: Fri, 18 Jan 2019 17:10:58 +0100 From: Greg KH To: Gwendal Grignou Cc: stable@vger.kernel.org, groeck@chromium.org, keescook@chromium.org Subject: Re: [PATCH v2] proc: Remove empty line in /proc/self/status Message-ID: <20190118161058.GG11503@kroah.com> References: <20190114181336.74501-1-gwendal@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190114181336.74501-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 Mon, Jan 14, 2019 at 10:13:36AM -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] > > Fixes: 84964fa3e5a0 ("proc: Provide details on speculation flaw mitigations") > > Signed-off-by: Gwendal Grignou > --- > v2: Format commit message properly with proper subject and fixes > keyword. > > fs/proc/array.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Now applied, thanks. greg k-h