From: Matthew Wilcox <willy@infradead.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Davidlohr Bueso <dave@stgolabs.net>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Chaitanya Kulkarni <kch@nvidia.com>,
Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH v4 2/5] block: add partition parser for U-Boot uImage.FIT
Date: Wed, 9 Nov 2022 13:58:29 +0000 [thread overview]
Message-ID: <Y2uyBYyQOC4O5iep@casper.infradead.org> (raw)
In-Reply-To: <Y2rgNEQlxKgiIDdk@makrotopia.org>
On Tue, Nov 08, 2022 at 11:03:16PM +0000, Daniel Golle wrote:
> + /* map first page */
> + page = read_mapping_page(
> + mapping, fit_start_sector >> (PAGE_SHIFT - SECTOR_SHIFT), NULL);
> +
> + if (IS_ERR(page))
> + return -EFAULT;
> +
> + if (PageError(page))
> + return -EFAULT;
Why are you checking for PageError? You won't ever get a page with an
error back from read_mapping_page(). And you have the real error in
'page', so why return -EFAUlT, which would indicate a problem copying
from the user. Also, this is a great place to use the new folio APIs
instead of the old page APIs. So:
folio = read_mapping_folio(mapping,
fit_start_sector >> PAGE_SECTORS_SHIFT, NULL);
if (IS_ERR(folio))
return PTR_ERR(folio);
> + init_fit = page_address(page);
init_fit = folio_address(folio) +
offset_in_folio(folio, fit_start_sector * SECTOR_SIZE);
> + if (!init_fit) {
> + put_page(page);
> + return -EFAULT;
> + }
page_address() or folio_address() can't ever return NULL, you should
just drop this nonsense check.
... actually, why can't you call read_part_sector() and avoid all of
this?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-11-09 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 23:03 [PATCH v4 2/5] block: add partition parser for U-Boot uImage.FIT Daniel Golle
2022-11-09 13:58 ` Matthew Wilcox [this message]
2022-11-09 14:36 ` Daniel Golle
2022-11-09 17:21 ` Matthew Wilcox
2022-11-10 1:52 ` Daniel Golle
2022-11-10 15:03 ` Matthew Wilcox
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=Y2uyBYyQOC4O5iep@casper.infradead.org \
--to=willy@infradead.org \
--cc=axboe@kernel.dk \
--cc=daniel@makrotopia.org \
--cc=dave@stgolabs.net \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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