From: Johannes Berg <johannes@sipsolutions.net>
To: linux-um@lists.infradead.org,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: j@w1.fi
Subject: TRACE_IRQFLAGS_SUPPORT seems incomplete
Date: Tue, 28 May 2019 23:00:21 +0200 [thread overview]
Message-ID: <a5611c91d4883c7ef91dc14a72946e18bf5809b6.camel@sipsolutions.net> (raw)
Hi,
Now I've tried for a while ... but can't figure it out.
It looks like TRACE_IRQFLAGS_SUPPORT is incomplete, we're getting lots
of warnings like
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:4220 check_flags+0xa4/0x255
[ 0.000000] DEBUG_LOCKS_WARN_ON(current->hardirqs_enabled)
[ 0.000000] Call Trace:
[ 0.000000] [<60047243>] show_stack+0x13b/0x155
[ 0.000000] [<60521206>] dump_stack+0x2a/0x2c
[ 0.000000] [<600652af>] __warn+0x10c/0x151
[ 0.000000] [<6006538b>] warn_slowpath_fmt+0x97/0x99
[ 0.000000] [<600a3355>] check_flags+0xa4/0x255
[ 0.000000] [<600a554e>] lock_acquire+0x6c/0x1a0
[ 0.000000] [<60539298>] _raw_spin_lock+0x30/0x83
[ 0.000000] [<600b6d41>] handle_edge_irq+0x23/0x13d
[ 0.000000] [<600b2b17>] generic_handle_irq+0x23/0x27
[ 0.000000] [<600454ab>] do_IRQ+0x39/0x54
[ 0.000000] [<6004556d>] sigio_handler+0xa7/0x111
[ 0.000000] [<6005badf>] sig_handler_common+0xa9/0xbf
[...]
[ 0.000000] possible reason: unannotated irqs-off.
I've tried to put the right trace_irqflags_{on,off} calls in places like
sig_handler_common(), but I can only seem to shift the warning around.
Has anyone looked at this? You need to enable CONFIG_PROVE_LOCKING,
CONFIG_DEBUG_LOCKDEP and CONFIG_TRACE_IRQFLAGS for this to show up, but
I think Jouni had some others that might be related, without having
enabled CONFIG_DEBUG_LOCKDEP.
Thanks,
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
reply other threads:[~2019-05-28 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a5611c91d4883c7ef91dc14a72946e18bf5809b6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-um@lists.infradead.org \
--cc=richard.weinberger@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).