From: Andrew Morton <akpm@linux-foundation.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-fsdevel@vger.kernel.org,
David Rientjes <rientjes@google.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
Date: Thu, 20 Dec 2018 12:38:33 -0800 [thread overview]
Message-ID: <20181220123833.c7305ae124845b36bc05cff6@linux-foundation.org> (raw)
In-Reply-To: <80bec689c8ce0d46ef64f0dbbee349b54dd4038c.1545261970.git.mirq-linux@rere.qmqm.pl>
On Thu, 20 Dec 2018 00:28:04 +0100 Michał Mirosław <mirq-linux@rere.qmqm.pl> 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.
next prev parent reply other threads:[~2018-12-20 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 23:28 [PATCH 0/2] procfs: /proc/PID/comm fixes Michał Mirosław
2018-12-19 23:28 ` [PATCH 2/2] procfs: lseek(/proc/PID/comm, 0, SEEK_END) Michał Mirosław
2018-12-19 23:28 ` [PATCH 1/2] procfs: signal /proc/PID/comm write truncation Michał Mirosław
2018-12-20 20:38 ` Andrew Morton [this message]
2018-12-21 10:07 ` Alexey Dobriyan
2019-01-13 12:49 ` Michał Mirosław
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=20181220123833.c7305ae124845b36bc05cff6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rientjes@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).