From: Salah Triki <salah.triki@acm.org>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: Salah Triki <salah.triki@gmail.com>,
akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
mhocko@suse.com, vdavydov@virtuozzo.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct
Date: Sat, 2 Jul 2016 14:34:43 +0100 [thread overview]
Message-ID: <20160702133443.GB3817@pc> (raw)
In-Reply-To: <5777A7AA.4020500@osg.samsung.com>
On Sat, Jul 02, 2016 at 12:38:18PM +0100, Luis de Bethencourt wrote:
> On 02/07/16 09:05, Salah Triki wrote:
> > The only caller of befs_find_brun_direct is befs_fblock2brun, which
> > already validates that the block is within the range of direct blocks.
> > So remove the duplicate validation.
> >
> > Signed-off-by: Salah Triki <salah.triki@gmail.com>
> > ---
> > fs/befs/datastream.c | 8 --------
> > 1 file changed, 8 deletions(-)
> >
> > diff --git a/fs/befs/datastream.c b/fs/befs/datastream.c
> > index 26cc417..e224b9a 100644
> > --- a/fs/befs/datastream.c
> > +++ b/fs/befs/datastream.c
> > @@ -249,17 +249,9 @@ befs_find_brun_direct(struct super_block *sb, const befs_data_stream *data,
> > int i;
> > const befs_block_run *array = data->direct;
> > befs_blocknr_t sum;
> > - befs_blocknr_t max_block =
> > - data->max_direct_range >> BEFS_SB(sb)->block_shift;
> >
> > befs_debug(sb, "---> %s, find %lu", __func__, (unsigned long)blockno);
> >
> > - if (blockno > max_block) {
> > - befs_error(sb, "%s passed block outside of direct region",
> > - __func__);
> > - return BEFS_ERR;
> > - }
> > -
> > for (i = 0, sum = 0; i < BEFS_NUM_DIRECT_BLOCKS;
> > sum += array[i].len, i++) {
> > if (blockno >= sum && blockno < sum + (array[i].len)) {
> >
>
> Hi Salah,
>
> These aren't the same check though. If we ignore the BEFS_SB(sb)->block_shift just to
> comparing them, we can consider the checks to be the following.
>
> In befs_fblock2brun():
> if (fblock < data->max_direct_range)
>
> In befs_find_brun_direct():
> if (fblock > data->max_direct_range)
>
> Notice how one checks if the block is past the range, and the other checks if it isn't
> before it.
>
> They also looked similar to me the first time I saw them and I had to double-check :)
>
> Thanks,
> Luis
>
>
the two checks could not be evaluated to true at the same time, and since befs_find_brun_direct
is called only when the first check is passed, the second check will be always evaluated to false.
So I think the second check is useless, am I right ?
Salah
next prev parent reply other threads:[~2016-07-02 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 8:05 [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct Salah Triki
2016-07-02 8:05 ` [PATCH 2/4] fs: befs: Coding style fix Salah Triki
2016-07-02 11:22 ` Luis de Bethencourt
2016-07-02 8:05 ` [PATCH 3/4] fs: befs: Remove useless calls to brelse in befs_find_brun_dblindirect Salah Triki
2016-07-02 11:51 ` Luis de Bethencourt
2016-07-02 8:05 ` [PATCH 4/4] fs: befs: Remove goto from befs_bread_iaddr Salah Triki
2016-07-02 12:04 ` Luis de Bethencourt
2016-07-02 11:38 ` [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct Luis de Bethencourt
2016-07-02 13:34 ` Salah Triki [this message]
2016-07-02 14:44 ` Luis de Bethencourt
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=20160702133443.GB3817@pc \
--to=salah.triki@acm.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=mhocko@suse.com \
--cc=salah.triki@gmail.com \
--cc=vdavydov@virtuozzo.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.