From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Palethorpe Date: Fri, 02 Aug 2019 15:57:45 +0200 Subject: [LTP] [RFC PATCH 1/9] lib: Add support for guarded buffers In-Reply-To: <1879623564.3992300.1564655982672.JavaMail.zimbra@redhat.com> References: <20190801092616.30553-1-chrubis@suse.cz> <20190801092616.30553-2-chrubis@suse.cz> <1879623564.3992300.1564655982672.JavaMail.zimbra@redhat.com> Message-ID: <87a7crd606.fsf@rpws.prws.suse.cz> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Hello, Jan Stancek writes: > ----- Original Message ----- >> This commit adds a support for guarder buffers. Guarded buffer is a >> buffer allocated so that there is PROT_NONE page immediatelly after the >> end of the buffer i.e. any access after the buffer generates >> SEGFAULT/EFAULT etc. >> >> The library is hooked into the tst_test structure so that all you need >> is to fill up an NULL terminated array of buffer pointers and sizes to >> get the respective buffers allocated. The library supports allocating >> memory in test runtime as well as well as allocating more complex >> buffers, which currently are iovec vectors. > > Runtime alloc in loop could be an issue, do we need also runtime free? I think tst_alloc needs a bit more documentation at the least. If we have runtime free then we need to figure out which map the address belongs to or what its offset is (if any). -- Thank you, Richard.