From: Sedat Dilek <sedat.dilek@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Alfredo Alvarez Fernandez <alfredoalvarezfernandez@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260
Date: Wed, 30 Mar 2016 11:36:31 +0200 [thread overview]
Message-ID: <CA+icZUUtAGhgWPGZDdPWijNE3TqeRU3haRc7tP4X9WiEKsYLgQ@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUqDxwf8eEXfdB_ESAUXt0dcbvO4ByukRDfirPCLnwhFQ@mail.gmail.com>
> [ 0.000000] -------------------------------------------------------
> [ 0.000000] Good, all 253 testcases passed! |
> [ 0.000000] ---------------------------------
>
> And it's all good?
> ( On shutdown I saw an(other) issue - will investigate, might not be related. )
>
The initial reported issue is hard but reproducible.
Mar 30 08:26:52 fambox kernel: [ 683.309212] ------------[ cut here
]------------
Mar 30 08:26:52 fambox kernel: [ 683.309221] WARNING: CPU: 3 PID:
10090 at kernel/locking/lockdep.c:2023 __lock_acquire+0x147a/0x2260
Mar 30 08:26:52 fambox kernel: [ 683.309223]
DEBUG_LOCKS_WARN_ON(chain_hlocks[chain->base + j] != id)
Mar 30 08:26:52 fambox kernel: [ 683.309225] Modules linked in: btrfs
xor raid6_pq ntfs xfs libcrc32c ppp_deflate bsd_comp ppp_async
crc_ccitt option usb_wwan cdc_ether usbserial usbnet arc4 iwldvm
mac80211 bnep rfcomm i915 uvcvideo snd_hda_codec_hdmi
snd_hda_codec_realtek videobuf2_vmalloc kvm_intel
snd_hda_codec_generic videobuf2_memops videobuf2_v4l2 snd_hda_intel
videobuf2_core kvm snd_hda_codec joydev videodev usb_storage
parport_pc ppdev snd_hwdep btusb snd_hda_core btrtl i2c_algo_bit
snd_pcm irqbypass btbcm iwlwifi drm_kms_helper psmouse btintel
snd_seq_midi bluetooth syscopyarea snd_seq_midi_event sysfillrect
snd_rawmidi serio_raw samsung_laptop sysimgblt snd_seq fb_sys_fops
snd_timer cfg80211 drm snd_seq_device snd soundcore wmi mac_hid video
intel_rst lpc_ich lp parport binfmt_misc hid_generic usbhid hid r8169
mii
Mar 30 08:26:52 fambox kernel: [ 683.309283] CPU: 3 PID: 10090 Comm:
mv Not tainted 4.6.0-rc1-4-iniza-small #1
Mar 30 08:26:52 fambox kernel: [ 683.309285] Hardware name: SAMSUNG
ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH,
BIOS 13XK 03/28/2013
Mar 30 08:26:52 fambox kernel: [ 683.309287] 0000000000000000
ffff8800330af5d0 ffffffff81411c25 ffff8800330af620
Mar 30 08:26:52 fambox kernel: [ 683.309290] 0000000000000000
ffff8800330af610 ffffffff81083db1 000007e7330af610
Mar 30 08:26:52 fambox kernel: [ 683.309293] ffff880109059300
0000000000000000 0000000000000004 31419e23b49ae8f8
Mar 30 08:26:52 fambox kernel: [ 683.309296] Call Trace:
Mar 30 08:26:52 fambox kernel: [ 683.309301] [<ffffffff81411c25>]
dump_stack+0x85/0xc0
Mar 30 08:26:52 fambox kernel: [ 683.309304] [<ffffffff81083db1>]
__warn+0xd1/0xf0
Mar 30 08:26:52 fambox kernel: [ 683.309307] [<ffffffff81083e1f>]
warn_slowpath_fmt+0x4f/0x60
Mar 30 08:26:52 fambox kernel: [ 683.309309] [<ffffffff810dec8a>]
__lock_acquire+0x147a/0x2260
Mar 30 08:26:52 fambox kernel: [ 683.309312] [<ffffffff810e0709>]
lock_acquire+0x119/0x220
Mar 30 08:26:52 fambox kernel: [ 683.309316] [<ffffffff8131dc05>] ?
do_get_write_access+0x3a5/0x5d0
Mar 30 08:26:52 fambox kernel: [ 683.309319] [<ffffffff8180d188>]
_raw_spin_lock+0x38/0x50
Mar 30 08:26:52 fambox kernel: [ 683.309322] [<ffffffff8131dc05>] ?
do_get_write_access+0x3a5/0x5d0
Mar 30 08:26:52 fambox kernel: [ 683.309324] [<ffffffff8131dc05>]
do_get_write_access+0x3a5/0x5d0
Mar 30 08:26:52 fambox kernel: [ 683.309327] [<ffffffff8131de63>]
jbd2_journal_get_write_access+0x33/0x60
Mar 30 08:26:52 fambox kernel: [ 683.309331] [<ffffffff812ff25e>]
__ext4_journal_get_write_access+0x4e/0x90
Mar 30 08:26:52 fambox kernel: [ 683.309334] [<ffffffff8130665d>]
ext4_mb_mark_diskspace_used+0x6d/0x470
Mar 30 08:26:52 fambox kernel: [ 683.309336] [<ffffffff81307f68>]
ext4_mb_new_blocks+0x3e8/0x840
Mar 30 08:26:52 fambox kernel: [ 683.309338] [<ffffffff812f6807>] ?
ext4_find_extent+0x1b7/0x320
Mar 30 08:26:52 fambox kernel: [ 683.309340] [<ffffffff810db9c9>] ?
__lock_is_held+0x49/0x70
Mar 30 08:26:52 fambox kernel: [ 683.309343] [<ffffffff812fb1b5>]
ext4_ext_map_blocks+0xab5/0x2100
Mar 30 08:26:52 fambox kernel: [ 683.309348] [<ffffffff812ca45c>]
ext4_map_blocks+0x10c/0x510
Mar 30 08:26:52 fambox kernel: [ 683.309350] [<ffffffff810db9c9>] ?
__lock_is_held+0x49/0x70
Mar 30 08:26:52 fambox kernel: [ 683.309353] [<ffffffff812ce093>]
ext4_writepages+0x723/0x1010
Mar 30 08:26:52 fambox kernel: [ 683.309356] [<ffffffff8180d377>] ?
_raw_spin_unlock+0x27/0x40
Mar 30 08:26:52 fambox kernel: [ 683.309359] [<ffffffff811bb221>]
do_writepages+0x21/0x30
Mar 30 08:26:52 fambox kernel: [ 683.309362] [<ffffffff811abb5a>]
__filemap_fdatawrite_range+0xaa/0xf0
Mar 30 08:26:52 fambox kernel: [ 683.309365] [<ffffffff811abc4c>]
filemap_flush+0x1c/0x20
Mar 30 08:26:52 fambox kernel: [ 683.309368] [<ffffffff812cb4a3>]
ext4_alloc_da_blocks+0x43/0x130
Mar 30 08:26:52 fambox kernel: [ 683.309370] [<ffffffff812db0b1>]
ext4_rename+0x6a1/0x8f0
Mar 30 08:26:52 fambox kernel: [ 683.309372] [<ffffffff810dd24d>] ?
mark_held_locks+0x6d/0x90
Mar 30 08:26:52 fambox kernel: [ 683.309374] [<ffffffff8180981f>] ?
mutex_lock_nested+0x25f/0x3d0
Mar 30 08:26:52 fambox kernel: [ 683.309377] [<ffffffff812db31d>]
ext4_rename2+0x1d/0x30
Mar 30 08:26:52 fambox kernel: [ 683.309379] [<ffffffff812428e1>]
vfs_rename+0x601/0x900
Mar 30 08:26:52 fambox kernel: [ 683.309383] [<ffffffff81371500>] ?
security_path_rename+0x70/0xd0
Mar 30 08:26:52 fambox kernel: [ 683.309386] [<ffffffff81247c78>]
SyS_rename+0x398/0x3b0
Mar 30 08:26:52 fambox kernel: [ 683.309389] [<ffffffff8180dc00>]
entry_SYSCALL_64_fastpath+0x23/0xc1
Mar 30 08:26:52 fambox kernel: [ 683.309391] ---[ end trace
7dacba969839f82f ]---
- Sedat -
next prev parent reply other threads:[~2016-03-30 9:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 8:15 [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 Sedat Dilek
2016-03-27 8:57 ` Sedat Dilek
2016-03-27 12:03 ` Linus Torvalds
2016-03-27 13:32 ` Boqun Feng
2016-03-27 18:23 ` Theodore Ts'o
2016-03-27 19:40 ` Sedat Dilek
[not found] ` <CA+55aFwoKRpgq8OCTxUaP+8gOg-mnN3nbruYgiK32a=C5U4TkQ@mail.gmail.com>
2016-03-27 20:24 ` Sedat Dilek
2016-03-27 20:48 ` Peter Zijlstra
2016-03-27 20:59 ` Sedat Dilek
2016-03-27 21:48 ` Sedat Dilek
2016-03-28 1:05 ` Boqun Feng
2016-03-28 6:33 ` Peter Zijlstra
2016-03-29 8:47 ` Ingo Molnar
2016-03-30 9:20 ` Sedat Dilek
2016-03-30 9:36 ` Sedat Dilek [this message]
2016-03-30 9:36 ` Peter Zijlstra
2016-03-30 9:49 ` Sedat Dilek
2016-03-30 10:33 ` Sedat Dilek
2016-03-30 12:43 ` Peter Zijlstra
2016-03-30 12:46 ` Sedat Dilek
2016-03-30 13:15 ` Peter Zijlstra
2016-03-30 9:50 ` Peter Zijlstra
2016-03-30 9:59 ` Boqun Feng
2016-03-30 10:36 ` Peter Zijlstra
2016-03-30 11:07 ` Sedat Dilek
2016-03-31 15:42 ` Peter Zijlstra
2016-03-31 15:52 ` Boqun Feng
2016-04-02 6:26 ` Sedat Dilek
2016-03-30 14:06 ` Peter Zijlstra
2016-03-30 15:21 ` Sedat Dilek
2016-03-30 17:03 ` [PATCH] lockdep: print chain_key collision information Alfredo Alvarez Fernandez
2016-03-30 17:19 ` Peter Zijlstra
2016-04-01 6:36 ` [tip:core/urgent] locking/lockdep: Print " tip-bot for Alfredo Alvarez Fernandez
2016-05-10 9:09 ` Peter Zijlstra
2016-04-04 15:31 ` [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 Sedat Dilek
2016-04-04 16:02 ` Peter Zijlstra
2016-05-09 11:37 ` Sedat Dilek
2016-06-03 15:15 ` Sedat Dilek
2016-04-23 12:54 ` [tip:locking/urgent] lockdep: Fix lock_chain::base size tip-bot for Peter Zijlstra
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=CA+icZUUtAGhgWPGZDdPWijNE3TqeRU3haRc7tP4X9WiEKsYLgQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=alfredoalvarezfernandez@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).