All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Paul E.McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [lkp-robot] [debugfs]  f3e7155d08: BUG:unable_to_handle_kernel
Date: Mon, 24 Apr 2017 14:36:15 +0800	[thread overview]
Message-ID: <20170424063615.GA15491@yexl-desktop> (raw)
In-Reply-To: <871ssj3r8l.fsf@gmail.com>

On 04/23, Nicolai Stange wrote:
>Hi Xiaolong,
>
>I'm encountering some difficulties running the reproducer, see below.
>Any help is very welcome!
>

Thanks for watching the report and trying the reproducer.

>
>On Tue, Apr 18 2017, kernel test robot wrote:
>
>> [   45.772683] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
><snip>
>> [   45.772697] IP: __debugfs_remove+0x5c/0xc0
>> [   45.772743] Call Trace:
>> [   45.772750]  debugfs_remove_recursive+0xd4/0x1e0
>> [   45.772758]  rpc_clnt_debugfs_unregister+0x19/0x30
>> [   45.772762]  rpc_client_register+0x18a/0x1c0
>> [   45.772765]  rpc_new_client+0x1de/0x2e0
>> [   45.772768]  rpc_create_xprt+0x58/0x170
>> [   45.772769]  rpc_create+0xea/0x1c0
>> [   45.772776]  nfs_create_rpc_client+0xe8/0x130
>> [   45.772814]  nfs4_init_client+0x7e/0x290 [nfsv4]
>> [   45.772820]  ? __radix_tree_replace+0x8a/0x140
>> [   45.772823]  ? radix_tree_iter_tag_clear+0x1c/0x20
>> [   45.772827]  ? __rpc_init_priority_wait_queue+0x81/0xb0
>> [   45.772830]  ? rpc_init_wait_queue+0x13/0x20
>> [   45.772847]  ? nfs4_alloc_client+0x1d2/0x1e0 [nfsv4]
><snip>
>> [ 45.772985] Code: 8b 7c 24 30 48 89 de e8 f3 28 e6 ff 48 89 df e8 3b
>> 22 e5 ff 4c 8b 63 78 48 c7 c2 20 d7 3b 82 48 c7 c6 e0 9f c9 81 49 8d
>> 7c 24 18 <41> c7 44 24 10 00 00 00 00 4d 8d 6c 24 10 e8 a1 b6 cc ff 49
>> 8d
>
>Ok, that's
>
>	41 c7 44 24 10 00 00 	movl   $0x0,0x10(%r12)
>
>which is probably the init_completion() in __debugfs_remove_file():
>
>	fsd = dentry->d_fsdata;
>	init_completion(&fsd->active_users_drained);
>
>This would mean that fsd == NULL and this can happen only if the dentry
>in question isn't a regular file but a symlink or whatever. So, an
>additional d_is_reg() is needed here. I'll fix this in the next
>iteration once I got the reproducer working.
>
>
>> To reproduce:
>>
>>         git clone https://github.com/01org/lkp-tests.git
>>         cd lkp-tests
>>         bin/lkp qemu -k <bzImage> job-script  # job-script is attached in this email
>>
>
>This gives
>
>  make: Entering directory '/home/nic/lkp-tests/bin/event'
>  gcc    -c -o wakeup.o wakeup.c
>  gcc   -o wakeup wakeup.o
>  rm -f wakeup.o
>  strip wakeup
>  make: Leaving directory '/home/nic/lkp-tests/bin/event'
>  cpio: root:lkp: invalid group
>  cpio: root:lkp: invalid group
>  cpio: root:lkp: invalid group
>  gzip: /home/nic/.lkp/cache/lkp-x86_64.cpio: No such file or directory
>  mv: cannot stat ‘/home/nic/.lkp/cache/lkp-x86_64.cpio.gz’: No such file or directory
>  mv: cannot stat ‘/home/nic/.lkp/cache/lkp-x86_64.cgz’: No such file or directory
>  result_root: /home/nic/.lkp//result/boot/1/vm-lkp-nex04-8G/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/f3e7155d085591ab58f0993ce633fea58c082b35/3
>  downloading initrds ...
>  /usr/bin/wget -q --local-encoding=UTF-8 --retry-connrefused --waitretry 1000 --tries 1000 https://github.com/0day-ci/lkp-qemu/raw/master/osimage/debian/debian-x86_64-2016-08-31.cgz -N -P /home/nic/.lkp/cache/osimage/debian
>  /usr/bin/wget -q --local-encoding=UTF-8 --retry-connrefused --waitretry 1000 --tries 1000 https://github.com/0day-ci/lkp-qemu/raw/master/osimage/deps/debian-x86_64-2016-08-31.cgz/lkp_2017-04-01.cgz -N -P /home/nic/.lkp/cache/osimage/deps/debian-x86_64-2016-08-31.cgz
>  Failed to download osimage/deps/debian-x86_64-2016-08-31.cgz/lkp_2017-04-01.cgz
>
>Manual download of that very last lkp_2017-04-01.cgz file results in a 404
>error. Please let me know if you need more details.

