From: Randy Dunlap <rdunlap@xenotime.net>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 17 (exofs)
Date: Tue, 17 Nov 2009 09:48:12 -0800 [thread overview]
Message-ID: <20091117094812.97775988.rdunlap@xenotime.net> (raw)
In-Reply-To: <4B02DC46.5060202@panasas.com>
On Tue, 17 Nov 2009 19:24:22 +0200 Boaz Harrosh wrote:
> On 11/17/2009 07:10 PM, Boaz Harrosh wrote:
> > On 11/17/2009 07:08 PM, Boaz Harrosh wrote:
> >> On 11/17/2009 07:02 PM, Randy Dunlap wrote:
> >>> On Tue, 17 Nov 2009 19:53:09 +1100 Stephen Rothwell wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> Changes since 20091116:
> >>>
> >>>
> >>> on i386 (X86_32):
> >>>
> >>> fs/built-in.o: In function `exofs_sbi_read':
> >>> (.text+0x592964): undefined reference to `__umoddi3'
> >>>
> >>> ---
> >>> ~Randy
> >>
> >> exofs_sbi_read is a totally simple loop thing. What does the
> >> __umoddi3 means? Please help?
> >>
> >> Boaz
> >
> > OK I think I get it. It's that u64 mod (%) operation. I'll try to
> > find a ready made macro for that. Sorry
> >
> > Boaz
> >
>
> I'll push this fix for tomorrow. Thanks for helping me find it.
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks!
> 4G devices is more than enough thank you ;-)
>
> Boaz
> ---
> git diff --stat -p -M fs/exofs/ios.c
> fs/exofs/ios.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/exofs/ios.c b/fs/exofs/ios.c
> index 14b2600..5bad01f 100644
> --- a/fs/exofs/ios.c
> +++ b/fs/exofs/ios.c
> @@ -320,8 +320,9 @@ int exofs_sbi_read(struct exofs_io_state *ios)
>
> for (i = 0; i < 1; i++) {
> struct osd_request *or;
> - unsigned first_dev = ios->obj.id % ios->sbi->s_numdevs;
> + unsigned first_dev = (unsigned)ios->obj.id;
>
> + first_dev %= ios->sbi->s_numdevs;
> or = osd_start_request(ios->sbi->s_ods[first_dev], GFP_KERNEL);
> if (unlikely(!or)) {
> EXOFS_ERR("%s: osd_start_request failed\n", __func__);
>
---
~Randy
next prev parent reply other threads:[~2009-11-17 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 8:53 linux-next: Tree for November 17 Stephen Rothwell
2009-11-17 17:02 ` linux-next: Tree for November 17 (exofs) Randy Dunlap
2009-11-17 17:08 ` Boaz Harrosh
2009-11-17 17:10 ` Boaz Harrosh
2009-11-17 17:24 ` Boaz Harrosh
2009-11-17 17:48 ` Randy Dunlap [this message]
2009-11-17 18:17 ` [PATCH -next] sep: fix 2 warnings Randy Dunlap
2009-11-17 18:29 ` Alan Cox
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=20091117094812.97775988.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®