Re: xfs failure on parisc (and presumably other VI cache systems) caused by I/O to vmalloc/vmap areas

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: James Bottomley <James.Bottomley@xxxxxxx>
Subject: Re: xfs failure on parisc (and presumably other VI cache systems) caused by I/O to vmalloc/vmap areas
From: Christoph Hellwig <hch@xxxxxx>
Date: Tue, 13 Oct 2009 03:40:40 +0200
Cc: Parisc List <linux-parisc@xxxxxxxxxxxxxxx>, Linux Filesystem Mailing List <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-arch@xxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>
In-reply-to: <1252434469.13003.3.camel@xxxxxxxxxxxxx>
User-agent: Mutt/1.3.28i

So what's going to happen with this patch series?  Can we expect it to
get merged one day?

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: xfs failure on parisc (and presumably other VI cache systems) caused by I/O to vmalloc/vmap areas
  - From: James Bottomley

References:
- xfs failure on parisc (and presumably other VI cache systems) caused by I/O to vmalloc/vmap areas
  - From: James Bottomley

Prev by Date: Re: [rfc][patch] store-free path walking
Next by Date: Re: [rfc][patch] store-free path walking
Previous by thread: [PATCH 5/5] xfs: fix xfs to work with Virtually Indexed architectures
Next by thread: Re: xfs failure on parisc (and presumably other VI cache systems) caused by I/O to vmalloc/vmap areas
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux