From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sanity.bbclass: Reading /proc/sys/vm/mmap_min_addr is not permitted with 2.6.33+ on host
Date: Sun, 3 Jan 2010 08:00:30 +0100 [thread overview]
Message-ID: <20100103070030.GA3202@jama> (raw)
In-Reply-To: <1262455806.2553.90.camel@lenovo.internal.reciva.com>
On Sat, Jan 02, 2010 at 06:10:05PM +0000, Phil Blundell wrote:
> On Sat, 2010-01-02 at 18:10 +0100, Martin Jansa wrote:
> > * With 2.6.33-rc2-00252-ge9e5521 on my host I noticed that
> > "cat /proc/sys/vm/mmap_min_addr" returns now
> > "cat: /proc/sys/vm/mmap_min_addr: Operation not permitted"
> > Its probably becuse of
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e1a6ef2dea88101b056b6d9984f3325c5efced3
> > But I'm not sure if checking CAP_SYS_RAWIO even for reading this value
> > is intentional or just bug which should be fixed in kernel.
> >
> > * This patch prints notice about need to check that value yourself (as
> > root) instead of failing with "ERROR: IO Error: [Errno 1] Operation
> > not permitted"
> >
> > * Its not optimal, because this notice is shown every time you run
> > bitbake (even after checking/setting 0 to mmap_min_addr if you have
> > kernel not allowing to read it
> >
>
> That does sound fairly unsatisfactory. Printing a diagnostic on every
> build, with no way for the user to suppress it, surely can't be the way
> of the future.
Yes, agreed. I consider this only as temporary solution, because
without this change I cannot use bitbake at all and of course I can
remove that message if this behavior stay the same in 2.6.33 release or
someone check qemu mmap failure.
That's why I didn't push it and just sent it here as heads up for
builders with 2.6.33-rc* to save tham few mins checking what happen to
bitbake.
> If you can't tell whether mmap_min_addr is set correctly or not then it
> would probably be better to not show the diagnostic at all. Perhaps you
> could investigate patching qemu to print a more meaningful message if it
> actually encounters a mmap() failure of this kind.
Cheers,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
prev parent reply other threads:[~2010-01-03 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 17:10 [PATCH] sanity.bbclass: Reading /proc/sys/vm/mmap_min_addr is not permitted with 2.6.33+ on host Martin Jansa
2010-01-02 18:10 ` Phil Blundell
2010-01-03 0:53 ` Denys Dmytriyenko
2010-01-15 17:14 ` Marcin Juszkiewicz
2010-01-15 18:56 ` [PATCH] sanity.bbclass: Reading?/proc/sys/vm/mmap_min_addr " Denys Dmytriyenko
2010-01-15 19:00 ` Marcin Juszkiewicz
2010-01-03 7:00 ` Martin Jansa [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=20100103070030.GA3202@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 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.