From: Chris Mason <clm@fb.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dave Jones <davej@codemonkey.org.uk>, Josef Bacik <jbacik@fb.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>,
David Sterba <dsterba@suse.com>, <conchur@web.de>
Subject: Re: 4.4rc3 nfsd/btrfs kasan warning.
Date: Wed, 2 Dec 2015 14:01:38 -0500 [thread overview]
Message-ID: <20151202190138.GF8918@ret.masoncoding.com> (raw)
In-Reply-To: <CAPAsAGyB578shW36WcpwdTLA0-uwpa574fH4ZDfYPzeQ=f9zPw@mail.gmail.com>
On Wed, Dec 02, 2015 at 09:32:34PM +0300, Andrey Ryabinin wrote:
> 2015-12-02 20:14 GMT+03:00 Chris Mason <clm@fb.com>:
> > On Wed, Dec 02, 2015 at 11:09:43AM -0500, Dave Jones wrote:
> >> On Wed, Dec 02, 2015 at 10:11:28AM -0500, Josef Bacik wrote:
> >> > On 12/02/2015 09:59 AM, Dave Jones wrote:
> >> > > Got a few of these in the logs this morning after an overnight rsync over nfs
> >> > > to an exported btrfs volume.
> >> >
> >> > That's probably us and not NFS, what line is that in
> >> > setup_cluster_bitmap? Thanks,
> >>
> >> If my math is correct, it's this..
> >>
> >> if (entry->offset != bitmap_offset)
> >>
> >> I don't seem to be able to trigger it on demand unfortunatly.
> >
> > Is it possible we're blowing the stack? It seems pretty tricky to get a
> > stack out of bounds out of this code without flat out blowing through
> > it.
> >
>
> I think it just empty bitmaps list.
> list_first_entry() can't be used on empty list.
Ohh, I was so busy looking for free'd entries I missed that. Good
point.
-chris
prev parent reply other threads:[~2015-12-02 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:59 4.4rc3 nfsd/btrfs kasan warning Dave Jones
2015-12-02 15:11 ` Josef Bacik
2015-12-02 16:09 ` Dave Jones
2015-12-02 17:14 ` Chris Mason
2015-12-02 17:36 ` Dave Jones
2015-12-02 18:32 ` Andrey Ryabinin
2015-12-02 19:01 ` Chris Mason [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=20151202190138.GF8918@ret.masoncoding.com \
--to=clm@fb.com \
--cc=bfields@fieldses.org \
--cc=conchur@web.de \
--cc=davej@codemonkey.org.uk \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
/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