From: Mike Hearn <mh@codeweavers.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binfmt_elf.c allow .bss with no access (p---)
Date: Fri, 12 Mar 2004 16:42:11 +0000 [thread overview]
Message-ID: <pan.2004.03.12.16.42.11.387702@codeweavers.com> (raw)
In-Reply-To: 4050BBA1.2080804@BitWagon.com
On Thu, 11 Mar 2004 11:18:57 -0800, John Reiser wrote:
> Yes, because the patch considers each PT_LOAD with p_filesz < p_memsz
> to have a "local" .bss. This is more general than plain 2.6.3 which
> creates only one "global" BSS after accumulating information from all
> of the PT_LOAD.
Fantastic. I'm afraid I'm unfamiliar with the kernel development process,
how do I track the patch to find out when it's checked in and which
releases it's available in (we'd really like 2.4 as well, though it may be
too late to make it worthwhile for now....)
thanks -mike
next prev parent reply other threads:[~2004-03-12 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 17:38 Potential bug in fs/binfmt_elf.c? Mike Hearn
2004-03-05 18:28 ` John Reiser
2004-03-06 18:46 ` Ulrich Drepper
2004-03-06 21:10 ` Mike Hearn
2004-03-07 6:11 ` Ulrich Drepper
2004-03-07 9:58 ` Mike Hearn
2004-03-07 10:46 ` Ulrich Drepper
2004-03-07 11:53 ` Mike Hearn
2004-03-07 21:32 ` Ulrich Drepper
2004-03-07 23:55 ` Eric W. Biederman
2004-03-08 5:57 ` John Reiser
2004-03-08 8:06 ` Jakub Jelinek
2004-03-11 6:17 ` [PATCH] binfmt_elf.c allow .bss with no access (p---) John Reiser
2004-03-11 14:23 ` Mike Hearn
2004-03-11 19:18 ` John Reiser
2004-03-12 16:42 ` Mike Hearn [this message]
[not found] ` <20040412185317.79ac7d7d.akpm@osdl.org>
2004-04-13 17:33 ` John Reiser
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=pan.2004.03.12.16.42.11.387702@codeweavers.com \
--to=mh@codeweavers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@theoretic.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