From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: nfsd tree build warning
Date: Mon, 16 Mar 2009 09:42:45 -0400 [thread overview]
Message-ID: <20090316134245.GB8598@fieldses.org> (raw)
In-Reply-To: <20090316165121.3ebaf449.sfr@canb.auug.org.au>
On Mon, Mar 16, 2009 at 04:51:21PM +1100, Stephen Rothwell wrote:
> Today's linux-next build (powerpc ppc64_defconfig) produced this warning:
>
> fs/nfsd/nfs4recover.c: In function 'nfsd4_build_namelist':
> fs/nfsd/nfs4recover.c:203: warning: array subscript is above array bounds
>
> Caused by commit d1d269b9d0cadf221cfa3ddbe65a3a0e4cf100e1 ("nfsd4: don't
> do lookup within readdir in recovery code").
That should be fixed now, thanks.--b.
next prev parent reply other threads:[~2009-03-16 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 5:51 linux-next: nfsd tree build warning Stephen Rothwell
2009-03-16 13:42 ` J. Bruce Fields [this message]
2009-03-16 23:05 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 3:57 Stephen Rothwell
2009-04-29 15:01 ` J. Bruce Fields
2009-08-11 1:07 Stephen Rothwell
2009-08-11 16:53 ` 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=20090316134245.GB8598@fieldses.org \
--to=bfields@fieldses.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;
as well as URLs for NNTP newsgroup(s).