From: Frank Kotler <fbkotler@comcast.net>
To: "linux-assembly@vger.kernel.org" <linux-assembly@vger.kernel.org>
Subject: linuxassembly.org - asmutils
Date: Wed, 06 Jul 2005 16:03:35 -0400 [thread overview]
Message-ID: <42CC3917.3020105@comcast.net> (raw)
In-Reply-To: <42CBC727.8060203@linuxassembly.org>
Konstantin Boldyshev wrote:
> Perhaps you've meant linuxassembly.ORG?
What's the story with http://asm.sourceforge.net ? Just a mirror, or is
there some difference?
...
> Still hoping to release new asmutils..
Great! There are a couple bugs in 0.17...
Makefile - insists on buggy 0.98 to build. Deleting the obvious
offending lines fixes it. (we apologize for 0.98.37 - elf output was
badly broken... but 0.98??? Jesus, it won't even assemble its own "test"
directory!)
truss.asm - "pause" is an instruction nowadays. Speak to Intel, not
Nasm's fault. I fixed it by changing to "$pause" (two places, IIRC), but
any change would fix it...
Several of the utilities segfault on 2.6.10+ (this was first brought to
my attention on 2.6.11, but the patch appears to have been applied to
2.6.10 - still there in 2.6.12) This applies to those utilities with the
(only) code section set to "R X", but those with "RWX" still work okay.
I don't know if the proper fix is to make all code sections writeable
(last lines in Brian's "elf.inc") or to make sure every program made
this way has a "UDATASEG"...
Call it a "kernel bug" if you like (I do), but I don't think it's going
to go away.
What are the security implications of making the code section writeable?
Is this a "safe" thing to do?
> And still lacking time for this.. :(
So many bits,so little time... :) Huge thanks to you and others involved
for what you've done. It's a *tremendous* help!
Best,
Frank
next prev parent reply other threads:[~2005-07-06 20:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506292204.j5TM4mLj024638@zeus2.kernel.org>
2005-06-29 23:37 ` TT6: High-quality custom logos and business identities Richard Cooper
2005-06-30 1:13 ` James Colannino
2005-07-01 22:31 ` Steffen Solyga
2005-07-01 22:33 ` Hendrik Visage
2005-07-02 5:28 ` Frank Kotler
2005-07-03 6:15 ` Daniel Bonekeeper
2005-07-08 5:28 ` Richard Cooper
2005-07-04 16:30 ` Does anyone still read this list? Agner Fog
2005-07-03 17:17 ` TT6: High-quality custom logos and business identities jko
2005-06-30 3:09 ` Herbert Poetzl
2005-07-06 11:57 ` Konstantin Boldyshev
2005-07-06 20:03 ` Frank Kotler [this message]
2005-07-07 19:20 ` linuxassembly.org - asmutils Konstantin Boldyshev
2006-02-08 6:26 ` new asmutils are on the way Konstantin Boldyshev
2006-02-08 12:57 ` Frank Kotler
2006-02-08 22:22 ` Konstantin Boldyshev
2006-02-11 0:51 ` Frank Kotler
2006-02-13 16:40 ` Konstantin Boldyshev
2006-02-21 15:41 ` asmutils 0.18 released Konstantin Boldyshev
2006-02-21 16:00 ` Jan Wagemakers
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=42CC3917.3020105@comcast.net \
--to=fbkotler@comcast.net \
--cc=linux-assembly@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).