cinap_lenrek ac88ce4f7f make bind(2) error handling consistent ... The mount() and bind() syscalls return -1 on error, and the mountid sequence number on success. The manpage states that the mountid sequence number is a positive integer, but the kernels implementation currently uses a unsigned 32-bit integer and does not guarantee that the mountid will not become negative. Most code just cares about the error, so test for the -1 error value only.		2020-05-02 17:32:01 +02:00
..
9660
prep	disk/edisk: allow printing and readonly inspection of hybrid MBR/GPT disks (thanks aiju)	2017-12-05 23:44:43 +01:00
sacfs	make bind(2) error handling consistent	2020-05-02 17:32:01 +02:00
smart
vblade
cryptsetup.c	fix bugs and cleanup cryptsetup code	2016-10-24 20:56:11 +02:00
exsort.c
format.c	disk/format: implement long name support	2019-08-19 01:09:24 +02:00
mbr.c
mkext.c
mkfile	fix bugs and cleanup cryptsetup code	2016-10-24 20:56:11 +02:00
mkfs.c	disk/mkfs: remove unused cputype variable (thanks kvik)	2018-11-12 16:54:59 +01:00
partfs.c
rd9660.c