linux-kernel - Re: [PATCH] ipc: Limit sysctl value to IPCMNI

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] [day] [month] [year] [list]

Message-Id: <20180618145114.4a50c378b38b639d7ea8ecdc@linux-foundation.org>
Date:   Mon, 18 Jun 2018 14:51:14 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Waiman Long <longman@...hat.com>
Cc:     Takashi Iwai <tiwai@...e.de>, Davidlohr Bueso <dbueso@...e.de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ipc: Limit sysctl value to IPCMNI

On Mon, 18 Jun 2018 13:27:24 +0800 Waiman Long <longman@...hat.com> wrote:

> >>
> >> Maybe another possible solution would be to add another proc entry to
> >> handle this correctly, and make the old one only for compatibility.
> > Yes, I guess so.  Just leave the old tunable alone.  Possibly we
> > could add a printk_once("please switch to the new interface").
> 
> A problem with that is the fact that those sysctl parameters have been
> there for so long that it may be hard to persuade users to use the new
> sysctl parameters.

That's what a once-off warning could help with.  Tell them they're
using a deprecated interface.  It would take a few years, but when
people see the old interface is scheduled for removal, they'll switch,
over time.