From: ebiederm@xmission.com (Eric W. Biederman)
To: Tim Gardner <tim.gardner@canonical.com>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH linux-next] befs: befs_fill_super(): remove unreachable code
Date: Tue, 12 Feb 2013 09:46:19 -0800 [thread overview]
Message-ID: <87halhfms4.fsf@xmission.com> (raw)
In-Reply-To: <1360690488-60060-1-git-send-email-tim.gardner@canonical.com> (Tim Gardner's message of "Tue, 12 Feb 2013 10:34:47 -0700")
Tim Gardner <tim.gardner@canonical.com> writes:
> befs_sb->num_blocks is of base type u64 which is the same as sector_t.
> Therefore, num_blocks can never be larger then the maximum
> value of sector_t.
The analysys is wrong. On 32bit with CONFIG_LBAF unset sector_t is an
unsigned long aka a u32, while befs_off_t is always a u64.
Nacked-by: "Eric W. Biederman" <ebiederm@xmission.com>
> smatch analysis:
>
> fs/befs/linuxvfs.c:851 befs_fill_super() warn: impossible
> condition '(befs_sb->num_blocks > ~(0)) => (0-u64max > u64max)'
>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> ---
> fs/befs/linuxvfs.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/fs/befs/linuxvfs.c b/fs/befs/linuxvfs.c
> index 2b3bda8..2ce5705 100644
> --- a/fs/befs/linuxvfs.c
> +++ b/fs/befs/linuxvfs.c
> @@ -848,13 +848,6 @@ befs_fill_super(struct super_block *sb, void *data, int silent)
> if (befs_check_sb(sb) != BEFS_OK)
> goto unacquire_priv_sbp;
>
> - if( befs_sb->num_blocks > ~((sector_t)0) ) {
> - befs_error(sb, "blocks count: %Lu "
> - "is larger than the host can use",
> - befs_sb->num_blocks);
> - goto unacquire_priv_sbp;
> - }
> -
> /*
> * set up enough so that it can read an inode
> * Fill in kernel superblock fields from private sb
next prev parent reply other threads:[~2013-02-12 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 17:34 [PATCH linux-next] befs: befs_fill_super(): remove unreachable code Tim Gardner
2013-02-12 17:46 ` Eric W. Biederman [this message]
2013-02-12 18:07 ` Tim Gardner
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=87halhfms4.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.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.