It's most likely we haven't upload the lkp_2017-04-01.cgz file to github.
I'll check it and get back to you later.

Thanks,
Xiaolong
>
>
>Thank you!
>
>Nicolai

WARNING: multiple messages have this Message-ID (diff)
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [debugfs] f3e7155d08: BUG:unable_to_handle_kernel
Date: Mon, 24 Apr 2017 14:36:15 +0800	[thread overview]
Message-ID: <20170424063615.GA15491@yexl-desktop> (raw)
In-Reply-To: <871ssj3r8l.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3745 bytes --]

On 04/23, Nicolai Stange wrote:
>Hi Xiaolong,
>
>I'm encountering some difficulties running the reproducer, see below.
>Any help is very welcome!
>

Thanks for watching the report and trying the reproducer.

>
>On Tue, Apr 18 2017, kernel test robot wrote:
>
>> [   45.772683] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
><snip>
>> [   45.772697] IP: __debugfs_remove+0x5c/0xc0
>> [   45.772743] Call Trace:
>> [   45.772750]  debugfs_remove_recursive+0xd4/0x1e0
>> [   45.772758]  rpc_clnt_debugfs_unregister+0x19/0x30
>> [   45.772762]  rpc_client_register+0x18a/0x1c0
>> [   45.772765]  rpc_new_client+0x1de/0x2e0
>> [   45.772768]  rpc_create_xprt+0x58/0x170
>> [   45.772769]  rpc_create+0xea/0x1c0
>> [   45.772776]  nfs_create_rpc_client+0xe8/0x130
>> [   45.772814]  nfs4_init_client+0x7e/0x290 [nfsv4]
>> [   45.772820]  ? __radix_tree_replace+0x8a/0x140
>> [   45.772823]  ? radix_tree_iter_tag_clear+0x1c/0x20
>> [   45.772827]  ? __rpc_init_priority_wait_queue+0x81/0xb0
>> [   45.772830]  ? rpc_init_wait_queue+0x13/0x20
>> [   45.772847]  ? nfs4_alloc_client+0x1d2/0x1e0 [nfsv4]
><snip>
>> [ 45.772985] Code: 8b 7c 24 30 48 89 de e8 f3 28 e6 ff 48 89 df e8 3b
>> 22 e5 ff 4c 8b 63 78 48 c7 c2 20 d7 3b 82 48 c7 c6 e0 9f c9 81 49 8d
>> 7c 24 18 <41> c7 44 24 10 00 00 00 00 4d 8d 6c 24 10 e8 a1 b6 cc ff 49
>> 8d
>
>Ok, that's
>
>	41 c7 44 24 10 00 00 	movl   $0x0,0x10(%r12)
>
>which is probably the init_completion() in __debugfs_remove_file():
>
>	fsd = dentry->d_fsdata;
>	init_completion(&fsd->active_users_drained);
>
>This would mean that fsd == NULL and this can happen only if the dentry
>in question isn't a regular file but a symlink or whatever. So, an
>additional d_is_reg() is needed here. I'll fix this in the next
>iteration once I got the reproducer working.
>
>
>> To reproduce:
>>
>>         git clone https://github.com/01org/lkp-tests.git
>>         cd lkp-tests
>>         bin/lkp qemu -k <bzImage> job-script  # job-script is attached in this email
>>
>
>This gives
>
>  make: Entering directory '/home/nic/lkp-tests/bin/event'
>  gcc    -c -o wakeup.o wakeup.c
>  gcc   -o wakeup wakeup.o
>  rm -f wakeup.o
>  strip wakeup
>  make: Leaving directory '/home/nic/lkp-tests/bin/event'
>  cpio: root:lkp: invalid group
>  cpio: root:lkp: invalid group
>  cpio: root:lkp: invalid group
>  gzip: /home/nic/.lkp/cache/lkp-x86_64.cpio: No such file or directory
>  mv: cannot stat ‘/home/nic/.lkp/cache/lkp-x86_64.cpio.gz’: No such file or directory
>  mv: cannot stat ‘/home/nic/.lkp/cache/lkp-x86_64.cgz’: No such file or directory
>  result_root: /home/nic/.lkp//result/boot/1/vm-lkp-nex04-8G/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/f3e7155d085591ab58f0993ce633fea58c082b35/3
>  downloading initrds ...
>  /usr/bin/wget -q --local-encoding=UTF-8 --retry-connrefused --waitretry 1000 --tries 1000 https://github.com/0day-ci/lkp-qemu/raw/master/osimage/debian/debian-x86_64-2016-08-31.cgz -N -P /home/nic/.lkp/cache/osimage/debian
>  /usr/bin/wget -q --local-encoding=UTF-8 --retry-connrefused --waitretry 1000 --tries 1000 https://github.com/0day-ci/lkp-qemu/raw/master/osimage/deps/debian-x86_64-2016-08-31.cgz/lkp_2017-04-01.cgz -N -P /home/nic/.lkp/cache/osimage/deps/debian-x86_64-2016-08-31.cgz
>  Failed to download osimage/deps/debian-x86_64-2016-08-31.cgz/lkp_2017-04-01.cgz
>
>Manual download of that very last lkp_2017-04-01.cgz file results in a 404
>error. Please let me know if you need more details.

