public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] ecryptfs: re-order a condition for static checkers
Date: Tue, 29 Jan 2019 22:37:35 +0000	[thread overview]
Message-ID: <20190129223734.GB29425@lindsey> (raw)

On 2018-12-14 14:51:13, Dan Carpenter wrote:
> Can we merge this patch?  KASAN will probably complain about this as
> well, I think...

Yes, my apologies for the way too long delay. I just noticed that
there's another commit of yours that I left sitting in the ecryptfs next
branch from last year and never pushed it up. I'll get both commits in
and will return to keeping a better eye on ecryptfs submissions.

Thanks!

Tyler

> 
> regards,
> dan carpenter
> 
> On Wed, Aug 22, 2018 at 01:43:59PM +0300, Dan Carpenter wrote:
> > Static checkers complain that we are using "s->i" as an offset before
> > we check whether it is within bounds.  It doesn't matter much but we
> > can easily swap the order of the checks to make everyone happy.
> > 
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > 
> > diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
> > index e74fe84d0886..624ff4409c61 100644
> > --- a/fs/ecryptfs/keystore.c
> > +++ b/fs/ecryptfs/keystore.c
> > @@ -1063,8 +1063,9 @@ ecryptfs_parse_tag_70_packet(char **filename, size_t *filename_size,
> >  		       "rc = [%d]\n", __func__, rc);
> >  		goto out_free_unlock;
> >  	}
> > -	while (s->decrypted_filename[s->i] != '\0'
> > -	       && s->i < s->block_aligned_filename_size)
> > +
> > +	while (s->i < s->block_aligned_filename_size &&
> > +	       s->decrypted_filename[s->i] != '\0')
> >  		s->i++;
> >  	if (s->i = s->block_aligned_filename_size) {
> >  		printk(KERN_WARNING "%s: Invalid tag 70 packet; could not "

             reply	other threads:[~2019-01-29 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 22:37 Tyler Hicks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-14 11:51 [PATCH] ecryptfs: re-order a condition for static checkers Dan Carpenter
2018-08-22 10:43 Dan Carpenter

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=20190129223734.GB29425@lindsey \
    --to=tyhicks@canonical.com \
    --cc=kernel-janitors@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