[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPAsAGyB578shW36WcpwdTLA0-uwpa574fH4ZDfYPzeQ=f9zPw@mail.gmail.com>
Date: Wed, 2 Dec 2015 21:32:34 +0300
From: Andrey Ryabinin <ryabinin.a.a@...il.com>
To: Chris Mason <clm@...com>, Dave Jones <davej@...emonkey.org.uk>,
Josef Bacik <jbacik@...com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
"J. Bruce Fields" <bfields@...ldses.org>,
Jeff Layton <jlayton@...chiereds.net>,
David Sterba <dsterba@...e.com>, conchur@....de
Subject: Re: 4.4rc3 nfsd/btrfs kasan warning.
2015-12-02 20:14 GMT+03:00 Chris Mason <clm@...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.
BTW, there is similar report
http://lkml.kernel.org/r/<trinity-c7a088d8-bb35-484e-bf27-dbd9a94a804c-1448959367092@...pp-webde-bs56>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists