bug#70586: cp walks dir differently than rm and is hitting "File name too long" where this could be avoided

On 10/15/25 09:36, Collin Funk wrote:
> I'll have a look at that one too. Finding a reasonable way to define the
> sort functions in terms of 'FTSENT **' will not be very fun though.

Should be easier for ls than for cp, as fts isn't really designed for 
destinations so you'll have to traverse the destination by hand.

As you say, this is all reasonably low priority, as only buggy uses and 
attackers create file names longer than PATH_MAX (and rm is the cure for 
that...).