Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756781AbcJRXjd (ORCPT ); Tue, 18 Oct 2016 19:39:33 -0400 Received: from mail-oi0-f45.google.com ([209.85.218.45]:36186 "EHLO mail-oi0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756357AbcJRXjY (ORCPT ); Tue, 18 Oct 2016 19:39:24 -0400 MIME-Version: 1.0 In-Reply-To: <20161018233148.GA93792@clm-mbp.masoncoding.com> References: <20161011144507.okg6baqvodn2m2lh@codemonkey.org.uk> <20161018224205.bjgloslaxcej2td2@codemonkey.org.uk> <20161018233148.GA93792@clm-mbp.masoncoding.com> From: Linus Torvalds Date: Tue, 18 Oct 2016 16:39:22 -0700 X-Google-Sender-Auth: w_arO3r80rcujonlmIIxa3M4i9k Message-ID: Subject: Re: bio linked list corruption. To: Chris Mason , Jens Axboe , Dave Jones , Al Viro , Josef Bacik , David Sterba , linux-btrfs , Linux Kernel , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 477 Lines: 12 On Tue, Oct 18, 2016 at 4:31 PM, Chris Mason 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. Linus