It's most likely we haven't upload the lkp_2017-04-01.cgz file to github.
I'll check it and get back to you later.

Thanks,
Xiaolong
>
>
>Thank you!
>
>Nicolai

  reply	other threads:[~2017-04-24  6:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 14:54 deadlock in synchronize_srcu() in debugfs? Johannes Berg
2017-03-23 15:29 ` Johannes Berg
2017-03-24  8:56   ` Johannes Berg
2017-03-24  9:24     ` Johannes Berg
2017-03-24 17:45       ` Paul E. McKenney
2017-03-24 18:51         ` Johannes Berg
2017-03-24 19:33           ` Paul E. McKenney
2017-03-24 20:20             ` Paul E. McKenney
2017-03-27 11:18               ` Johannes Berg
2017-03-23 15:36 ` Nicolai Stange
2017-03-23 15:47   ` Johannes Berg
2017-03-27 11:36   ` Johannes Berg
2017-03-30  7:32     ` Nicolai Stange
2017-03-30  7:55       ` Johannes Berg
2017-03-30 10:27         ` Nicolai Stange
2017-03-30 11:11           ` Johannes Berg
2017-03-31  9:03             ` Nicolai Stange
2017-03-31  9:44               ` Johannes Berg
2017-04-16  9:51               ` [RFC PATCH 0/9] debugfs: per-file removal protection Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 1/9] debugfs: add support for more elaborate ->d_fsdata Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 2/9] debugfs: implement per-file removal protection Nicolai Stange
2017-04-18  2:23                   ` [lkp-robot] [debugfs] f3e7155d08: BUG:unable_to_handle_kernel kernel test robot
2017-04-18  2:23                     ` kernel test robot
2017-04-23 18:37                     ` Nicolai Stange
2017-04-23 18:37                       ` Nicolai Stange
2017-04-24  6:36                       ` Ye Xiaolong [this message]
2017-04-24  6:36                         ` Ye Xiaolong
2017-04-16  9:51                 ` [RFC PATCH 3/9] debugfs: debugfs_real_fops(): drop __must_hold sparse annotation Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 4/9] debugfs: convert to debugfs_file_get() and -put() Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 5/9] IB/hfi1: " Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 6/9] debugfs: purge obsolete SRCU based removal protection Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 7/9] debugfs: call debugfs_real_fops() only after debugfs_file_get() Nicolai Stange
2017-04-16  9:51                 ` [RFC PATCH 8/9] debugfs: defer debugfs_fsdata allocation to first usage Nicolai Stange
2017-04-18  9:36                   ` Johannes Berg
2017-05-02 20:05                     ` Nicolai Stange
2017-05-03  5:43                       ` Johannes Berg
2017-04-16  9:51                 ` [RFC PATCH 9/9] debugfs: free debugfs_fsdata instances Nicolai Stange
2017-04-17 16:01                   ` Paul E. McKenney
2017-04-18  9:39                     ` Johannes Berg
2017-04-18 13:31                       ` Paul E. McKenney
2017-04-18 13:40                         ` Johannes Berg
2017-04-18 15:17                           ` Paul E. McKenney
2017-04-18 15:20                             ` Johannes Berg
2017-04-18 17:19                               ` Paul E. McKenney
2017-03-23 15:37 ` deadlock in synchronize_srcu() in debugfs? Paul E. McKenney
2017-03-23 15:46   ` Johannes Berg

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=20170424063615.GA15491@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=nicstange@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.