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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 7 Jun 2017 18:26:01 +0000
From:   "Hefty, Sean" <sean.hefty@...el.com>
To:     Leon Romanovsky <leon@...nel.org>,
        Jason Gunthorpe <jgunthorpe@...idianresearch.com>
CC:     "Wan, Kaike" <kaike.wan@...el.com>,
        "Fleck, John" <john.fleck@...el.com>,
        "Weiny, Ira" <ira.weiny@...el.com>, Thomas Graf <tgraf@...g.ch>,
        Doug Ledford <dledford@...hat.com>,
        Jiri Pirko <jiri@...lanox.com>,
        RDMA mailing list <linux-rdma@...r.kernel.org>,
        linux-netdev <netdev@...r.kernel.org>
Subject: RE: Netlink messages without NLM_F_REQUEST flag

> It is acking that message from user was received by kernel and now
> processing. The message from kernel to user are anyway unreliable [1],
> so I don't understand on which handshake you are talking.
> 
> [1] "reliable transmissions from kernel to user are impossible in any
> case"
> https://linux.die.net/man/7/netlink

The SA messages are kernel initiated messages that target a user space daemon (e.g. ibacm) for cached PR data.  If that fails because the daemon isn't running or the message is lost, the normal retry mechanism in the kernel should kick in and try sending the SA message to the remote (i.e. real) SA.

- Sean

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