Subject: Re: copystr
To: David Laight <>
From: Jason R Thorpe <>
List: tech-kern
Date: 09/03/2002 06:30:09
On Tue, Sep 03, 2002 at 11:07:56AM +0100, David Laight wrote:

 > FWIW memmove() check for overlapped copies and memcpy()
 > should not (and would be expected to copy 'forwards').

Yes, I agree.  I'm not sure why some of our memcpy's are implemented
this way, but it was always bothered me.

        -- Jason R. Thorpe <>