linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Quentin Schulz <quentin.schulz@bootlin.com>,
	richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.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, 2 Jul 2018 09:51:21 +0200	[thread overview]
Message-ID: <20180702095121.67bc61ef@bbrezillon> (raw)
In-Reply-To: <1530516625.469.82.camel@gmail.com>

Hi Artem,

On Mon, 02 Jul 2018 10:30:25 +0300
Artem Bityutskiy <dedekind1@gmail.com> wrote:

> 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 ?

Yep, it's on purpose, I asked Quentin to keep the test on the update
volume path.

> 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, I thought checking the CRC just after updating the volume made
sense, just to make sure things were written correctly on the medium.
Let's add a comment explaining why we keep the check here, unless you
see a strong reason to get rid of this check in the update path.

Regards,

Boris

  parent reply	other threads:[~2018-07-02  7:51 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
2018-07-02  7:49       ` Artem Bityutskiy
2018-07-02  7:51     ` Boris Brezillon [this message]
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=20180702095121.67bc61ef@bbrezillon \
    --to=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=richard@nod.at \
    --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).