[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9ba0cd0b-33f6-2156-aaf2-ad9ed9a00115@pmhahn.de>
Date: Wed, 19 Oct 2016 19:09:46 +0200
From: Philipp Hahn <pmhahn@...ahn.de>
To: Chris Mason <clm@...com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jens Axboe <axboe@...com>,
Dave Jones <davej@...emonkey.org.uk>,
Al Viro <viro@...iv.linux.org.uk>, Josef Bacik <jbacik@...com>,
David Sterba <dsterba@...e.com>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: bio linked list corruption.
Hello,
Am 19.10.2016 um 01:42 schrieb Chris Mason:
> On Tue, Oct 18, 2016 at 04:39:22PM -0700, Linus Torvalds wrote:
>> On Tue, Oct 18, 2016 at 4:31 PM, Chris Mason <clm@...com> wrote:
>>>
>>> Jens, not sure if you saw the whole thread. This has triggered bad page
>>> state errors, and also corrupted a btrfs list. It hurts me to say,
>>> but it
>>> might not actually be your fault.
>>
>> Where is that thread, and what is the "this" that triggers problems?
>>
>> Looking at the "->mq_list" users, I'm not seeing any changes there in
>> the last year or so. So I don't think it's the list itself.
>
> Seems to be the whole thing:
>
> http://www.gossamer-threads.com/lists/linux/kernel/2545792
>
> My guess is xattr, but I don't have a good reason for that.
Nearly a month ago I reported also a "list_add corruption", but with 4.1.6:
<http://marc.info/?l=linux-kernel&m=147508265316854&w=2>
That server rungs Samba4, which also is a heavy user of xattr.
Might be that it is related.
Philipp Hahn
Powered by blists - more mailing lists