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
| ||
|
Date: Sun, 1 Apr 2007 11:03:15 -0700 From: "Ken Chen" <kenchen@...gle.com> To: "devzero@....de" <devzero@....de> Cc: linux-kernel@...r.kernel.org, jdike@...toit.com Subject: Re: [patch] remove artificial software max_loop limit On 4/1/07, devzero@....de <devzero@....de> wrote: > not sure if this is a real issue and if it`s UML or loop related - > but how is low-memory situations being handled when > creating loop devices ? kernel returns -ENOMEM as an error code if there are no memory left to initialize loop device. > should losetup or dmesg tell "out of memory" if there is not > enough memory left ? It should, as kernel does pass that info back to app. Does losetup check return value of open() syscall? - 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/
Powered by blists - more mailing lists