From: Rong Chen <rong.a.chen@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [LKP] 0a3856392c [ 10.513760] INFO: trying to register non-static key.
Date: Wed, 12 Sep 2018 13:04:12 +0800 [thread overview]
Message-ID: <283720fb-e9ec-2f2b-660a-ef97d233914f@intel.com> (raw)
In-Reply-To: <20180907021937.GA7440@bombadil.infradead.org>
On 09/07/2018 10:19 AM, Matthew Wilcox wrote:
> On Fri, Sep 07, 2018 at 09:05:39AM +0800, kernel test robot wrote:
>> Greetings,
>>
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>
>> commit 0a3856392cff1542170b5bc37211c9a21fd0c3f6
>> Author: Matthew Wilcox <willy@infradead.org>
>> AuthorDate: Mon Jun 18 17:23:37 2018 -0400
>> Commit: Matthew Wilcox <willy@infradead.org>
>> CommitDate: Tue Aug 21 23:54:20 2018 -0400
>>
>> test_ida: Move ida_check_leaf
>>
>> Convert to new API and move to kernel space. Take the opportunity to
>> test the situation a little more thoroughly (ie at different offsets).
>>
>> Signed-off-by: Matthew Wilcox <willy@infradead.org>
> Thank you test-bot. Can you check if this patch fixes the problem?
Thanks, It works.
Best Regards,
Rong Chen
>
> diff --git a/lib/test_ida.c b/lib/test_ida.c
> index 2d1637d8136b..b06880625961 100644
> --- a/lib/test_ida.c
> +++ b/lib/test_ida.c
> @@ -150,10 +150,10 @@ static void ida_check_conv(struct ida *ida)
> IDA_BUG_ON(ida, !ida_is_empty(ida));
> }
>
> +static DEFINE_IDA(ida);
> +
> static int ida_checks(void)
> {
> - DEFINE_IDA(ida);
> -
> IDA_BUG_ON(&ida, !ida_is_empty(&ida));
> ida_check_alloc(&ida);
> ida_check_destroy(&ida);
>
prev parent reply other threads:[~2018-09-12 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 1:05 [LKP] 0a3856392c [ 10.513760] INFO: trying to register non-static key kernel test robot
2018-09-07 2:19 ` Matthew Wilcox
2018-09-12 5:04 ` Rong Chen [this message]
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=283720fb-e9ec-2f2b-660a-ef97d233914f@intel.com \
--to=rong.a.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=willy@infradead.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