From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: Luis Henriques <luis.henriques-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: Trond Myklebust
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
"David S. Miller" <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] gss_krb5: use lcm from kernel lib
Date: Wed, 22 Jan 2014 13:12:42 -0500 [thread overview]
Message-ID: <20140122181242.GB13704@fieldses.org> (raw)
In-Reply-To: <20140119215040.GA7978@hercules>
On Sun, Jan 19, 2014 at 09:50:51PM +0000, Luis Henriques wrote:
> Replace hardcoded lowest common multiple algorithm by the lcm()
> function in kernel lib.
Looks OK to me. Applying for 3.14 if Trond hasn't already picked it up.
--b.
>
> Signed-off-by: Luis Henriques <luis.henriques-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> ---
> net/sunrpc/auth_gss/gss_krb5_keys.c | 17 ++++-------------
> 1 file changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/net/sunrpc/auth_gss/gss_krb5_keys.c b/net/sunrpc/auth_gss/gss_krb5_keys.c
> index 76e42e6..a16c5b6 100644
> --- a/net/sunrpc/auth_gss/gss_krb5_keys.c
> +++ b/net/sunrpc/auth_gss/gss_krb5_keys.c
> @@ -59,6 +59,7 @@
> #include <linux/crypto.h>
> #include <linux/sunrpc/gss_krb5.h>
> #include <linux/sunrpc/xdr.h>
> +#include <linux/lcm.h>
>
> #ifdef RPC_DEBUG
> # define RPCDBG_FACILITY RPCDBG_AUTH
> @@ -72,7 +73,7 @@
> static void krb5_nfold(u32 inbits, const u8 *in,
> u32 outbits, u8 *out)
> {
> - int a, b, c, lcm;
> + unsigned long ulcm;
> int byte, i, msbit;
>
> /* the code below is more readable if I make these bytes
> @@ -82,17 +83,7 @@ static void krb5_nfold(u32 inbits, const u8 *in,
> outbits >>= 3;
>
> /* first compute lcm(n,k) */
> -
> - a = outbits;
> - b = inbits;
> -
> - while (b != 0) {
> - c = b;
> - b = a%b;
> - a = c;
> - }
> -
> - lcm = outbits*inbits/a;
> + ulcm = lcm(inbits, outbits);
>
> /* now do the real work */
>
> @@ -101,7 +92,7 @@ static void krb5_nfold(u32 inbits, const u8 *in,
>
> /* this will end up cycling through k lcm(k,n)/k times, which
> is correct */
> - for (i = lcm-1; i >= 0; i--) {
> + for (i = ulcm-1; i >= 0; i--) {
> /* compute the msbit in k which gets added into this byte */
> msbit = (
> /* first, start with the msbit in the first,
> --
> 1.8.3.2
>
> Cheers,
> --
> Luis
--
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
prev parent reply other threads:[~2014-01-22 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 21:50 [PATCH] gss_krb5: use lcm from kernel lib Luis Henriques
2014-01-22 18:12 ` J. Bruce Fields [this message]
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=20140122181242.GB13704@fieldses.org \
--to=bfields-uc3wqj2krung9huczpvpmw@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luis.henriques-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.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 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).