From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Scott James Remnant <scott@netsplit.com>
Cc: Junichi Uekawa <dancer@netfort.gr.jp>,
322309@bugs.debian.org, 329468@bugs.debian.org,
debian-devel@bugs.debian.org, linux-kernel@vger.kernel.org,
332903@bugs.debian.org
Subject: Re: Bug#322309: Debian woody dpkg no longer works with recent linux kernel.
Date: Tue, 11 Oct 2005 23:24:30 +0900 [thread overview]
Message-ID: <87achg9lnl.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <1128897196.19000.3.camel@localhost.localdomain>
Hi,
> > dpkg in Debian woody (3.0) is broken by recent linux kernels;
> > due to the following command changing behavior (mmap of
> > zero-byte length):
> >
> > addr=mmap(NULL, 0, PROT_READ, MAP_SHARED, fd, 0);
> >
> > These bugs are caused by mmap changing behavior;
> > it used to return NULL when given a length of 0.
> > However, it now returns -1, and gives back an errno=EINVAL.
> >
> Indeed. This was the sole change in the 1.13.8 release.
1.13.8 is more recent than sarge; and I'm not quite sure
why sarge successfully installs, and woody fails.
I'm seeing several potential solutions.
0.
Backport dpkg change to woody and update woody
(maybe impossible due to Debian oldstable
update infrastructure)
1.
Modify [c]debootstrap to dump dummy data in
/var/lib/dpkg/{status,available}
2.
write a kernel patch to return 0 when mmap is
called with length=0
3.
Create a LD_PRELOAD or ptrace hack to return
0 when mmap is called with length=0
regards,
junichi
next prev parent reply other threads:[~2005-10-11 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 15:16 Junichi Uekawa
2005-10-09 22:33 ` Bug#322309: " Scott James Remnant
2005-10-10 1:07 ` Junichi Uekawa
2005-10-11 14:24 ` Junichi Uekawa [this message]
2005-10-11 15:15 ` Junichi Uekawa
2005-10-11 15:19 ` Jon Masters
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=87achg9lnl.dancerj%dancer@netfort.gr.jp \
--to=dancer@netfort.gr.jp \
--cc=322309@bugs.debian.org \
--cc=329468@bugs.debian.org \
--cc=332903@bugs.debian.org \
--cc=debian-devel@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@netsplit.com \
/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
Powered by JetHome