| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Dec 2018 18:21:42 +0800
From: kernel test robot <rong.a.chen@...el.com>
To: Eric Biggers <ebiggers@...gle.com>
Cc: Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, LKP <lkp@...org>
Subject: [LKP] acc9eb0a60 [ 76.294850] WARNING: possible circular locking
dependency detected
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit acc9eb0a607300be08639fd4449bf51225239c7d
Author: Eric Biggers <ebiggers@...gle.com>
AuthorDate: Thu Nov 1 15:52:29 2018 -0700
Commit: Theodore Ts'o <tytso@....edu>
CommitDate: Wed Nov 28 18:09:25 2018 -0500
ext4: add fs-verity read support
Make ext4_mpage_readpages() verify data as it is read from fs-verity
files, using the helper functions from fs/verity/.
To be compatible with fscrypt, like in the corresponding f2fs patch this
required refactoring the decryption workflow into a generic "post-read
processing" workflow, which can do decryption, verification, or both.
Co-developed-by: Theodore Ts'o <tytso@....edu>
Signed-off-by: Theodore Ts'o <tytso@....edu>
Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Signed-off-by: Theodore Ts'o <tytso@....edu>
bff49d3e9a ext4: add basic fs-verity support
acc9eb0a60 ext4: add fs-verity read support
285053b5a4 Add linux-next specific files for 20181218
+-------------------------------------------------------+------------+------------+---------------+
| | bff49d3e9a | acc9eb0a60 | next-20181218 |
+-------------------------------------------------------+------------+------------+---------------+
| boot_successes | 45 | 10 | 6 |
| boot_failures | 1 | 11 | 11 |
| RIP:strncpy_from_user | 1 | | |
| Mem-Info | 1 | 1 | |
| WARNING:possible_circular_locking_dependency_detected | 0 | 10 | 11 |
| invoked_oom-killer:gfp_mask=0x | 0 | 1 | |
| WARNING:at_kernel/locking/lockdep.c:#lock_downgrade | 0 | 2 | 2 |
| RIP:lock_downgrade | 0 | 1 | 2 |
+-------------------------------------------------------+------------+------------+---------------+
[child1:862] vm86 (166:[32BIT]) returned ENOSYS, marking as inactive.
[child1:862] acct (51:[32BIT]) returned ENOSYS, marking as inactive.
[ 72.903984] VFS: Warning: trinity-c2 using old stat() call. Recompile your binary.
[ 76.274082]
[ 76.279556] ======================================================
[ 76.294850] WARNING: possible circular locking dependency detected
[ 76.310053] 4.20.0-rc4-00022-gacc9eb0 #1 Not tainted
[ 76.319011] ------------------------------------------------------
[ 76.328475] trinity-c1/894 is trying to acquire lock:
[ 76.336320] (____ptrval____) (slab_mutex){+.+.}, at: slab_attr_store+0x59/0xcb
[ 76.347769]
[ 76.347769] but task is already holding lock:
[ 76.357140] (____ptrval____) (kn->count#39){++++}, at: kernfs_fop_write+0xc2/0x148
[ 76.368828]
[ 76.368828] which lock already depends on the new lock.
[ 76.368828]
[ 76.381855]
[ 76.381855] the existing dependency chain (in reverse order) is:
[ 76.393371]
[ 76.393371] -> #1 (kn->count#39){++++}:
[ 76.402088] kernfs_remove_by_name_ns+0x54/0x6d
[ 76.409899] sysfs_slab_add+0xde/0x239
[ 76.416774] __kmem_cache_create+0xd9/0xfc
[ 76.424126] create_cache+0x132/0x170
[ 76.430840] kmem_cache_create_usercopy+0x19c/0x1e7
[ 76.439230] kmem_cache_create+0xd/0xf
[ 76.446230] f2fs_init_post_read_processing+0x1b/0x69
[ 76.454683] init_f2fs_fs+0xa4/0xf9
[ 76.461192] do_one_initcall+0xc2/0x223
[ 76.468272] kernel_init_freeable+0x1d6/0x260
[ 76.475985] kernel_init+0x5/0xeb
[ 76.482272] ret_from_fork+0x24/0x30
[ 76.488975]
[ 76.488975] -> #0 (slab_mutex){+.+.}:
[ 76.497533] __mutex_lock+0x7e/0x37a
[ 76.504174] slab_attr_store+0x59/0xcb
[ 76.511138] kernfs_fop_write+0xff/0x148
[ 76.518415] __vfs_write+0x1c/0xa2
[ 76.524769] vfs_write+0xad/0xd6
[ 76.630277] ksys_write+0x4b/0x79
[ 76.636749] do_syscall_64+0x54/0x62
[ 76.643389] entry_SYSCALL_64_after_hwframe+0x49/0xbe
[ 76.652053]
[ 76.652053] other info that might help us debug this:
[ 76.652053]
[ 76.664818] Possible unsafe locking scenario:
[ 76.664818]
[ 76.674442] CPU0 CPU1
[ 76.681673] ---- ----
[ 76.688839] lock(kn->count#39);
[ 76.716415] lock(slab_mutex);
[ 76.725218] lock(kn->count#39);
[ 76.734094] lock(slab_mutex);
[ 76.739445]
[ 76.739445] *** DEADLOCK ***
[ 76.739445]
[ 76.749627] 4 locks held by trinity-c1/894:
[ 76.756341] #0: (____ptrval____) (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x31/0x37
[ 76.768140] #1: (____ptrval____) (sb_writers#5){.+.+}, at: vfs_write+0x8f/0xd6
[ 76.779479] #2: (____ptrval____) (&of->mutex){+.+.}, at: kernfs_fop_write+0xb9/0x148
[ 76.791501] #3: (____ptrval____) (kn->count#39){++++}, at: kernfs_fop_write+0xc2/0x148
[ 76.804124]
[ 76.804124] stack backtrace:
[ 76.811660] CPU: 1 PID: 894 Comm: trinity-c1 Not tainted 4.20.0-rc4-00022-gacc9eb0 #1
[ 76.823761] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[ 76.836396] Call Trace:
[ 76.840872] dump_stack+0x5e/0x84
[ 76.846647] print_circular_bug+0x1c7/0x1d4
[ 76.854295] __lock_acquire+0xc5a/0xf41
[ 76.860710] ? check_chain_key+0x78/0xc1
[ 76.867359] ? lock_acquire+0x11c/0x17b
[ 76.873707] lock_acquire+0x11c/0x17b
[ 76.879739] ? slab_attr_store+0x59/0xcb
[ 76.886234] __mutex_lock+0x7e/0x37a
[ 76.892199] ? slab_attr_store+0x59/0xcb
[ 76.898660] ? __mutex_lock+0x86/0x37a
[ 76.904873] ? slab_attr_store+0x59/0xcb
[ 76.911409] ? __lock_is_held+0x40/0x71
[ 76.917711] ? slab_attr_store+0x59/0xcb
[ 76.924089] slab_attr_store+0x59/0xcb
[ 76.930468] kernfs_fop_write+0xff/0x148
[ 76.936993] __vfs_write+0x1c/0xa2
[ 76.942752] ? rcu_read_lock_sched_held+0x58/0x5e
[ 76.950243] ? rcu_sync_lockdep_assert+0x23/0x49
[ 76.957573] ? __sb_start_write+0x128/0x157
[ 76.964382] ? vfs_write+0x8f/0xd6
[ 76.970195] vfs_write+0xad/0xd6
[ 76.975703] ksys_write+0x4b/0x79
[ 76.981433] do_syscall_64+0x54/0x62
[ 76.987428] entry_SYSCALL_64_after_hwframe+0x49/0xbe
[ 76.995386] RIP: 0033:0x457389
[ 77.000891] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 2b 84 00 00 c3 66 2e 0f 1f 84 00 00 00 00
[ 77.027760] RSP: 002b:00007ffff4980f98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 77.039498] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000000000457389
[ 77.050042] RDX: 0000000000000afd RSI: 0000000002c0cfb0 RDI: 0000000000000055
[ 77.060535] RBP: 00007ffff4981040 R08: fffffffffffffff7 R09: 000000000000003d
[ 77.071050] R10: 00000000000000b4 R11: 0000000000000246 R12: 0000000000000002
[ 77.081588] R13: 00007fa257ca8058 R14: 00000000028c7830 R15: 00007fa257ca8000
[child1:894] kcmp (349:[32BIT]) returned ENOSYS, marking as inactive.
BusyBox v1.19.4 (2012-04-22 08:49:11 PDT) multi-call binary.
# HH:MM RESULT GOOD BAD GOOD_BUT_DIRTY DIRTY_NOT_BAD
git bisect start 285053b5a4c0204840fb92cfaba06352718e2eed 7566ec393f4161572ba6f11ad5171fd5d59b0fbd --
git bisect bad 88bbac9a05685ee52454b7805c8f0d44383b5c91 # 01:42 B 0 2 17 0 Merge remote-tracking branch 'ieee1394/for-next'
git bisect good 2c49a9ccbf72d7d10c31e2b834df0807b8243413 # 02:02 G 17 0 7 7 Merge remote-tracking branch 'samsung-krzk/for-next'
git bisect bad 9848e584efb4265ec368b27727bf935fe2f394eb # 02:12 B 0 1 16 0 Merge remote-tracking branch 'ext4/dev'
git bisect good c13559eda3e569671267ce120f80879d66d7f58c # 02:34 G 16 0 3 3 Merge remote-tracking branch 'parisc-hd/for-next'
git bisect bad 70c4cd6a639a51bd1c7974db16fcc20589896630 # 02:47 B 0 2 17 0 Merge remote-tracking branch 'fscrypt/master'
git bisect good e2c8659b744c86f723497b6fcad33a014b2044b8 # 03:17 G 17 0 3 3 Merge remote-tracking branch 's390/features'
git bisect good 5c31d40d1968118bc17f572487b7274ff51cef8c # 03:36 G 16 0 5 5 Merge remote-tracking branch 'sparc-next/master'
git bisect good 8f916e7c561872d65ff93932b011c57ad686c4ed # 03:56 G 17 0 1 1 Merge remote-tracking branch 'xtensa/xtensa-for-next'
git bisect good 0c9ff58d6b2c795225531c6d5e12fd3e4eaffa03 # 04:19 G 17 0 2 2 fs-verity: support builtin file signatures
git bisect bad f3fd6cd74fedf99b6060f75df00943fda13b65f2 # 04:40 B 1 8 0 0 fscrypt: remove filesystem specific build config option
git bisect bad 50ee9e5d8e3ef15fc4bed781df9a6b2f708230ff # 05:06 B 0 6 21 0 f2fs: fs-verity support
git bisect bad acc9eb0a607300be08639fd4449bf51225239c7d # 05:39 B 7 10 1 1 ext4: add fs-verity read support
git bisect good bff49d3e9affae6f9e38a9103a4166ade2c310dd # 06:09 G 16 0 0 0 ext4: add basic fs-verity support
# first bad commit: [acc9eb0a607300be08639fd4449bf51225239c7d] ext4: add fs-verity read support
git bisect good bff49d3e9affae6f9e38a9103a4166ade2c310dd # 06:12 G 50 0 7 7 ext4: add basic fs-verity support
# extra tests with debug options
git bisect bad acc9eb0a607300be08639fd4449bf51225239c7d # 06:37 B 0 6 21 0 ext4: add fs-verity read support
# extra tests on HEAD of linux-next/master
git bisect bad 285053b5a4c0204840fb92cfaba06352718e2eed # 06:38 B 1 11 0 0 Add linux-next specific files for 20181218
# extra tests on tree/branch linux-next/master
git bisect bad 285053b5a4c0204840fb92cfaba06352718e2eed # 06:38 B 1 11 0 0 Add linux-next specific files for 20181218
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/lkp Intel Corporation
Download attachment "dmesg-yocto-vm-yocto-236:20181219053930:x86_64-randconfig-u0-12181957:4.20.0-rc4-00022-gacc9eb0:1.gz" of type "application/gzip" (16544 bytes)
Download attachment "dmesg-yocto-vm-yocto-114:20181219060955:x86_64-randconfig-u0-12181957:4.20.0-rc4-00021-gbff49d3:2.gz" of type "application/gzip" (27816 bytes)
View attachment "reproduce-yocto-vm-yocto-236:20181219053930:x86_64-randconfig-u0-12181957:4.20.0-rc4-00022-gacc9eb0:1" of type "text/plain" (922 bytes)
View attachment "config-4.20.0-rc4-00022-gacc9eb0" of type "text/plain" (141037 bytes)
Powered by blists - more mailing lists