linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Capella <sebastian.capella@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org,
	patches@linaro.org, Joe Perches <joe@perches.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Michel Lespinasse <walken@google.com>,
	Shaohua Li <shli@kernel.org>,
	Jerome Marchand <jmarchan@redhat.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v5 1/2] mm: add kstrimdup function
Date: Thu, 30 Jan 2014 13:45:45 -0800	[thread overview]
Message-ID: <20140130214545.18296.69349@capellas-linux> (raw)
In-Reply-To: <20140130132251.4f662aeddc09d8410dee4490@linux-foundation.org>

Quoting Andrew Morton (2014-01-30 13:22:51)
> On Thu, 30 Jan 2014 13:11:57 -0800 Sebastian Capella <sebastian.capella@linaro.org> wrote:
> > +char *kstrimdup(const char *s, gfp_t gfp)
> > +{
> > +     char *buf;
> > +     char *begin = skip_spaces(s);
> > +     size_t len = strlen(begin);
> > +
> > +     while (len > 1 && isspace(begin[len - 1]))
> > +             len--;
> 
> That's off-by-one isn't it?  kstrimdup("   ") should return "", not " ".
> 
> > +     buf = kmalloc_track_caller(len + 1, gfp);
> > +     if (!buf)
> > +             return NULL;
> > +
> > +     memcpy(buf, begin, len);
> > +     buf[len] = '\0';
> > +
> > +     return buf;
> > +}

Hi Andrew,

I think this is a little tricky.

For an empty string, the function relies on skip_spaces to point begin
at the \0'.

Alternately, if we don't have an empty string, we know we have at least 1
non-space, non-null character at begin[0], and there's no need to check it,
so the loop stops at [1].  If there's a space at 1, we just put the '\0'
there.

We could check at [0], but I think its already been checked by skip_spaces.

I'll add a comment above the while for that

Thanks,

Sebastian


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2014-01-30 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 21:11 (unknown), Sebastian Capella
2014-01-30 21:11 ` [PATCH v5 1/2] mm: add kstrimdup function Sebastian Capella
2014-01-30 21:22   ` Andrew Morton
2014-01-30 21:44     ` David Rientjes
2014-01-30 21:45     ` Sebastian Capella [this message]
2014-01-30 21:51       ` Andrew Morton
2014-01-30 22:25         ` Sebastian Capella
2014-01-30 21:11 ` [PATCH v5 2/2] PM / Hibernate: use name_to_dev_t to parse resume Sebastian Capella

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=20140130214545.18296.69349@capellas-linux \
    --to=sebastian.capella@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jmarchan@redhat.com \
    --cc=joe@perches.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=patches@linaro.org \
    --cc=shli@kernel.org \
    --cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).