From: Randy Dunlap <rdunlap@infradead.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: fix map_files test on F29
Date: Sun, 14 Apr 2019 09:06:45 -0700 [thread overview]
Message-ID: <8f4ea187-67cc-fa5f-ea6d-5070e18b503c@infradead.org> (raw)
In-Reply-To: <20190414155848.GA23418@avx2>
On 4/14/19 8:58 AM, Alexey Dobriyan wrote:
> On Sun, Apr 14, 2019 at 08:24:53AM -0700, Randy Dunlap wrote:
>> On 4/14/19 5:36 AM, Alexey Dobriyan wrote:
>>> F29 bans mapping first 64KB even for root making test fail.
>>
>> so there is an F29-only patch that prevents that?
>> something that is not in mainline?
>
> Ehh, no. F29 ships stable kernels actually.
>
> Test assumes mmap(0, MAP_FIXED) succeeds as root. F29 uses SELinux
> to ban that.
>
Thanks for the clarification.
--
~Randy
prev parent reply other threads:[~2019-04-14 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 12:36 [PATCH] proc: fix map_files test on F29 Alexey Dobriyan
2019-04-14 15:24 ` Randy Dunlap
2019-04-14 15:58 ` Alexey Dobriyan
2019-04-14 16:06 ` Randy Dunlap [this message]
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=8f4ea187-67cc-fa5f-ea6d-5070e18b503c@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).