From: William Dauchy <william@gandi.net>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Trond Myklebust <trond.myklebust@primarydata.com>,
jloup@gandi.net
Subject: extra reference to fl->fl_file, possible regression
Date: Fri, 10 Jul 2015 11:29:10 +0200 [thread overview]
Message-ID: <20150710092910.GI15144@gandi.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
Hello,
We have been testing the two following patches on top of the last 3.14.x.
(they have been queued up for stable releases)
commit db2efec0caba4f81a22d95a34da640b86c313c8e
Author: Jeff Layton <jlayton@poochiereds.net>
Date: Tue Jun 30 14:12:30 2015 -0400
nfs: take extra reference to fl->fl_file when running a LOCKU operation
commit feaff8e5b2cfc3eae02cf65db7a400b0b9ffc596
Author: Jeff Layton <jlayton@poochiereds.net>
Date: Tue May 12 15:48:10 2015 -0400
nfs: take extra reference to fl->fl_file when running a setlk
It resulted in random instabilities; we are unable to reproduce it reliably for now;
the only trace we got was the one below.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8 at kernel/rcu/tree.c:2191 rcu_do_batch.isra.51+0x384/0x3d0()
CPU: 0 PID: 8 Comm: rcuc/0 Not tainted 3.14 #1
0000000000000009 ffff88061e5dfd10 ffffffff815f5143 0000000000000000
ffff88061e5dfd48 ffffffff8105eece 000000000000002f ffff880627c0b600
000000000000002f 0000000000000246 0000000000000000 ffff88061e5dfd58
Call Trace:
[<ffffffff815f5143>] dump_stack+0x4d/0x81
[<ffffffff8105eece>] warn_slowpath_common+0x6e/0x90
[<ffffffff8105efd5>] warn_slowpath_null+0x15/0x20
[<ffffffff810bc634>] rcu_do_batch.isra.51+0x384/0x3d0
[<ffffffff810bc42a>] ? rcu_do_batch.isra.51+0x17a/0x3d0
[<ffffffff810bc9ed>] rcu_cpu_kthread+0xed/0x130
[<ffffffff8108aabe>] smpboot_thread_fn+0x18e/0x2e0
[<ffffffff8108a930>] ? in_egroup_p+0x40/0x40
[<ffffffff8108358c>] kthread+0xec/0x110
[<ffffffff810834a0>] ? __kthread_parkme+0x80/0x80
[<ffffffff815fcb39>] ret_from_fork+0x49/0x80
[<ffffffff810834a0>] ? __kthread_parkme+0x80/0x80
---[ end trace 27f9589ec4225b03 ]---
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-07-10 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 9:29 William Dauchy [this message]
2015-07-10 11:24 ` extra reference to fl->fl_file, possible regression Jeff Layton
2015-07-10 11:36 ` William Dauchy
2015-07-10 12:54 ` William Dauchy
2015-07-10 14:39 ` Jeff Layton
2015-07-10 15:06 ` William Dauchy
2015-07-10 15:18 ` 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=20150710092910.GI15144@gandi.net \
--to=william@gandi.net \
--cc=jlayton@poochiereds.net \
--cc=jloup@gandi.net \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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