From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyril Hrubis Date: Mon, 13 Feb 2017 10:08:37 +0100 Subject: [LTP] madvise07.c:72: FAIL: Did not receive SIGBUS In-Reply-To: References: Message-ID: <20170213090837.GA16973@rei.lan> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Hi! > I'm trying to run ltp on upstream kernel-4.10.0-rc7, and found that > madvise07 always failing with no SIGBUS received when mmap the PRIVATE > memory. I hope to know if there're some relevant stuff about this > issue. > Any discussion or document for that? Looks like a plain old kernel bug to me. > # uname -r > 4.10.0-rc7 > > # ./madvise07 > tst_test.c:794: INFO: Timeout per run is 0h 05m 00s > madvise07.c:57: INFO: madvise(0x7f25bdd7e000, 4096, MADV_HWPOISON) > madvise07.c:72: FAIL: Did not receive SIGBUS after accessing > MAP_PRIVATE memory marked with MADV_HWPOISON If you reach this TFAIL the child wasn't killed with a signal after it accessed memory marked with MADV_HWPOISON. What hardware is this? > madvise07.c:57: INFO: madvise(0x7f25bdd7e000, 4096, MADV_HWPOISON) > madvise07.c:90: PASS: madvise(..., MADV_HWPOISON) on MAP_SHARED memory -- Cyril Hrubis chrubis@suse.cz