Re: WARN_ON_ONCE pop with tip of your nfsd-next branch

[Jeff Layton <jeff.layton@primarydata.com>]

On Sun, 8 Jun 2014 14:44:36 -0400
"J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Sun, Jun 08, 2014 at 01:17:23PM -0400, J. Bruce Fields wrote:
> > On Sat, Jun 07, 2014 at 09:51:09PM -0400, Jeff Layton wrote:
> > > Hi Bruce,
> > > 
> > > Just a heads up...
> > > 
> > > Was doing some testing with a pile of patches (mostly v4 state-related)
> > > on top of your nfsd-next branch, and saw this pop:
> > 
> > Do you know exactly was the commit id of the last commit from my branch?
> 
> Also, do you remember what sort of testing it was?
> 
> --b.

The tip was at a676de9e22b4c13c8d4a27289b1f2bcf35dce6dd. It looks like
maybe you rebased at some point though and now the commit IDs are
different? To make it pop, I ran fsstress on a v4.1 mount. I think it
was these options:

    $ fsstress -d <dir> -n 1000 -p 128

I'll see if I can make it happen again when I have some time for more
testing.

Thanks,
-- 
Jeff Layton <jlayton@primarydata.com>