All of lore.kernel.org
 help / color / mirror / Atom feed
From: avienamo@nvidia.com (Aapo Vienamo)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] arm: kgdb: patch_text() in kgdb_arch_set_breakpoint() may sleep
Date: Wed, 5 Aug 2015 18:50:31 +0300	[thread overview]
Message-ID: <55C230C7.2000909@nvidia.com> (raw)

Hi,

The breakpoint setting code in arch/arm/kernel/kgdb.c calls
patch_text(), which ends up trying to sleep while in interrupt context.
The bug was introduced by commit: 23a4e40 arm: kgdb: Handle read-only
text / modules. The resulting behavior is "BUG: scheduling while
atomic..." when setting a breakpoint in kgdb. This was tested on an
Nvidia Jetson TK1 board with 4.2.0-rc5-next-20150805 kernel.

Regards,
Aapo Vienamo

WARNING: multiple messages have this Message-ID (diff)
From: Aapo Vienamo <avienamo@nvidia.com>
To: <dianders@chromium.org>, <keescook@chromium.org>, <nico@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [BUG] arm: kgdb: patch_text() in kgdb_arch_set_breakpoint() may sleep
Date: Wed, 5 Aug 2015 18:50:31 +0300	[thread overview]
Message-ID: <55C230C7.2000909@nvidia.com> (raw)

Hi,

The breakpoint setting code in arch/arm/kernel/kgdb.c calls
patch_text(), which ends up trying to sleep while in interrupt context.
The bug was introduced by commit: 23a4e40 arm: kgdb: Handle read-only
text / modules. The resulting behavior is "BUG: scheduling while
atomic..." when setting a breakpoint in kgdb. This was tested on an
Nvidia Jetson TK1 board with 4.2.0-rc5-next-20150805 kernel.

Regards,
Aapo Vienamo

             reply	other threads:[~2015-08-05 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 15:50 Aapo Vienamo [this message]
2015-08-05 15:50 ` [BUG] arm: kgdb: patch_text() in kgdb_arch_set_breakpoint() may sleep Aapo Vienamo
2015-08-24  2:45 ` Doug Anderson
2015-08-24  2:45   ` Doug Anderson
2015-08-24 17:46   ` Kees Cook
2015-08-24 17:46     ` Kees Cook
2015-08-24 23:56     ` Doug Anderson
2015-08-24 23:56       ` Doug Anderson
2015-08-25  5:20       ` Kees Cook
2015-08-25  5:20         ` Kees Cook
2015-08-25 22:06       ` Doug Anderson
2015-08-25 22:06         ` Doug Anderson

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=55C230C7.2000909@nvidia.com \
    --to=avienamo@nvidia.com \
    --cc=linux-arm-kernel@lists.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 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.