linux-kernel - Re: [Patch 2/8] ipc/mqueue: switch back to using non-max values on create

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20120417160055.f8e35101.akpm@linux-foundation.org>
Date:	Tue, 17 Apr 2012 16:00:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	KOSAKI Motohiro <kosaki.motohiro@...il.com>
Cc:	Doug Ledford <dledford@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [Patch 2/8] ipc/mqueue: switch back to using non-max values on
 create

On Tue, 17 Apr 2012 18:32:25 -0400
KOSAKI Motohiro <kosaki.motohiro@...il.com> wrote:

> > Here the "future patch" is "mqueue: separate mqueue default value from
> > maximum value v2" in this series, yes?
> >
> > So people who have applications which are broken by this patch will
> > need to manually set /proc/sys/fs/mqueue/msg_default and/or
> > /proc/sys/fs/mqueue/msgsize_default to get those apps working again?
> >
> 
> Yes, it works.
> 

OK, I updated the changelog for this patch to reflect that.

I worry a bit that some people who we don't know about will hit this
problem and will have to spend a lot of time working out why it broke. 
Is there some way in which we can make it easier for them?  A little
printk_once() in a suitable place?


--
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/