Re: [PATCH] string.h: un-fortify memcpy_and_pad

2017-09-11 Thread Christoph Hellwig
> Hello Stephen and Christoph, > > my broken patch 01f33c336e2d is in Linus' tree and causing compiler > warnings there. Could you please take care that this fix is pulled in > on top of it? Or should I take another action myself? string.h is a bit of a maintainers no mans land. Given that the p

Re: [PATCH] string.h: un-fortify memcpy_and_pad

2017-09-11 Thread Martin Wilck
On Wed, 2017-09-06 at 14:36 +0200, Martin Wilck wrote: > The way I'd implemented the new helper memcpy_and_pad with > __FORTIFY_INLINE caused compiler warnings for certain kernel > configurations. > > This helper is only used in a single place at this time, and thus > doesn't benefit much from fo

Re: [PATCH] string.h: un-fortify memcpy_and_pad

2017-09-06 Thread Arnd Bergmann
On Tue, Sep 5, 2017 at 9:26 PM, Arnd Bergmann wrote: > On Tue, Sep 5, 2017 at 8:23 PM, Martin Wilck wrote: >> The way I'd implemented the new helper memcpy_and_pad with >> __FORTIFY_INLINE caused compiler warnings for certain kernel >> configurations. >> >> This helper is only used in a single p

Re: [PATCH] string.h: un-fortify memcpy_and_pad

2017-09-05 Thread Arnd Bergmann
On Tue, Sep 5, 2017 at 8:23 PM, Martin Wilck wrote: > The way I'd implemented the new helper memcpy_and_pad with > __FORTIFY_INLINE caused compiler warnings for certain kernel > configurations. > > This helper is only used in a single place at this time, and thus > doesn't benefit much from forti