From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
David Sterba <dsterba@suse.cz>
Subject: Re: btrfs/058 deadlock with lseek
Date: Tue, 26 Nov 2019 17:56:27 +0800 [thread overview]
Message-ID: <b99618bc-1215-6c2d-5bdb-e43cb79cbd8e@gmx.com> (raw)
In-Reply-To: <3310d598-bd2f-6024-e5ac-c1c6080c0fd7@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 2054 bytes --]
On 2019/11/26 下午4:17, Qu Wenruo wrote:
> Hi guys,
>
> Just got a reproducible error in btrfs/058.
> The backtrace is completely in VFS territory, not btrfs related lock at all:
With the help of Nikolay and Johannes, the offending commit is pinned
down to 0be0ee71816b ("vfs: properly and reliably lock f_pos in
fdget_pos()"), and Linus will soon revert it.
Not a big deal, but testers would have a much easier life using David's
misc-5.5 (still based on v5.4-rc).
And to David, would you please keep your misc-5.5 branch until the
offending patch get reverted?
Thanks,
Qu
> BTRFS info (device dm-5): checking UUID tree
> sysrq: Show Blocked State
> task PC stack pid father
> rm D 0 560678 560445 0x00000000
> Call Trace:
> __schedule+0x5c7/0xea0
> ? __sched_text_start+0x8/0x8
> ? lock_downgrade+0x380/0x380
> ? lock_contended+0x730/0x730
> ? debug_check_no_locks_held+0x60/0x60
> schedule+0x7b/0x170
> schedule_preempt_disabled+0x18/0x30
> __mutex_lock+0x481/0xc70
> ? __fdget_pos+0x7e/0x80
> ? mutex_trylock+0x190/0x190
> ? debug_lockdep_rcu_enabled+0x26/0x40
> ? kmem_cache_free+0x157/0x3b0
> ? putname+0x73/0x80
> ? __ia32_sys_rmdir+0x30/0x30
> ? __check_object_size+0x134/0x1e6
> mutex_lock_nested+0x1b/0x20
> ? mutex_lock_nested+0x1b/0x20
> __fdget_pos+0x7e/0x80
> ksys_lseek+0x1d/0xf0
> __x64_sys_lseek+0x43/0x50
> do_syscall_64+0x79/0xe0
> entry_SYSCALL_64_after_hwframe+0x49/0xbe
> RIP: 0033:0x7f7518e5652b
> Code: Bad RIP value.
> RSP: 002b:00007ffead7508e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7518e5652b
> RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 00007f7518f267e0 R08: 0000000000000001 R09: 0000000000000001
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 0000000000000002 R14: 00007f7518f2be68 R15: 00007f7518f287e0
>
> Is this a known bug in VFS layer?
>
> Thanks,
> Qu
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-26 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 8:17 btrfs/058 deadlock with lseek Qu Wenruo
2019-11-26 9:56 ` Qu Wenruo [this message]
2019-11-26 14:58 ` David Sterba
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=b99618bc-1215-6c2d-5bdb-e43cb79cbd8e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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).