linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karsten Graul <kgraul@linux.ibm.com>
To: Kees Cook <keescook@chromium.org>, Heiko Carstens <hca@linux.ibm.com>
Cc: Julian Wiedmann <jwi@linux.ibm.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] s390: iucv: Avoid field over-reading memcpy()
Date: Tue, 29 Jun 2021 17:19:50 +0200	[thread overview]
Message-ID: <614191b7-6b5f-75f3-7490-62505970ceb5@linux.ibm.com> (raw)
In-Reply-To: <20210616201942.1246211-1-keescook@chromium.org>

On 16/06/2021 22:19, Kees Cook wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memcpy(), memmove(), and memset(), avoid
> intentionally reading across neighboring array fields.
> 
> Add a wrapping struct to serve as the memcpy() source so the compiler
> can perform appropriate bounds checking, avoiding this future warning:
> 
> In function '__fortify_memcpy',
>     inlined from 'iucv_message_pending' at net/iucv/iucv.c:1663:4:
> ./include/linux/fortify-string.h:246:4: error: call to '__read_overflow2_field' declared with attribute error: detected read beyond size of field (2nd parameter)
> 
> Signed-off-by: Kees Cook <keescook@chromium.org>

Looks good, thanks for taking care of that change.

Acked-by: Karsten Graul <kgraul@linux.ibm.com>

> ---
>  net/iucv/iucv.c | 22 ++++++++++++----------
>  1 file changed, 12 insertions(+), 10 deletions(-)
> 
> diff --git a/net/iucv/iucv.c b/net/iucv/iucv.c
> index 349c6ac3313f..e6795d5a546a 100644
> --- a/net/iucv/iucv.c
> +++ b/net/iucv/iucv.c
> @@ -1635,14 +1635,16 @@ struct iucv_message_pending {
>  	u8  iptype;
>  	u32 ipmsgid;
>  	u32 iptrgcls;
> -	union {
> -		u32 iprmmsg1_u32;
> -		u8  iprmmsg1[4];
> -	} ln1msg1;
> -	union {
> -		u32 ipbfln1f;
> -		u8  iprmmsg2[4];
> -	} ln1msg2;
> +	struct {
> +		union {
> +			u32 iprmmsg1_u32;
> +			u8  iprmmsg1[4];
> +		} ln1msg1;
> +		union {
> +			u32 ipbfln1f;
> +			u8  iprmmsg2[4];
> +		} ln1msg2;
> +	} rmmsg;
>  	u32 res1[3];
>  	u32 ipbfln2f;
>  	u8  ippollfg;
> @@ -1660,10 +1662,10 @@ static void iucv_message_pending(struct iucv_irq_data *data)
>  		msg.id = imp->ipmsgid;
>  		msg.class = imp->iptrgcls;
>  		if (imp->ipflags1 & IUCV_IPRMDATA) {
> -			memcpy(msg.rmmsg, imp->ln1msg1.iprmmsg1, 8);
> +			memcpy(msg.rmmsg, &imp->rmmsg, 8);
>  			msg.length = 8;
>  		} else
> -			msg.length = imp->ln1msg2.ipbfln1f;
> +			msg.length = imp->rmmsg.ln1msg2.ipbfln1f;
>  		msg.reply_size = imp->ipbfln2f;
>  		path->handler->message_pending(path, &msg);
>  	}
> 

-- 
Karsten

(I'm a dude)

      parent reply	other threads:[~2021-06-29 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 20:19 [PATCH] s390: iucv: Avoid field over-reading memcpy() Kees Cook
2021-06-29 14:25 ` Heiko Carstens
2021-06-29 15:19 ` Karsten Graul [this message]

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=614191b7-6b5f-75f3-7490-62505970ceb5@linux.ibm.com \
    --to=kgraul@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=hca@linux.ibm.com \
    --cc=jwi@linux.ibm.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).