[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87aaed23s1.fsf@tucsk.pomaz.szeredi.hu>
Date: Mon, 23 May 2011 10:57:02 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Erez Zadok <ezk@....cs.sunysb.edu>
Cc: "viro\@ZenIV.linux.org.uk" <viro@...IV.linux.org.uk>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
"apw\@canonical.com" <apw@...onical.com>,
"nbd\@openwrt.org" <nbd@...nwrt.org>,
"neilb\@suse.de" <neilb@...e.de>,
"hramrach\@centrum.cz" <hramrach@...trum.cz>,
"jordipujolp\@gmail.com" <jordipujolp@...il.com>
Subject: Re: [PATCH 5/7] overlay filesystem (inode.c bad error path)
Erez Zadok <ezk@....cs.sunysb.edu> writes:
> Done: reverted my ovl patches and applied yours. And indeed, the NULL
> oopses don't show up after 10 minutes of running. Just to be sure, I
> ran overlayfs on top of ext2, ext3, xfs, reiserfs, and tmps — no
> oopses. And I wasn't able to reproduce the WARN_ON in ovl_permission.
Great, thanks for testing. Pushed to .v9 branch.
> Are you interested in testing overlayfs on top of NFS at this time?
No, not as an upper layer. NFS as a lower layer should work fine.
Thanks,
Miklos
--
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