[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a3uYZNP+C5MHS1nbo4-j1Azr472RrDivwbiL+yWisYJRQ@mail.gmail.com>
Date: Wed, 6 Sep 2017 15:02:44 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Martin Wilck <mwilck@...e.com>
Cc: Christoph Hellwig <hch@....de>,
Keith Busch <keith.busch@...el.com>,
Sagi Grimberg <sagi@...mberg.me>,
Johannes Thumshirn <jthumshirn@...e.de>,
Hannes Reinecke <hare@...e.de>, linux-nvme@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] string.h: un-fortify memcpy_and_pad
On Tue, Sep 5, 2017 at 9:26 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Tue, Sep 5, 2017 at 8:23 PM, Martin Wilck <mwilck@...e.com> 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 fortification. So simplify the code
>> by dropping fortification support for now.
>>
>> Fixes: 3c5fa8cd18f8 "string.h: add memcpy_and_pad()"
>> Signed-off-by: Martin Wilck <mwilck@...e.com>
>
> Looks good to me,
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
>
> I've added this to my randconfig testing tree, if you don't hear anything
> from me by tomorrow, you can assume that it caused no other failures.
build-tested successfully.
Tested-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists