[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171019.115756.1156159427863267036.davem@davemloft.net>
Date: Thu, 19 Oct 2017 11:57:56 +0100 (WEST)
From: David Miller <davem@...emloft.net>
To: ard.biesheuvel@...aro.org
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in
dql_complete()
From: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Date: Wed, 18 Oct 2017 16:45:15 +0100
> Even though calling dql_completed() with a count that exceeds the
> queued count is a serious error, it still does not justify bringing
> down the entire kernel with a BUG_ON(). So relax it to a WARN_ON()
> instead.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>
This is bogus.
Unless you are going to do all of the work necessary to fix
the out-of-bounds condition here, you cannot safely continue
into the rest of this function.
Things are going to explode in many places if you don't, at
a minimum, fix the 'count' value to be in range.
But like others I don't like this, the driver needs to be fixed
urgently if this condition triggers.
Sorry I'm not applying this.
Powered by blists - more mailing lists