From: Suresh Jayaraman <sjayaraman@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: sfrench@samba.org, linux-cifs-client@lists.samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: fix compiler warning on 64-bit arch-s
Date: Fri, 18 Jul 2008 18:05:32 +0530 [thread overview]
Message-ID: <48808E14.8050801@suse.de> (raw)
In-Reply-To: <4880A5A9.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> ---
> fs/cifs/asn1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-2.6.26/fs/cifs/asn1.c 2008-07-13 23:51:29.000000000 +0200
> +++ 2.6.26-cifs-warning/fs/cifs/asn1.c 2008-07-17 15:23:11.000000000 +0200
> @@ -400,7 +400,7 @@ asn1_oid_decode(struct asn1_ctx *ctx,
> size = eoc - ctx->pointer + 1;
>
> /* first subid actually encodes first two subids */
> - if (size < 2 || size > ULONG_MAX/sizeof(unsigned long))
> + if (size < 2 || size > UINT_MAX/sizeof(unsigned long))
> return 0;
>
> *oid = kmalloc(size * sizeof(unsigned long), GFP_ATOMIC);
>
>
I did see the following patch from David Howells attempting to fix the
same warning posted a little earlier.
Fix the CIFS range check to always use a big enough size variable that
the compiler won't moan about comparing it to ULONG_MAX/8 on a 64-bit
platform.
Signed-off-by: David Howells <dhowells@redhat.com>
---
fs/cifs/asn1.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/cifs/asn1.c b/fs/cifs/asn1.c
index f58e41d..512587d 100644
--- a/fs/cifs/asn1.c
+++ b/fs/cifs/asn1.c
@@ -394,8 +394,8 @@ asn1_oid_decode(struct asn1_ctx *ctx,
unsigned char *eoc, unsigned long **oid, unsigned int *len)
{
unsigned long subid;
- unsigned int size;
unsigned long *optr;
+ size_t size;
size = eoc - ctx->pointer + 1;
Thanks,
--
Suresh Jayaraman
next prev parent reply other threads:[~2008-07-18 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 12:16 [PATCH] cifs: fix compiler warning on 64-bit arch-s Jan Beulich
2008-07-18 12:35 ` Suresh Jayaraman [this message]
2008-07-22 13:05 ` Steve French
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=48808E14.8050801@suse.de \
--to=sjayaraman@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
/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.