mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chase Douglas <chase.douglas@canonical.com>
To: linux-kernel@vger.kernel.org, kernel-team <kernel-team@lists.ubuntu.com>
Subject: Using tracing_off() in __schedule_bug()
Date: Fri, 12 Mar 2010 10:32:04 -0500	[thread overview]
Message-ID: <40ec3ea41003120732w5f44a2ebq728047e742f32bba@mail.gmail.com> (raw)

We're considering using tracing_off() in __schedule_bug() in the
Ubuntu kernel to help us solve "scheduling while atomic" bugs without
needing to compile and install a special kernel to do so. Using the
tracing_off() call enables us to generate smaller function traces when
debugging, and find the bug easier since it should be at the end of
any traces. The patch we are thinking of using can be found at [1].
You can find an overview of how bugs are solved using this approach
there as well.

Are there any thoughts as to the appropriateness of this patch in
Ubuntu kernels? My guess is that this isn't done in the upstream
vanilla kernels because it would be annoying to have a stock kernel
littered with tracing_off() calls if you hit one when you weren't
meaning to. However, we're interested in hearing if there's some
negative consequence we haven't thought of.

Thanks,
Chase Douglas

[1] http://lkml.org/lkml/2009/4/10/310

             reply	other threads:[~2010-03-12 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 15:32 Chase Douglas [this message]
2010-03-12 23:34 ` Steven Rostedt
2010-03-13  2:12   ` Chase Douglas
2010-03-13  2:30     ` Steven Rostedt
2010-03-13  2:50       ` Chase Douglas
2010-03-13  3:09         ` Steven Rostedt
2010-03-13  3:15           ` Chase Douglas

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=40ec3ea41003120732w5f44a2ebq728047e742f32bba@mail.gmail.com \
    --to=chase.douglas@canonical.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®