From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] madvise07.c:72: FAIL: Did not receive SIGBUS
Date: Mon, 13 Feb 2017 10:08:37 +0100 [thread overview]
Message-ID: <20170213090837.GA16973@rei.lan> (raw)
In-Reply-To: <CAEemH2ddpwBet_2crzv+sOJ9P84fscFH1re4SCo1dD_PKGgsgA@mail.gmail.com>
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
next prev parent reply other threads:[~2017-02-13 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 2:53 [LTP] madvise07.c:72: FAIL: Did not receive SIGBUS Li Wang
2017-02-13 9:08 ` Cyril Hrubis [this message]
2017-02-13 12:43 ` Richard Palethorpe
2017-02-14 14:06 ` Jan Stancek
2017-02-14 15:18 ` Richard Palethorpe
2017-02-14 15:25 ` Jan Stancek
2017-02-15 9:38 ` Li Wang
2017-02-15 9:45 ` Li Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170213090837.GA16973@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.