Date: Thu, 26 May 2016 06:38:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-standards@FreeBSD.org Subject: [Bug 209729] Defining RLIM_SAVED_MAX and RLIM_SAVED_CUR in sys/sys/resource.h according to POSIX. Message-ID: <bug-209729-15-bDCHVgD49K@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209729-15@https.bugs.freebsd.org/bugzilla/> References: <bug-209729-15@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209729 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-standards@FreeBSD.o | |rg CC| |kib@FreeBSD.org Component|kern |standards --- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> --- Is there a consensus that the patch is the right thing to do ? POSIX specifies that RLIM_SAVED_MAX and RLIM_SAVED_CUR can be same as RLIM_INFINITY, if all limit values are represented as rlim_t. Our rlim_t is 64-bit signed (which is already non-conforming), and e.g. RLIMIT_FSIZE file sizes larger than (1ULL<<63) cannot be represented by our rlim_t without so= me strength of interpretation. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209729-15-bDCHVgD49K>