[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <725dd537afca44489dad48e8ef20e894@AcuMS.aculab.com>
Date: Tue, 13 Oct 2020 15:22:50 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Giuseppe Scrivano' <gscrivan@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"christian.brauner@...ntu.com" <christian.brauner@...ntu.com>,
"containers@...ts.linux-foundation.org"
<containers@...ts.linux-foundation.org>
Subject: RE: [PATCH 2/2] selftests: add tests for CLOSE_RANGE_CLOEXEC
> Subject: [PATCH 2/2] selftests: add tests for CLOSE_RANGE_CLOEXEC
You really ought to check that it skips closed files.
For instance using dup2() to move some open files to 'big numbers'.
Although you know how it works, a 'black box' test would also
reduce RLIMIT_NOFILES below one of the open files and check
files above the RLIMIT_NOFILES value are affected.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists