From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: Quentin Schulz <quentin.schulz@bootlin.com>,
dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@bootlin.com, marek.vasut@gmail.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com
Subject: Re: [PATCH v3 1/2] ubi: provide a way to skip CRC checks
Date: Mon, 02 Jul 2018 09:43:48 +0200 [thread overview]
Message-ID: <1814021.2UnKZ8bNR8@blindfold> (raw)
In-Reply-To: <1530516625.469.82.camel@gmail.com>
Artem,
Am Montag, 2. Juli 2018, 09:30:25 CEST schrieb Artem Bityutskiy:
> Hi,
>
> On Thu, 2018-06-28 at 09:40 +0200, Quentin Schulz wrote:
> > diff --git a/drivers/mtd/ubi/kapi.c b/drivers/mtd/ubi/kapi.c
> > index d4b2e87..e9e9ecb 100644
> > --- a/drivers/mtd/ubi/kapi.c
> > +++ b/drivers/mtd/ubi/kapi.c
> > @@ -202,7 +202,7 @@ struct ubi_volume_desc *ubi_open_volume(int ubi_num, int vol_id, int mode)
> > desc->mode = mode;
> >
> > mutex_lock(&ubi->ckvol_mutex);
> > - if (!vol->checked) {
> > + if (!vol->checked && !vol->skip_check) {
> > /* This is the first open - check the volume */
> > err = ubi_check_volume(ubi, vol_id);
> > if (err < 0) {
>
> Did you deliberately did not add a similar check to 'vol_cdev_write()' ?
> You want to skip checking on load but do have the checking after volume update ?
> Looks a bit inconsistent to me. At the very least deserves a comment in
> 'vol_cdev_write()' about why 'skip_check' flag is ignored there.
Well, the idea is skipping the check, not the crc32 on the medium.
That way we can later, if needed, offer a way to drop the flag but
and don't have to rewrite with crc32-enabled.
Thanks,
//richard
next prev parent reply other threads:[~2018-07-02 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 7:40 [PATCH v3 0/2] ubi: add possibility to skip CRC check for static UBI volumes Quentin Schulz
2018-06-28 7:40 ` [PATCH v3 1/2] ubi: provide a way to skip CRC checks Quentin Schulz
2018-07-01 19:37 ` Richard Weinberger
2018-07-02 7:30 ` Artem Bityutskiy
2018-07-02 7:43 ` Richard Weinberger [this message]
2018-07-02 7:49 ` Artem Bityutskiy
2018-07-02 7:51 ` Boris Brezillon
2018-07-02 7:56 ` Richard Weinberger
2018-07-02 9:36 ` Artem Bityutskiy
2018-06-28 7:40 ` [PATCH v3 2/2] ubi: expose the volume CRC check skip flag Quentin Schulz
2018-07-01 19:35 ` Richard Weinberger
2018-07-01 20:33 ` Boris Brezillon
2018-07-01 20:50 ` Richard Weinberger
2018-07-02 6:44 ` Quentin Schulz
2018-07-02 6:52 ` Boris Brezillon
2018-07-02 6:54 ` Richard Weinberger
2018-07-01 20:54 ` Joe Perches
2018-07-01 21:01 ` Richard Weinberger
2018-07-01 21:39 ` Joe Perches
2018-07-02 6:46 ` Boris Brezillon
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=1814021.2UnKZ8bNR8@blindfold \
--to=richard@nod.at \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=quentin.schulz@bootlin.com \
--cc=thomas.petazzoni@bootlin.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).