linux-kernel - About getrandom(2) contract

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

Message-ID: <CALN7hCKMP7xr4KmnP=hzC8rsBNk5vgmvybTy+ViUw9=2A5_NBg@mail.gmail.com>
Date:   Wed, 18 Sep 2019 12:08:02 +0300
From:   Elichai Turkel <elichai.turkel@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: About getrandom(2) contract

Hi,

Unlike other syscalls(like `read(2)`) `getrandom(2)`'s contract
doesn't define what happens if you pass `buflen=0`, does the pointer
still has to be valid? (what does valid even mean?) are there any side
effects?
i.e. is `getrandom(0x01, 0, 0)` undefined behavior?.

Thanks,
Elichai.
-- 
PGP: 5607C93B5F86650C