[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59382: cp(1) tries to allocate too much memory if filesystem blocksi
bug#59382: cp(1) tries to allocate too much memory if filesystem blocksizes are unusual
Mon, 2 Jan 2023 23:24:01 +0000
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.0
On 02/01/2023 23:18, Paul Eggert wrote:
On 2023-01-02 15:03, Pádraig Brady wrote:
On 20/11/2022 03:50, Paul Eggert wrote:
Although we inadvertently removed support for weird devices in 2009 by
commit 55efc5f3ee485b3e31a91c331f07c89aeccc4e89, and nobody seems to
care (because people use dd or whatever to deal with weird devices), I
think it'd be better to limit the fix to regular files. And while we're
at it we might as well resurrect support for weird devices.
Paul I'm happy with your patch for this.
I've rebased and tweaked the summary and NEWS slightly in the attached.
OK for me to apply?
Sure, that looks good, thanks.
I forgot about documenting the reinstated I/O block size multiple constraint,
which I'll do with the attached.
Description: Text Data