From: Richard Weinberger <richard@nod.at>
To: David Oberhollenzer <goliath@sigma-star.at>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] libubigen: Maintain a eraseblock association table
Date: Tue, 15 May 2018 22:22:16 +0200 [thread overview]
Message-ID: <5480742.m6jlgxS7AR@blindfold> (raw)
In-Reply-To: <cc8f9abd-42b7-cc71-b89c-92c5cbd84aa3@sigma-star.at>
Am Dienstag, 15. Mai 2018, 21:58:01 CEST schrieb David Oberhollenzer:
> On 05/14/2018 01:25 PM, Richard Weinberger wrote:
> > @@ -229,6 +234,12 @@ int ubigen_write_volume(const struct ubigen_info *ui,
> > memset(outbuf + ui->data_offs + len, 0xFF,
> > ui->peb_size - ui->data_offs - len);
> >
> > + vi->eba[lnum] = lseek(out, 0, SEEK_CUR) / ui->peb_size;
> > + if (vi->eba[lnum] == -1) {
> > + sys_errmsg("cannot get offset of output file");
> > + goto out_free1;
> > + }
> > +
> > if (write(out, outbuf, ui->peb_size) != ui->peb_size) {
> > sys_errmsg("cannot write %d bytes to the output file", ui->peb_size);
> > goto out_free1;
>
> Wouldn't that division swallow errors? If I interpret the C99 draft correctly, dividing
> an lseek return value of -1 by ui->peb_size > 1 should result in 0.
Yep, that needs fixing.
Thanks,
//richard
next prev parent reply other threads:[~2018-05-15 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 11:25 [PATCH 0/5] mtd-utils: Add fastmap support to ubinize Richard Weinberger
2018-05-14 11:25 ` [PATCH 1/5] Sync ubi-media.h with Linux Richard Weinberger
2018-05-14 11:25 ` [PATCH 2/5] ubinize: Don't stat image file twice Richard Weinberger
2018-05-14 11:25 ` [PATCH 3/5] libubigen: Carry image path and size in volume info Richard Weinberger
2018-05-14 11:25 ` [PATCH 4/5] libubigen: Maintain a eraseblock association table Richard Weinberger
2018-05-15 19:58 ` David Oberhollenzer
2018-05-15 20:22 ` Richard Weinberger [this message]
2018-05-14 11:25 ` [PATCH 5/5] ubinize: Add fastmap support Richard Weinberger
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=5480742.m6jlgxS7AR@blindfold \
--to=richard@nod.at \
--cc=goliath@sigma-star.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.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