From: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public•gmane.org>
To: Jim Rees <rees-63aXycvo3TyHXe+LvDLADg@public•gmane.org>
Cc: Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public•gmane.org>,
Sasha Levin
<levinsasha928-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>,
<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public•gmane.org>,
<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>,
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>
Subject: Re: [PATCH] SUNRPC: Prevent kernel stack corruption on long values of flush
Date: Wed, 17 Oct 2012 11:29:44 -0700 [thread overview]
Message-ID: <507EF918.5030004@panasas.com> (raw)
In-Reply-To: <20120718205510.GA18374-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
On 07/18/2012 01:55 PM, Jim Rees wrote:
> Dave Jones wrote:
>
>
> Unsigned long isn't necessarily 32 bits.
> On 64-bit systems %lu can be up to 18446744073709551615
>
> Thanks. You caught me thinking "Intel." How embarrassing.
What? why even on Intel-64 long is 64bit. long is always the
same or bigger then a pointer (A pointer must always fit
in a long)
On the other hand int is 32bit in Intel-64 unlike some
other CPUs where int(s) may get to be 64bit as well.
Cheers
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-17 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 22:01 [PATCH] SUNRPC: Prevent kernel stack corruption on long values of flush Sasha Levin
2012-07-18 17:39 ` J. Bruce Fields
2012-07-18 20:00 ` Jim Rees
[not found] ` <20120718200049.GA17964-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2012-07-18 20:33 ` Dave Jones
[not found] ` <20120718203304.GA18540-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-07-18 20:55 ` Jim Rees
[not found] ` <20120718205510.GA18374-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2012-10-17 18:29 ` Boaz Harrosh [this message]
[not found] ` <507EF918.5030004-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2012-10-18 8:34 ` David Laight
2012-07-18 21:08 ` J. Bruce Fields
[not found] ` <50072BA7.6070205@gmail.com>
[not found] ` <50072BA7.6070205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-18 21:43 ` Sasha Levin
[not found] ` <50072DEE.2000205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-18 23:04 ` Jim Rees
[not found] ` <20120718173913.GA1298-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2012-10-17 17:59 ` Sasha Levin
[not found] ` <CA+1xoqcgWTP8pAY3Ok2R0JM-ZXSkGroEvAFcqP0KaK=dABiTXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-17 19:02 ` J. Bruce Fields
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=507EF918.5030004@panasas.com \
--to=bharrosh-c4p08nqkorlbdgjk7y7tuq@public$(echo .)gmane.org \
--cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public$(echo .)gmane.org \
--cc=davej-H+wXaHxf7aLQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=levinsasha928-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=rees-63aXycvo3TyHXe+LvDLADg@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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