lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87fregxfcw.fsf@trenco.lwn.net>
Date: Mon, 28 Jul 2025 13:52:31 -0600
From: Jonathan Corbet <corbet@....net>
To: Štěpán Němec <stepnem@...k.net>
Cc: "Alex Xu (Hello71)" <alex_y_xu@...oo.ca>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: admin-guide: update to current minimum pipe size
 default

Štěpán Němec <stepnem@...k.net> writes:

> On Mon, 28 Jul 2025 13:07:58 -0600
> Jonathan Corbet wrote:
>
>> Štěpán Němec <stepnem@...k.net> writes:
>>
>>> Fixes: 46c4c9d1beb7 ("pipe: increase minimum default pipe size to 2 pages")
>>> Signed-off-by: Štěpán Němec <stepnem@...k.net>
>>> ---
>
> [...]
>
>> This seems like a reasonable change, but can I ask you to resubmit it
>> with a proper changelog, please?
>
> Do you mean a better/longer commit message?
>
> I felt that the Subject: and Fixes: says it all and didn't
> want to duplicate information (contained in its commit
> message and comments added by that change, as well as the
> very paragraph we're updating here).
>
> Would adding something like
>
>   The pipe size limit used when the fs.pipe-user-pages-soft
>   sysctl value is reached was increased from one to two
>   pages in commit 46c4c9d1beb7; update the documentation to
>   match the new reality.
>   
> work?

Yes, that is what I had in mind.  Patches should always explain
themselves without making people chase down Fixes tags and such.

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