linux-kernel - msgmnb limits?

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

Date:	Tue, 16 Feb 2010 11:59:06 +0100
From:	Troels Arvin <troels.arvin@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: msgmnb limits?

Hello,

On a server with lots of RAM (192GB), I ran into an application (DB2) 
which applies the following sysctl changes when it's started, if the 
values haven't already been set to - at least - the stated values:

  - kernel.msgmax = 65535
  - kernel.msgmnb = 65536

However, that doesn't work: Certain operations (LOAD and 
backups/restores) will fail with the following messages, unless 
kernel.msgmnb is increased:

DIA8557C No message was sent using the message queue.
CALLED  : OS, -, msgsnd                           OSERR: EAGAIN (11)
DATA #1 : system V message queue identifier., PD_TYPE_SYSV_QUEUE_ID

I tried setting kernel.msgmnb to 524288, and then things work. This 
value was chosen out of the blue, and I'd like to make a more informed 
choice:

  - Is there a limit to the size of msgmnb?
  - Can I expect the system to start thrashing if msgmnb is
    increased beyond a certain value?
  - Is my understanding correkt: msgmnb should always be at least
    as large as msgmax?

Thanks in advance.

-- 
Regards,
Troels Arvin
--
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/