On Wed, Sep 20, 2023 at 1:08 PM Michal Hocko <mhocko@xxxxxxxx> wrote: > [...] > > have a strong opinion against it. Also just to be clear we are not > > talking about full revert of 58056f77502f but just the returning of > > EOPNOTSUPP, right? > > If we allow the limit to be set without returning a failure then we > still have options 2 and 3 on how to deal with that. One of them is to > enforce the limit. > Option 3 is a partial revert of 58056f77502f where we keep the no limit enforcement and remove the EOPNOTSUPP return on write. Let's go with option 3. In addition, let's add pr_warn_once on the read of kmem.limit_in_bytes as well.
