From: Olaf Hering <olh@suse.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: mprotect broken on ppc
Date: Sun, 21 Jan 2001 18:30:31 +0100 [thread overview]
Message-ID: <20010121183031.A25128@suse.de> (raw)
In-Reply-To: <20010120222630.B20689@suse.de>; from olh@suse.de on Sat, Jan 20, 2001 at 10:26:30PM +0100
On Sat, Jan 20, Olaf Hering wrote:
>
> On Sat, Jan 20, Olaf Hering wrote:
>
> >
> > Hi,
> >
> > there seems to be a bug in mprotect which was introduced in
> > test9->test10.
> >
> > The result is an invalid pointer from the getpwuid(3) function, this
> > function is used in rpm to check owner and group permissions.
>
> forgot some facts:
>
> the build host runs always a glibc2.13 system with 2.2 headers. The
> build chroot runs a glibc2.2 system with 2.4.0ac2 headers.
> And it fails when a kernel 2.4.0-test10 or later is running, every other
> kernel works fine.
I put some debug in mm/mprotect.c:
...
asmlinkage long sys_mprotect(unsigned long start, size_t len, unsigned
long prot)
{
unsigned long nstart, end, tmp;
struct vm_area_struct * vma, * next;
int error = -EINVAL;
if (start & ~PAGE_MASK) {
printk("sys_mprotect start \n");
return -EINVAL;
}
...
it fails here.
Jan 21 18:28:06 mandarine kernel: sys_mprotect start
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-21 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 21:19 mprotect broken on ppc Olaf Hering
2001-01-20 21:26 ` Olaf Hering
2001-01-21 17:30 ` Olaf Hering [this message]
2001-01-23 13:03 ` Olaf Hering
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=20010121183031.A25128@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.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.