linux-kernel - Re: Remove easily user-triggerable BUG from generic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120723190422.GA2703@fieldses.org>
Date:	Mon, 23 Jul 2012 15:04:22 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	"J. Bruce Fields" <bfields@...hat.com>
Subject: Re: Remove easily user-triggerable BUG from generic_setlease

On Mon, Jul 23, 2012 at 11:34:56AM -0700, Linus Torvalds wrote:
> On Mon, Jul 23, 2012 at 8:20 AM, J. Bruce Fields <bfields@...ldses.org> wrote:
> >
> > So we need something like the following, backported to 2.6.anything.
> 
> Please add a note about the 3.2+ version of this patch (well, totally
> different patch), and why this particular patch isn't needed there.
> 
> For stable, we should always have a pointer to the patch in mainline,
> and if mainline has a different solution, and note about *why*
> mainline has that different solution.

Right, I wasn't clear: that patch should go to mainline as well.

(Then, do we still want Dave's patch?: in some sense that BUG() was
correct, as the code was obviously intended to catch illegal values
earlier.  And having the BUG() means we found the problem quickly
instead of having to track down memory corruption.  On the other hand,
agreed that BUG()'ing under a spin lock is cruel.  Maybe we should stick
a WARN there if it's not overkill.)

--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/