Re: [PATCH v8 0/5] ipc: IPCMNI limit check for *mni & increase that limit

From: Andrew Morton
Date: Thu Sep 06 2018 - 18:24:55 EST


On Fri, 17 Aug 2018 09:50:08 -0700 Davidlohr Bueso <dave@xxxxxxxxxxxx> wrote:

> >Enforcing the range limit check may cause some existing applications to break
> >if they unwittingly set a value higher than 32k. To allow system administrators
> >to work around this issue, a new ipcmni_compat sysctl parameter can now be set
> >to restore the old behavior. This compatibility mode can only be set if the
> >ipcmni_extend boot parameter is not specified. Patch 5 implements this new
> >sysctl parameter.
> >
> >Waiman Long (5):
> > ipc: IPCMNI limit check for msgmni and shmmni
> > ipc: IPCMNI limit check for semmni
>
> I've reviewed the first two which look good and are actual immediate fixes
> to the bogus user input. I haven't gotten around yet the rest of the patches
> but are at least a bit more controversial than the first two. As such, could
> patch 1 and 2 be picked up once the merge window closes, for v4.20? Although
> -stable might want in, this situation is quite historic, so it's not that
> urgent.

Thanks. Could we please have a refresh and resend? Hopefully Luis
will have time for another pass.