From: Sasha Levin <sasha.levin@oracle.com>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: fs: locks: WARNING: CPU: 16 PID: 4296 at fs/locks.c:236 locks_free_lock_context+0x10d/0x240()
Date: Fri, 16 Jan 2015 09:31:23 -0500 [thread overview]
Message-ID: <54B920BB.3010205@oracle.com> (raw)
In-Reply-To: <20150115152247.5e660000@tlielax.poochiereds.net>
On 01/15/2015 03:22 PM, Jeff Layton wrote:
> Ok, I tried to reproduce it with that and several variations but it
> still doesn't seem to do it for me. Can you try the latest linux-next
> tree and see if it's still reproducible there?
It's still not in in today's -next, could you send me a patch for testing
instead?
Thanks,
Sasha
next prev parent reply other threads:[~2015-01-16 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:11 fs: locks: WARNING: CPU: 16 PID: 4296 at fs/locks.c:236 locks_free_lock_context+0x10d/0x240() Sasha Levin
2015-01-13 13:20 ` Jeff Layton
2015-01-13 13:25 ` Sasha Levin
2015-01-13 21:44 ` Jeff Layton
2015-01-13 22:50 ` Sasha Levin
2015-01-13 23:32 ` Jeff Layton
2015-01-14 14:27 ` Jeff Layton
2015-01-14 23:44 ` Sasha Levin
2015-01-15 2:26 ` Jeff Layton
2015-01-15 20:22 ` Jeff Layton
2015-01-16 14:31 ` Sasha Levin [this message]
2015-01-16 14:40 ` Jeff Layton
2015-01-16 18:10 ` Sasha Levin
2015-01-16 18:53 ` Jeff Layton
2015-01-16 21:16 ` Jeff Layton
2015-01-16 21:20 ` Sasha Levin
2015-01-21 13:25 ` Sasha Levin
2015-01-21 13:33 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B920BB.3010205@oracle.com \
--to=sasha.levin@oracle.com \
--cc=jeff.layton@primarydata.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).