Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Subject: Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 20 Dec 2018 12:38:33 -0800
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, David Rientjes <rientjes@xxxxxxxxxx>, Alexey Dobriyan <adobriyan@xxxxxxxxx>
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@xxxxxxxxxxxx> 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.

Follow-Ups:
- Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
  - From: Alexey Dobriyan

References:
- [PATCH 0/2] procfs: /proc/PID/comm fixes
  - From: Michał Mirosław
- [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
  - From: Michał Mirosław

Prev by Date: RE: Recent VFS/LSM patches cause Kernel panic - not syncing: Can't create rootfs
Next by Date: Re: [PATCH] iomap: Revert "fs/iomap.c: get/put the page in iomap_page_create/release()"
Previous by thread: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
Next by thread: Re: [PATCH 1/2] procfs: signal /proc/PID/comm write truncation
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux