mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, 322309-submitter@bugs.debian.org,
	329468@bugs.debian.org, 329468-submitter@bugs.debian.org,
	debian-devel@bugs.debian.org, linux-kernel@vger.kernel.org,
	332903-submitter@bugs.debian.org
Subject: Re: Bug#322309: Debian woody dpkg no longer works with recent	linux kernel.
Date: Mon, 10 Oct 2005 10:07:35 +0900	[thread overview]
Message-ID: <87y852rxgo.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <1128897196.19000.3.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

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.

Thanks, I didn't notice it was since 2.6.12. woody dpkg
was long broken. I've only seen more recent reports about this.

To fix this problem, will require update to 
dpkg in woody; which might not be feasible.
We could drop support of woody chroots in etch.
It might be possible to add a workaround hack 
in [c]debootstrap to trap mmap; or fill 
status/available files before invoking dpkg.


I'm not quite sure why sarge manages to bootstrap despite 
having a dpkg version (1.10.28) that shouldn't work.


regards,
	junichi

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-10  1:07 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 [this message]
2005-10-11 14:24   ` Junichi Uekawa
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=87y852rxgo.dancerj%dancer@netfort.gr.jp \
    --to=dancer@netfort.gr.jp \
    --cc=322309-submitter@bugs.debian.org \
    --cc=322309@bugs.debian.org \
    --cc=329468-submitter@bugs.debian.org \
    --cc=329468@bugs.debian.org \
    --cc=332903-submitter@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