All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang\, Ying" <ying.huang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Cc: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
	linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
	Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
	kernel test robot
	<xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	lkp-JC7UmRfGjtg@public.gmane.org
Subject: Re: [LKP] [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c
Date: Tue, 13 Dec 2016 09:27:51 +0800	[thread overview]
Message-ID: <87mvg08voo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20161212163518.GA20728-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org> (Jan Kara's message of "Mon, 12 Dec 2016 17:35:18 +0100")

Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org> writes:

> On Mon 12-12-16 18:13:21, kernel test robot wrote:
>> FYI, we noticed the following commit:
>> 
>> commit: e2ae766c1b030271b5099b25674e2131d1d1e8c1 ("ext4: convert DAX faults to iomap infrastructure")
>> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
>> 
>> in testcase: nvml
>> with following parameters:
>> 
>> 	group: vmem
>> 	test: pmem
>> 	nr_pmem: 1
>> 	fs: ext4
>> 	mount_option: dax
>> 
>> 
>> 
>> on test machine: 64 threads Intel(R) Xeon(R) CPU E5-4650 0 @ 2.70GHz with 64G memory
>> 
>> caused below changes:
>> 
>> 
>> +------------------------------------------------+------------+------------+
>> |                                                | 96f8ba3dd6 | e2ae766c1b |
>> +------------------------------------------------+------------+------------+
>> | boot_successes                                 | 2          | 2          |
>> | boot_failures                                  | 2          | 2          |
>> | BUG:kernel_hang_in_test_stage                  | 2          |            |
>> | WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup      | 0          | 2          |
>> | calltrace:parport_pc_init                      | 0          | 2          |
>> | calltrace:SyS_finit_module                     | 0          | 2          |
>> | WARNING:at_lib/kobject.c:#kobject_add_internal | 0          | 2          |
>> +------------------------------------------------+------------+------------+
>> 
>> 
>> 
>> user  :notice: [  325.592182] vmem_aligned_alloc/TEST1: SETUP (check/pmem/debug)
>> 
>> user  :notice: [  325.603973] vmem_aligned_alloc/TEST1: START: vmem_aligned_alloc
>> kern  :err   : [  325.608906] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:51
>> kern  :err   : [  325.608908] in_atomic(): 1, irqs_disabled(): 0, pid: 24813, name: vmem_aligned_al
>> kern  :warn  : [  325.608914] CPU: 44 PID: 24813 Comm: vmem_aligned_al Tainted: G           O    4.9.0-rc4-00045-ge2ae766 #1
>> kern  :warn  : [  325.608916] Hardware name: Intel Corporation LH Pass/S4600LH...., BIOS SE5C600.86B.99.02.1047.032320122259 03/23/2012
>> kern  :warn  : [  325.608922]  ffffc9002c1f7be0
>> kern  :warn  : [  325.608923]  ffffffff81466af9
>> kern  :warn  : [  325.608924]  ffff880fea2425c0
>
> I think this is actually a bug introduced by Ross' PMD support. Attached
> patch should fix it. Ross, can you check it please?

Hi, Jan

Could you provide a git tree commit for me to test it?  If you want it
to be tested by 0day.

Best Regards,
Huang, Ying

> 								Honza

WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
	linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
	kernel test robot <xiaolong.ye@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, lkp@01.org
Subject: Re: [LKP] [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c
Date: Tue, 13 Dec 2016 09:27:51 +0800	[thread overview]
Message-ID: <87mvg08voo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20161212163518.GA20728@quack2.suse.cz> (Jan Kara's message of "Mon, 12 Dec 2016 17:35:18 +0100")

Jan Kara <jack@suse.cz> writes:

> On Mon 12-12-16 18:13:21, kernel test robot wrote:
>> FYI, we noticed the following commit:
>> 
>> commit: e2ae766c1b030271b5099b25674e2131d1d1e8c1 ("ext4: convert DAX faults to iomap infrastructure")
>> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
>> 
>> in testcase: nvml
>> with following parameters:
>> 
>> 	group: vmem
>> 	test: pmem
>> 	nr_pmem: 1
>> 	fs: ext4
>> 	mount_option: dax
>> 
>> 
>> 
>> on test machine: 64 threads Intel(R) Xeon(R) CPU E5-4650 0 @ 2.70GHz with 64G memory
>> 
>> caused below changes:
>> 
>> 
>> +------------------------------------------------+------------+------------+
>> |                                                | 96f8ba3dd6 | e2ae766c1b |
>> +------------------------------------------------+------------+------------+
>> | boot_successes                                 | 2          | 2          |
>> | boot_failures                                  | 2          | 2          |
>> | BUG:kernel_hang_in_test_stage                  | 2          |            |
>> | WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup      | 0          | 2          |
>> | calltrace:parport_pc_init                      | 0          | 2          |
>> | calltrace:SyS_finit_module                     | 0          | 2          |
>> | WARNING:at_lib/kobject.c:#kobject_add_internal | 0          | 2          |
>> +------------------------------------------------+------------+------------+
>> 
>> 
>> 
>> user  :notice: [  325.592182] vmem_aligned_alloc/TEST1: SETUP (check/pmem/debug)
>> 
>> user  :notice: [  325.603973] vmem_aligned_alloc/TEST1: START: vmem_aligned_alloc
>> kern  :err   : [  325.608906] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:51
>> kern  :err   : [  325.608908] in_atomic(): 1, irqs_disabled(): 0, pid: 24813, name: vmem_aligned_al
>> kern  :warn  : [  325.608914] CPU: 44 PID: 24813 Comm: vmem_aligned_al Tainted: G           O    4.9.0-rc4-00045-ge2ae766 #1
>> kern  :warn  : [  325.608916] Hardware name: Intel Corporation LH Pass/S4600LH...., BIOS SE5C600.86B.99.02.1047.032320122259 03/23/2012
>> kern  :warn  : [  325.608922]  ffffc9002c1f7be0
>> kern  :warn  : [  325.608923]  ffffffff81466af9
>> kern  :warn  : [  325.608924]  ffff880fea2425c0
>
> I think this is actually a bug introduced by Ross' PMD support. Attached
> patch should fix it. Ross, can you check it please?

Hi, Jan

Could you provide a git tree commit for me to test it?  If you want it
to be tested by 0day.

Best Regards,
Huang, Ying

> 								Honza
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c
Date: Tue, 13 Dec 2016 09:27:51 +0800	[thread overview]
Message-ID: <87mvg08voo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20161212163518.GA20728@quack2.suse.cz>

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

Jan Kara <jack@suse.cz> writes:

> On Mon 12-12-16 18:13:21, kernel test robot wrote:
>> FYI, we noticed the following commit:
>> 
>> commit: e2ae766c1b030271b5099b25674e2131d1d1e8c1 ("ext4: convert DAX faults to iomap infrastructure")
>> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
>> 
>> in testcase: nvml
>> with following parameters:
>> 
>> 	group: vmem
>> 	test: pmem
>> 	nr_pmem: 1
>> 	fs: ext4
>> 	mount_option: dax
>> 
>> 
>> 
>> on test machine: 64 threads Intel(R) Xeon(R) CPU E5-4650 0 @ 2.70GHz with 64G memory
>> 
>> caused below changes:
>> 
>> 
>> +------------------------------------------------+------------+------------+
>> |                                                | 96f8ba3dd6 | e2ae766c1b |
>> +------------------------------------------------+------------+------------+
>> | boot_successes                                 | 2          | 2          |
>> | boot_failures                                  | 2          | 2          |
>> | BUG:kernel_hang_in_test_stage                  | 2          |            |
>> | WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup      | 0          | 2          |
>> | calltrace:parport_pc_init                      | 0          | 2          |
>> | calltrace:SyS_finit_module                     | 0          | 2          |
>> | WARNING:at_lib/kobject.c:#kobject_add_internal | 0          | 2          |
>> +------------------------------------------------+------------+------------+
>> 
>> 
>> 
>> user  :notice: [  325.592182] vmem_aligned_alloc/TEST1: SETUP (check/pmem/debug)
>> 
>> user  :notice: [  325.603973] vmem_aligned_alloc/TEST1: START: vmem_aligned_alloc
>> kern  :err   : [  325.608906] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:51
>> kern  :err   : [  325.608908] in_atomic(): 1, irqs_disabled(): 0, pid: 24813, name: vmem_aligned_al
>> kern  :warn  : [  325.608914] CPU: 44 PID: 24813 Comm: vmem_aligned_al Tainted: G           O    4.9.0-rc4-00045-ge2ae766 #1
>> kern  :warn  : [  325.608916] Hardware name: Intel Corporation LH Pass/S4600LH...., BIOS SE5C600.86B.99.02.1047.032320122259 03/23/2012
>> kern  :warn  : [  325.608922]  ffffc9002c1f7be0
>> kern  :warn  : [  325.608923]  ffffffff81466af9
>> kern  :warn  : [  325.608924]  ffff880fea2425c0
>
> I think this is actually a bug introduced by Ross' PMD support. Attached
> patch should fix it. Ross, can you check it please?

Hi, Jan

Could you provide a git tree commit for me to test it?  If you want it
to be tested by 0day.

Best Regards,
Huang, Ying

> 								Honza

WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: kernel test robot <xiaolong.ye@intel.com>,
	"Theodore Ts'o" <tytso@mit.edu>, <linux-nvdimm@ml01.01.org>,
	Dave Chinner <david@fromorbit.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	<linux-ext4@vger.kernel.org>, <lkp@01.org>
Subject: Re: [LKP] [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c
Date: Tue, 13 Dec 2016 09:27:51 +0800	[thread overview]
Message-ID: <87mvg08voo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20161212163518.GA20728@quack2.suse.cz> (Jan Kara's message of "Mon, 12 Dec 2016 17:35:18 +0100")

Jan Kara <jack@suse.cz> writes:

> On Mon 12-12-16 18:13:21, kernel test robot wrote:
>> FYI, we noticed the following commit:
>> 
>> commit: e2ae766c1b030271b5099b25674e2131d1d1e8c1 ("ext4: convert DAX faults to iomap infrastructure")
>> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
>> 
>> in testcase: nvml
>> with following parameters:
>> 
>> 	group: vmem
>> 	test: pmem
>> 	nr_pmem: 1
>> 	fs: ext4
>> 	mount_option: dax
>> 
>> 
>> 
>> on test machine: 64 threads Intel(R) Xeon(R) CPU E5-4650 0 @ 2.70GHz with 64G memory
>> 
>> caused below changes:
>> 
>> 
>> +------------------------------------------------+------------+------------+
>> |                                                | 96f8ba3dd6 | e2ae766c1b |
>> +------------------------------------------------+------------+------------+
>> | boot_successes                                 | 2          | 2          |
>> | boot_failures                                  | 2          | 2          |
>> | BUG:kernel_hang_in_test_stage                  | 2          |            |
>> | WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup      | 0          | 2          |
>> | calltrace:parport_pc_init                      | 0          | 2          |
>> | calltrace:SyS_finit_module                     | 0          | 2          |
>> | WARNING:at_lib/kobject.c:#kobject_add_internal | 0          | 2          |
>> +------------------------------------------------+------------+------------+
>> 
>> 
>> 
>> user  :notice: [  325.592182] vmem_aligned_alloc/TEST1: SETUP (check/pmem/debug)
>> 
>> user  :notice: [  325.603973] vmem_aligned_alloc/TEST1: START: vmem_aligned_alloc
>> kern  :err   : [  325.608906] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:51
>> kern  :err   : [  325.608908] in_atomic(): 1, irqs_disabled(): 0, pid: 24813, name: vmem_aligned_al
>> kern  :warn  : [  325.608914] CPU: 44 PID: 24813 Comm: vmem_aligned_al Tainted: G           O    4.9.0-rc4-00045-ge2ae766 #1
>> kern  :warn  : [  325.608916] Hardware name: Intel Corporation LH Pass/S4600LH...., BIOS SE5C600.86B.99.02.1047.032320122259 03/23/2012
>> kern  :warn  : [  325.608922]  ffffc9002c1f7be0
>> kern  :warn  : [  325.608923]  ffffffff81466af9
>> kern  :warn  : [  325.608924]  ffff880fea2425c0
>
> I think this is actually a bug introduced by Ross' PMD support. Attached
> patch should fix it. Ross, can you check it please?

Hi, Jan

Could you provide a git tree commit for me to test it?  If you want it
to be tested by 0day.

Best Regards,
Huang, Ying

> 								Honza

  parent reply	other threads:[~2016-12-13  1:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 10:13 [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c kernel test robot
     [not found] ` <20161212101321.GA37214-aQzoWfPLU1itqXYlAKuG4QC/G2K4zDHf@public.gmane.org>
2016-12-12 16:35   ` Jan Kara
2016-12-12 16:35     ` Jan Kara
2016-12-12 16:35     ` Jan Kara
2016-12-12 16:35     ` Jan Kara
     [not found]     ` <20161212163518.GA20728-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2016-12-12 22:13       ` Ross Zwisler
2016-12-12 22:13         ` Ross Zwisler
2016-12-12 22:13         ` Ross Zwisler
2016-12-12 22:13         ` Ross Zwisler
     [not found]         ` <20161212221329.GB3622-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-12-12 22:37           ` Theodore Ts'o
2016-12-12 22:37             ` Theodore Ts'o
2016-12-12 22:37             ` Theodore Ts'o
     [not found]             ` <20161212223735.t56oui7vlqhquaks-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2016-12-12 22:48               ` Ross Zwisler
2016-12-12 22:48                 ` Ross Zwisler
2016-12-12 22:48                 ` Ross Zwisler
2016-12-12 22:48                 ` Ross Zwisler
2016-12-12 23:00                 ` Theodore Ts'o
2016-12-12 23:00                   ` Theodore Ts'o
     [not found]                   ` <20161212230020.pbl5wnbqqdgcewlg-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2016-12-12 23:13                     ` Ross Zwisler
2016-12-12 23:13                       ` Ross Zwisler
2016-12-12 23:13                       ` Ross Zwisler
2016-12-12 23:13                       ` Ross Zwisler
2016-12-13  8:47                     ` Jan Kara
2016-12-13  8:47                       ` Jan Kara
2016-12-13  8:47                       ` Jan Kara
2016-12-13  1:27       ` Huang, Ying [this message]
2016-12-13  1:27         ` [LKP] " Huang, Ying
2016-12-13  1:27         ` Huang, Ying
2016-12-13  1:27         ` [LKP] " Huang, Ying
     [not found]         ` <87mvg08voo.fsf-5/hDr2MS57EDqwDYnZuMFFaTQe2KTcn/@public.gmane.org>
2016-12-13 11:42           ` Jan Kara
2016-12-13 11:42             ` Jan Kara
2016-12-13 11:42             ` Jan Kara
2016-12-13 11:42             ` [LKP] " Jan Kara
     [not found]             ` <20161213114208.GF15362-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2016-12-14  3:11               ` Huang, Ying
2016-12-14  3:11                 ` Huang, Ying
2016-12-14  3:11                 ` Huang, Ying
2016-12-14  3:11                 ` [LKP] " Huang, Ying

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=87mvg08voo.fsf@yhuang-dev.intel.com \
    --to=ying.huang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org \
    --cc=jack-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
    --cc=lkp-JC7UmRfGjtg@public.gmane.org \
    --cc=tytso-3s7WtUTddSA@public.gmane.org \
    --cc=xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 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.