On Wed, Sep 29, 2010 at 05:34:51PM +0200, Benny Halevy wrote: > On 2010-09-28 17:51, J. Bruce Fields wrote: > > On Tue, Sep 21, 2010 at 03:01:08PM -0400, J. Bruce Fields wrote: > >> On Tue, Sep 21, 2010 at 08:43:15PM +0200, Benny Halevy wrote: > >>> On 2010-09-21 18:42, J. Bruce Fields wrote: > >>>> I get the following on pnfs-all-latest, while doing a non-pnfs 4.1 mount. > >>> > >>> Bruce, can you please provide you .config file? > >>> >From the registers value it's possible the calldata is used > >>> after free... > >> > >> Yep. I ran a 'make oldconfig' on the appended and built from that. > >> > >> We've seen poisoning in trond's latest for-next as well. Which I don't > >> think you're including. But I'll add linux-nfs to the cc for that. > > > > By the way, nightly tests on pnfs code havn't been running due to lack > > of upstream writeback fixes: > > b76b4014f9d988d2412b873e4d4c13c7f9afc4e4 > > and > > 6628bc74f1aa9c35dd386320bf7ec04f12edb1b3 > > > > (both in -rc4, I believe). > > > > --b. > > OK, now that I've rebased onto -rc6 they should be there. Thanks. Looks like v4 is happier now, but v4.1 mounts fail with -EIO. (That's on pnfs-all-latest; pnfs-submit is OK.) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
