linux-kernel - Re: [RFC] apparently broken RLIMIT

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: <CAOPLpQfadzGT0OqGmJ7pLf9-b5PQ7ikHVpHMsgs-pJ4DnFCcXA@mail.gmail.com>
Date:	Sun, 6 Oct 2013 17:07:30 -0400
From:	Ulrich Drepper <drepper@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] apparently broken RLIMIT_CORE

On Sun, Oct 6, 2013 at 4:42 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> I doubt it is intentional, but I also cannot really feel that we care
> deeply. Afaik we don't really honor the size limit exactly anyway, ie
> we tend to check only at page boundaries etc. So do we really care?

I could imagine in the case Al brought up (a pipe as core file filter)
we might want to have some assurance the limits are not breached.  If
it doesn't cost that much I'd say implement it precisely.
--
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/