[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3d0904116ed2fa7e4fe8bb6f383534c5@lycos.com>
Date: Mon, 21 Dec 2015 12:31:06 +0500
From: "Artem S. Tashkinov" <t.artem@...os.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ming Lei <tom.leiming@...il.com>,
Kent Overstreet <kent.overstreet@...il.com>,
Christoph Hellwig <hch@....de>,
Ming Lin <ming.l@....samsung.com>, Jens Axboe <axboe@...com>,
"Artem S. Tashkinov" <t.artem@...lcity.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Tejun Heo <tj@...nel.org>, IDE-ML <linux-ide@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linus971@...il.com
Subject: Re: IO errors after "block: remove bio_get_nr_vecs()"
On 2015-12-21 10:23, Linus Torvalds wrote:
> On Sun, Dec 20, 2015 at 8:47 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> 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 ..
>
Let's wait for what Tejun Heo might say - I've applied his debugging
patch and sent back the results.
Building x86_64 kernel here involves installing a 64bit Linux VM, so I'd
like it to be the last resort.
--
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