mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Kees Cook <keescook@chromium.org>
Cc: Wenjia Zhang <wenjia@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] s390/qeth: Split memcpy() of struct qeth_ipacmd_addr_change flexible array
Date: Tue, 27 Sep 2022 13:54:27 +0200	[thread overview]
Message-ID: <23b905f8-2836-8879-fe9f-9521e0f8674e@linux.ibm.com> (raw)
In-Reply-To: <YzJO0f7v7N4Z+9Dk@work>



On 27.09.22 03:16, Gustavo A. R. Silva wrote:
> On Mon, Sep 26, 2022 at 05:39:53PM -0700, Kees Cook wrote:
>> To work around a misbehavior of the compiler's ability to see into
>> composite flexible array structs (as detailed in the coming memcpy()
>> hardening series[1]), split the memcpy() of the header and the payload
>> so no false positive run-time overflow warning will be generated.
>>
>> [1] https://lore.kernel.org/linux-hardening/20220901065914.1417829-2-keescook@chromium.org/
>>
>> Cc: Alexandra Winter <wintera@linux.ibm.com>
>> Cc: Wenjia Zhang <wenjia@linux.ibm.com>
>> Cc: Heiko Carstens <hca@linux.ibm.com>
>> Cc: Vasily Gorbik <gor@linux.ibm.com>
>> Cc: Alexander Gordeev <agordeev@linux.ibm.com>
>> Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
>> Cc: Sven Schnelle <svens@linux.ibm.com>
>> Cc: linux-s390@vger.kernel.org
>> Cc: netdev@vger.kernel.org
>> Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> 
> Thanks!
> --
> Gustavo
> 
Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>

Thank you
Alexandra
>> ---
>>  drivers/s390/net/qeth_l2_main.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/s390/net/qeth_l2_main.c b/drivers/s390/net/qeth_l2_main.c
>> index 2d4436cbcb47..0ce635b7b472 100644
>> --- a/drivers/s390/net/qeth_l2_main.c
>> +++ b/drivers/s390/net/qeth_l2_main.c
>> @@ -1530,8 +1530,8 @@ static void qeth_addr_change_event(struct qeth_card *card,
>>  	else
>>  		INIT_DELAYED_WORK(&data->dwork, qeth_l2_dev2br_worker);
>>  	data->card = card;
>> -	memcpy(&data->ac_event, hostevs,
>> -			sizeof(struct qeth_ipacmd_addr_change) + extrasize);
>> +	data->ac_event = *hostevs;
>> +	memcpy(data->ac_event.entry, hostevs->entry, extrasize);
>>  	queue_delayed_work(card->event_wq, &data->dwork, 0);
>>  }
>>  
>> -- 
>> 2.34.1
>>

  reply	other threads:[~2022-09-27 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  0:39 Kees Cook
2022-09-27  1:16 ` Gustavo A. R. Silva
2022-09-27 11:54   ` Alexandra Winter [this message]
2022-09-28  2:00 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23b905f8-2836-8879-fe9f-9521e0f8674e@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=gustavoars@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=wenjia@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®