From: Minchan Kim <minchan@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Michal Nazarewicz <mina86@mina86.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@suse.de>, Andy Whitcroft <apw@shadowen.org>,
Alexander Nyberg <alexn@dsv.su.se>
Subject: Re: [PATCH] Fix wrong EOF compare
Date: Fri, 11 Jan 2013 08:34:56 +0900 [thread overview]
Message-ID: <20130110233456.GB2470@blaptop> (raw)
In-Reply-To: <50EEE868.70705@infradead.org>
Hi Randy,
On Thu, Jan 10, 2013 at 08:12:24AM -0800, Randy Dunlap wrote:
> On 01/10/13 07:26, Michal Nazarewicz wrote:
> > On Thu, Jan 10 2013, Minchan Kim <minchan@kernel.org> wrote:
> >> getc returns "int" so EOF could be -1 but storing getc's return
> >> value to char directly makes the vaule to 255 so below condition
> >> is always false.
> >
> > Technically, this is implementation defined and I believe on many
> > systems char is signed thus the loop will end on EOF or byte 255.
> >
> > Either way, my point is the patch is correct, but the comment is not. ;)
>
> and change spelling of 'vaule' to 'value'
Oops. It was typo when I cooked the patch after testing in my ARM system.
> and test build it please.
Keep in mind. Thanks!
>
> >
> > Of course, even better if the function just used fgets(), ie. something
> > like:
> >
> > int read_block(char *buf, int buf_size, FILE *fin)
> > {
> > char *curr = buf, *const buf_end = buf + buf_size;
> >
> > while (buf_end - curr > 1 && fgets(curr, buf_end - curr, fin)) {
> > if (*curr == '\n') /* empty line */
> > return curr - buf;
> > curr += strlen(curr);
> > }
> >
> > return -1; /* EOF or no space left in buf. */
> > }
> >
> > which is much shorter and does not have buffer overflow issues.
> >
> >> It happens in my ARM system so loop is not ended, then segfaulted.
> >> This patch fixes it.
> >>
> >> *curr = getc(fin); // *curr = 255
> >> if (*curr == EOF) return -1; // if ( 255 == -1)
> >>
> >> Cc: Mel Gorman <mgorman@suse.de>
> >> Cc: Andy Whitcroft <apw@shadowen.org>
> >> Cc: Alexander Nyberg <alexn@dsv.su.se>
> >> Signed-off-by: Minchan Kim <minchan@kernel.org>
> >> ---
> >> Documentation/page_owner.c | 6 ++++--
> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/Documentation/page_owner.c b/Documentation/page_owner.c
> >> index f0156e1..b777fb6 100644
> >> --- a/Documentation/page_owner.c
> >> +++ b/Documentation/page_owner.c
> >> @@ -32,12 +32,14 @@ int read_block(char *buf, FILE *fin)
> >> {
> >> int ret = 0;
> >> int hit = 0;
> >> + int vaule;
> >> char *curr = buf;
> >>
> >> for (;;) {
> >> - *curr = getc(fin);
> >> - if (*curr == EOF) return -1;
> >> + value = getc(fin);
> >> + if (value == EOF) return -1;
> >>
> >> + *curr = value;
> >> ret++;
> >> if (*curr == '\n' && hit == 1)
> >> return ret - 1;
> >
> >
> >
>
>
> --
> ~Randy
>
> --
> 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>
--
Kind regards,
Minchan Kim
--
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>
next prev parent reply other threads:[~2013-01-10 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 6:05 [PATCH] Fix wrong EOF compare Minchan Kim
2013-01-10 15:26 ` Michal Nazarewicz
2013-01-10 16:12 ` Randy Dunlap
2013-01-10 23:34 ` Minchan Kim [this message]
2013-01-10 23:33 ` Minchan Kim
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=20130110233456.GB2470@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexn@dsv.su.se \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mina86@mina86.com \
--cc=rdunlap@infradead.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).