From: Stephen Boyd <sboyd@codeaurora.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, tglx@linutronix.de,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: + debugobjects-fix-selftest-for-static-warnings.patch added to -mm tree
Date: Sat, 14 Jan 2012 18:46:26 -0800 [thread overview]
Message-ID: <4F123E02.2070401@codeaurora.org> (raw)
In-Reply-To: <20111215213549.09360200057@hpza10.eem.corp.google.com>
On 12/15/11 13:35, akpm@linux-foundation.org wrote:
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>
> ------------------------------------------------------
> From: Stephen Boyd <sboyd@codeaurora.org>
> Subject: debugobjects: Fix selftest for static warnings
>
> debugobjects is now printing a warning when a fixup for a NOTAVAILABLE
> object is run. This causes the selftest to fail like:
>
> [ 0.000000] ODEBUG: selftest warnings failed 4 != 5
>
> We could just increase the number of warnings that the selftest is
> expecting to see because that is actually what has changed. But, it turns
> out that fixup_activate() was written with inverted logic and thus a fixup
> for a static object returned 1 indicating the object had been fixed, and 0
> otherwise. Fix the logic to be correct and update the counts to reflect
> that nothing needed fixing for a static object.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> Reported-By: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
Can this be picked up or merged into 3.3-rc1? Linus' tree has a broken
selftest without this change.
> lib/debugobjects.c | 14 +++-----------
> 1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff -puN lib/debugobjects.c~debugobjects-fix-selftest-for-static-warnings lib/debugobjects.c
> --- a/lib/debugobjects.c~debugobjects-fix-selftest-for-static-warnings
> +++ a/lib/debugobjects.c
> @@ -818,17 +818,9 @@ static int __init fixup_activate(void *a
> if (obj->static_init == 1) {
> debug_object_init(obj, &descr_type_test);
> debug_object_activate(obj, &descr_type_test);
> - /*
> - * Real code should return 0 here ! This is
> - * not a fixup of some bad behaviour. We
> - * merily call the debug_init function to keep
> - * track of the object.
> - */
> - return 1;
> - } else {
> - /* Real code needs to emit a warning here */
> + return 0;
> }
> - return 0;
> + return 1;
>
> case ODEBUG_STATE_ACTIVE:
> debug_object_deactivate(obj, &descr_type_test);
> @@ -967,7 +959,7 @@ static void __init debug_objects_selftes
>
> obj.static_init = 1;
> debug_object_activate(&obj, &descr_type_test);
> - if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, warnings))
> + if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings))
> goto out;
> debug_object_init(&obj, &descr_type_test);
> if (check_results(&obj, ODEBUG_STATE_INIT, ++fixups, ++warnings))
> _
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2012-01-15 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 21:35 + debugobjects-fix-selftest-for-static-warnings.patch added to -mm tree akpm
2012-01-15 2:46 ` Stephen Boyd [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=4F123E02.2070401@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.