mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE
@ 2012-04-08 23:19 Larry Finger
  2012-04-09  1:46 ` Devin Heitmueller
  0 siblings, 1 reply; 3+ messages in thread
From: Larry Finger @ 2012-04-08 23:19 UTC (permalink / raw)
  To: Mauro Carvalho Chehab
  Cc: Larry Finger, Hans Verkuil, linux-media, linux-kernel, jrh

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.

Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
---
 drivers/media/video/au0828/au0828-video.c |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/media/video/au0828/au0828-video.c b/drivers/media/video/au0828/au0828-video.c
index 0b3e481..5c53e38 100644
--- a/drivers/media/video/au0828/au0828-video.c
+++ b/drivers/media/video/au0828/au0828-video.c
@@ -891,8 +891,13 @@ static int res_locked(struct au0828_dev *dev, unsigned int bit)
 static void res_free(struct au0828_fh *fh, unsigned int bits)
 {
 	struct au0828_dev    *dev = fh->dev;
+	unsigned int bits2 = fh->resources & bits;
 
-	BUG_ON((fh->resources & bits) != bits);
+	if (bits2 != bits) {
+		WARN_ONCE(true, "au0828: Trying to free resource 0x%x"
+			  " without reserving it\n", bits);
+		return;
+	}
 
 	mutex_lock(&dev->lock);
 	fh->resources  &= ~bits;
-- 
1.7.10


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE
  2012-04-08 23:19 [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE Larry Finger
@ 2012-04-09  1:46 ` Devin Heitmueller
  2012-04-09  2:16   ` Larry Finger
  0 siblings, 1 reply; 3+ messages in thread
From: Devin Heitmueller @ 2012-04-09  1:46 UTC (permalink / raw)
  To: Larry Finger
  Cc: Mauro Carvalho Chehab, Hans Verkuil, linux-media, linux-kernel, jrh

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.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE
  2012-04-09  1:46 ` Devin Heitmueller
@ 2012-04-09  2:16   ` Larry Finger
  0 siblings, 0 replies; 3+ messages in thread
From: Larry Finger @ 2012-04-09  2:16 UTC (permalink / raw)
  To: Devin Heitmueller
  Cc: Mauro Carvalho Chehab, Hans Verkuil, linux-media, linux-kernel, jrh

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-04-09  2:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-08 23:19 [PATCH] media: au0828: Convert BUG_ON to WARN_ONCE Larry Finger
2012-04-09  1:46 ` Devin Heitmueller
2012-04-09  2:16   ` Larry Finger

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