From: plan9assembler <plan9assembler@gmail.com>
To: musl@lists.openwall.com
Subject: Re: util-linux-2.23 mount segmentation fault error
Date: Tue, 28 May 2013 06:40:14 +0900 [thread overview]
Message-ID: <CAGSZau3xevKg--HSuMn5ymBLy+XEpSKF0k=fqAA2Skd3Pcc4dw@mail.gmail.com> (raw)
In-Reply-To: <20130527142929.GF31915@port70.net>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
Hi, i am sure but it works for me.
actually, it little strange, because,
after modification, first time, it getting segfaults,
later, it works fine.
flags in util-linux-2.23 was created automatically.
musl linux system could be set by this method:
https://github.com/pikhq/bootstrap-linux/issues/8
https://github.com/pikhq/bootstrap-linux/issues/9
http://plan9assembler.wordpress.com/2013/04/26/bootstrap-linux-musl-cross/
gcc-4.8
CC = gcc -std=gnu99
CCDEPMODE = depmode=gcc3
CFLAGS = -g -O2
CPP = gcc -E
TIA
On Mon, May 27, 2013 at 11:29 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> * plan9assembler <plan9assembler@gmail.com> [2013-05-27 23:05:37 +0900]:
> > util-linux-2.23 mount segfault error seems to be solved.
> > no more segfault error, when i test mount binary.
> >
> > i modified follow macros in musl /include/bits/ioctl.h and musl libc
> > reinstalled.
> >
> > - #define _IOR(a,b,c) _IOC(2,(a),(b),sizeof(c))
> > - #define _IOWR(a,b,c) _IOC(3,(a),(b),sizeof(c))
> >
> > + #define _IOR(a,b,c) _IOC(2U,(a),(b),sizeof(c))
> > + #define _IOWR(a,b,c) _IOC(3U,(a),(b),sizeof(c))
> >
>
> hm are you sure this was the change that solved the segfault?
>
> that would be scary since the linux headers have signed
> int left shift overflows in many places
> (and as far as i know users of those headers dont use
> special compilation flags to make signed overflow
> well-defined like gcc -fwrapv)
>
> which compiler did you use and with what flags?
> (this could break a lot of legacy code)
>
[-- Attachment #2: Type: text/html, Size: 2383 bytes --]
next prev parent reply other threads:[~2013-05-27 21:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 15:46 plan9assembler
2013-05-25 16:26 ` Rich Felker
2013-05-25 21:34 ` plan9assembler
2013-05-26 9:14 ` Szabolcs Nagy
2013-05-26 11:22 ` plan9assembler
2013-05-27 14:05 ` plan9assembler
2013-05-27 14:29 ` Szabolcs Nagy
2013-05-27 21:40 ` plan9assembler [this message]
2013-05-29 13:46 ` plan9assembler
2013-05-29 14:11 ` Luca Barbato
2013-05-29 14:32 ` plan9assembler
2013-05-29 14:41 ` plan9assembler
2013-05-29 20:04 ` Szabolcs Nagy
2013-05-29 22:07 ` plan9assembler
2013-05-29 22:17 ` plan9assembler
2013-05-30 6:11 ` plan9assembler
2013-05-30 6:43 ` Szabolcs Nagy
2013-05-30 7:26 ` plan9assembler
2013-05-30 8:37 ` Szabolcs Nagy
2013-06-01 23:14 ` plan9assembler
2013-06-01 23:16 ` plan9assembler
2013-06-02 1:50 ` John Spencer
2013-06-02 10:55 ` plan9assembler
2013-06-02 13:00 ` Szabolcs Nagy
2013-06-02 22:02 ` plan9assembler
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='CAGSZau3xevKg--HSuMn5ymBLy+XEpSKF0k=fqAA2Skd3Pcc4dw@mail.gmail.com' \
--to=plan9assembler@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).