All of lore.kernel.org
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: dmatest: bug out when dma test times out
Date: Thu, 2 Nov 2017 22:03:40 +0530	[thread overview]
Message-ID: <20171102163340.GI3187@localhost> (raw)
In-Reply-To: <36367ec9-61b1-9701-2dec-667b175ed90d@codeaurora.org>

On Thu, Nov 02, 2017 at 07:50:02AM -0500, Timur Tabi wrote:
> On 11/02/2017 07:11 AM, Adam Wallis wrote:
> >>This will essentially kill the system. People have been trying to remove
> >>usage of BUG(), we should not do that. Complaining violently makes sense..
> >>
> >Understood. In my testing, the system is effectively shot if you run the dmatest
> >in a tight enough loop, however, at least using a WARN would alert the user that
> >the kernel might be in an unstable state. I will submit another patch with a
> >WARN, even though, I hope a proper fix can be introduced at some point. I am not
> >familiar enough with this code to propose such a fix at the moment though.
> 
> I think Adam's original patch is correct, because as he said, the code as it
> is today corrupts the kernel.  The BUG() is a stop-cap measure to prevent
> the user from thinking that the kernel is stable when it isn't.

It also helps people to get more information to debug the systems

> So I think that either dmatest gets fixed properly today (which Adam said he
> cannot do), or you should apply his patch until the code can get fixed.

Ofcourse fixing is better.

-- 
~Vinod

      reply	other threads:[~2017-11-02 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 19:49 [PATCH] dmaengine: dmatest: bug out when dma test times out Adam Wallis
2017-11-02  8:17 ` Vinod Koul
2017-11-02 12:11   ` Adam Wallis
2017-11-02 12:50     ` Timur Tabi
2017-11-02 16:33       ` Vinod Koul [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=20171102163340.GI3187@localhost \
    --to=vinod.koul@intel.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.