From: Larry Finger <Larry.Finger@lwfinger.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
jrh <jharbestonus@gmail.com>
Subject: Re: [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE
Date: Sun, 08 Apr 2012 21:16:46 -0500 [thread overview]
Message-ID: <4F82468E.5000308@lwfinger.net> (raw)
In-Reply-To: <CAGoCfixO1mUO0VGBL9GzOmaWpQ6rVos095reFfUWnVwCj0CyYg@mail.gmail.com>
On 04/08/2012 08:46 PM, Devin Heitmueller wrote:
> On Sun, Apr 8, 2012 at 7:19 PM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
>> In the mail thread at http://www.mythtv.org/pipermail/mythtv-users/2012-April/331164.html,
>> a kernel crash is triggered when trying to run mythtv with a HVR950Q tuner.
>> The crash condition is due to res_free() being called to free something that
>> has is not reserved. The actual reason for this mismatch of reserve/free is
>> not known; however, using a BUG_ON rather than a WARN_ON seems unfortunate.
>
> This patch should be nack'd. The real reason should be identified,
> and a patch should be submitted for that (and from what I gather, it
> seems like it is easily reproduced by the submitter). Just add a few
> "dump_stack()" calls in the res_get() and res_free() calls to identify
> the failing call path.
I agree that we need to find the real cause; however, I am not the one with the
problem, and I do not have the hardware. In addition, I am not sure how much
additional debug information the person will be able to provide. He has not
built Linux kernels since 1.2. If he can get a kernel built, then we will try to
find the real cause.
In any case, why the reluctance to get rid of the BUG_ON? Is this condition so
severe that the kernel needs to be stopped immediately?
Larry
prev parent reply other threads:[~2012-04-09 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 23:19 Larry Finger
2012-04-09 1:46 ` Devin Heitmueller
2012-04-09 2:16 ` Larry Finger [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=4F82468E.5000308@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dheitmueller@kernellabs.com \
--cc=hans.verkuil@cisco.com \
--cc=jharbestonus@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
Powered by JetHome