public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390/syscalls: Fix out of bounds arguments access
Date: Tue, 04 Jul 2017 05:05:13 +0000	[thread overview]
Message-ID: <20170704070513.59afca22@mschwideX1> (raw)
In-Reply-To: <20170703152022.GB16010@krava>

On Mon, 3 Jul 2017 17:20:22 +0200
Jiri Olsa <jolsa@redhat.com> wrote:

> On Mon, Jul 03, 2017 at 04:29:37PM +0200, Martin Schwidefsky wrote:
> 
> SNIP
> 
> > > ---
> > >  arch/s390/include/asm/syscall.h | 10 +++++++++-
> > >  1 file changed, 9 insertions(+), 1 deletion(-)  
> > 
> > There are callers of syscall_get_arguments with n=0. And it makes
> > sense to check for this case in the function instead of forcing all
> > callers to check for it.
> >    
> > > diff --git a/arch/s390/include/asm/syscall.h b/arch/s390/include/asm/syscall.h
> > > index 6ba0bf928909..5f7c11c932fa 100644
> > > --- a/arch/s390/include/asm/syscall.h
> > > +++ b/arch/s390/include/asm/syscall.h
> > > @@ -64,14 +64,22 @@ static inline void syscall_get_arguments(struct task_struct *task,
> > >  {
> > >  	unsigned long mask = -1UL;
> > > 
> > > +	/*
> > > +	 * No arguments for this syscall, there's nothing to do.
> > > +	 */
> > > +	if (!n)
> > > +		return;
> > > +
> > >  	BUG_ON(i + n > 6);  
> > 
> > So yes, for this part of the patch.
> >   
> > >  #ifdef CONFIG_COMPAT
> > >  	if (test_tsk_thread_flag(task, TIF_31BIT))
> > >  		mask = 0xffffffff;
> > >  #endif
> > > -	while (n-- > 0)
> > > +	while (n-- > 0) {
> > >  		if (i + n > 0)
> > >  			args[n] = regs->gprs[2 + i + n] & mask;
> > > +	}
> > > +
> > >  	if (i == 0)
> > >  		args[0] = regs->orig_gpr2 & mask;
> > >  }  
> > 
> > But why the unrelated whitespace damage with the additional { } ?  
> 
> I always get shouted at when I'm not using { } in conditions/loops
> having more than 1 line.. so I tend to add them when I see this
> breakage ;-)

I agree that there should have been { } with the initial patch.
It is just that the cleanup is unrelated to the true bug fix

> feel free to imot that or let me know and I'll send v2

I will strip that part and add a Cc: stable. Thanks.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

       reply	other threads:[~2017-07-04  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170703152022.GB16010@krava>
2017-07-04  5:05 ` Martin Schwidefsky [this message]
2017-06-29  9:38 [PATCH] s390/syscalls: Fix out of bounds arguments access Jiri Olsa

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=20170704070513.59afca22@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --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