Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751553AbbLUFXV (ORCPT ); Mon, 21 Dec 2015 00:23:21 -0500 Received: from mail-ig0-f182.google.com ([209.85.213.182]:36467 "EHLO mail-ig0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750860AbbLUFXS (ORCPT ); Mon, 21 Dec 2015 00:23:18 -0500 MIME-Version: 1.0 In-Reply-To: References: <20aa515947cdc15799f520f904ad99a2@lycos.com> <3c353dc4883c60ee99caa4555c81b6a1@lycos.com> Date: Sun, 20 Dec 2015 21:23:18 -0800 X-Google-Sender-Auth: Wq2LDd6tWxuL9faFE97rQ8Vqysk Message-ID: Subject: Re: IO errors after "block: remove bio_get_nr_vecs()" From: Linus Torvalds To: "Artem S. Tashkinov" Cc: Ming Lei , Kent Overstreet , Christoph Hellwig , Ming Lin , Jens Axboe , "Artem S. Tashkinov" , Steven Whitehouse , Tejun Heo , IDE-ML , Linux Kernel Mailing List 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: 863 Lines: 22 On Sun, Dec 20, 2015 at 8:47 PM, Linus Torvalds wrote: > > That said, we obviously need to figure out this current problem > regardless first.. ... although maybe it *would* be interesting to hear what happens if you just compile a 64-bit kernel instead? Do you still see the problem? Because if not, then we should look very specifically for some 32-bit PAE issue. For example, maybe we use "unsigned long" somewhere where we should use "phys_addr_t". On x86-64, they obviously end up being the same. On normal non-PAE x86-32, they are also the same. But .. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/