From: Richard Weinberger <richard@nod.at>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Quentin Schulz <quentin.schulz@bootlin.com>,
dedekind1@gmail.com, 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 2/2] ubi: expose the volume CRC check skip flag
Date: Mon, 02 Jul 2018 08:54:09 +0200 [thread overview]
Message-ID: <2109705.Xvz1DYdJuj@blindfold> (raw)
In-Reply-To: <20180702085227.2b418264@bbrezillon>
Am Montag, 2. Juli 2018, 08:52:27 CEST schrieb Boris Brezillon:
> On Mon, 2 Jul 2018 08:44:33 +0200
> Quentin Schulz <quentin.schulz@bootlin.com> wrote:
>
> > Hi Richard, Boris,
> >
> > On Sun, Jul 01, 2018 at 10:50:41PM +0200, Richard Weinberger wrote:
> > > Am Sonntag, 1. Juli 2018, 22:33:47 CEST schrieb Boris Brezillon:
> > > > On Sun, 01 Jul 2018 21:35:57 +0200
> > > > Richard Weinberger <richard@nod.at> wrote:
> > > >
> > > > > Quentin,
> > > > >
> > > > > Am Donnerstag, 28. Juni 2018, 09:40:53 CEST schrieb Quentin Schulz:
> > > > > > Now that we have the logic for skipping CRC check for static UBI volumes
> > > > > > in the core, let's expose it to users.
> > > > > >
> > > > > > This makes use of a padding byte in the volume description data
> > > > > > structure as a flag. This flag only tell for now whether we should skip
> > > > > > the CRC check of a volume.
> > > > > >
> > > > > > This checks the UBI volume for which we are trying to skip the CRC check
> > > > > > is static.
> > > > > >
> > > > > > Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > > > > > Signed-off-by: Quentin Schulz <quentin.schulz@bootlin.com>
> > > > > > Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > > > > > ---
> > > > > > drivers/mtd/ubi/cdev.c | 4 ++++
> > > > > > drivers/mtd/ubi/vmt.c | 3 +++
> > > > > > include/uapi/mtd/ubi-user.h | 16 ++++++++++++++--
> > > > > > 3 files changed, 21 insertions(+), 2 deletions(-)
> > > > > >
> > > > > > diff --git a/drivers/mtd/ubi/cdev.c b/drivers/mtd/ubi/cdev.c
> > > > > > index 45c3296..3eea1df 100644
> > > > > > --- a/drivers/mtd/ubi/cdev.c
> > > > > > +++ b/drivers/mtd/ubi/cdev.c
> > > > > > @@ -622,6 +622,10 @@ static int verify_mkvol_req(const struct ubi_device *ubi,
> > > > > > req->vol_type != UBI_STATIC_VOLUME)
> > > > > > goto bad;
> > > > > >
> > > > > > + if (req->flags & UBI_VOL_SKIP_CRC_CHECK_FLG &&
> > > >
> > > > Oops, missed that req->flags & UBI_VOL_SKIP_CRC_CHECK_FLG check was
> > > > missing parens (checkpatch --strict should complain about that).
> > >
> > > Latest when building my local branch or in linux-next we had noticed.
> > > No need to worry.
> > >
> > > > > > + req->vol_type != UBI_STATIC_VOLUME)
> > > > > > + goto bad;
> > > > >
> > > > > We should also reject unknown flags here.
> > > >
> > > > I agree.
> >
> > Should I send another version of my patches for it?
Yes. Please.
> Yes please, respin your series with this additional check. Just define
>
> #define UBI_VOL_VALID_FLGS (UBI_VOL_SKIP_CRC_CHECK_FLG)
>
> and then, in verify_mkvol_req() add
>
> if (req->flags & ~UBI_VOL_VALID_FLGS)
> goto bad;
Yep.
> > Same for
> > parenthesis around the flags masking above?
>
> No need to fix that one (unless Richard cares), as it seems I had it
> wrong.
Nah. If both gcc and checkpatch don't complain, let's keep it as-is.
Thanks,
//richard
next prev parent reply other threads:[~2018-07-02 6:54 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
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 [this message]
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=2109705.Xvz1DYdJuj@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).