From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:49066 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727387AbeLTUif (ORCPT ); Thu, 20 Dec 2018 15:38:35 -0500 Date: Thu, 20 Dec 2018 12:38:33 -0800 From: Andrew Morton To: =?UTF-8?B?TWljaGHFgiBNaXJvc8WCYXc=?= Cc: linux-fsdevel@vger.kernel.org, David Rientjes , Alexey Dobriyan Subject: Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation Message-Id: <20181220123833.c7305ae124845b36bc05cff6@linux-foundation.org> In-Reply-To: <80bec689c8ce0d46ef64f0dbbee349b54dd4038c.1545261970.git.mirq-linux@rere.qmqm.pl> References: <80bec689c8ce0d46ef64f0dbbee349b54dd4038c.1545261970.git.mirq-linux@rere.qmqm.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, 20 Dec 2018 00:28:04 +0100 Michał Mirosław wrote: > Keeps truncation working, but also signals to writing process > when that happens. Please fully describe what is presently wrong with truncation. ie: describe the end-user-visible effects of a bug when fixing it. Thanks.