mailing list of musl libc
 help / color / mirror / code / Atom feed
From: plan9assembler <plan9assembler@gmail.com>
To: musl@lists.openwall.com
Subject: Re: util-linux-2.23 mount segmentation fault error
Date: Sun, 2 Jun 2013 19:55:49 +0900	[thread overview]
Message-ID: <CAGSZau3L2cnbHjOvrvXxsigTWFd5bvWQ_0vBCgaBL7gn3HNSdQ@mail.gmail.com> (raw)
In-Reply-To: <51AAA4DD.8080408@barfooze.de>


[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]

Hi,

i have fixed build error of strace 4.7

vi strace-4.7/defs.h

+ #define sys_getdents64 sys_getdents
+ #define sys_truncate64 sys_truncate
+ #define sys_ftruncate64 sys_ftruncate

and Szabolcs Nagy was right, sscanf malloc patch fixed umount segfault.
but mount/umount timed out operation didn't fixed.

strace -o mount.log mount /dev/sda1 /mnt
strace -o umount.log umount  /mnt

attached strace log archive.
mount.log   :  mount log without patch
umount.log :  umount log without patch

mount_m.log : mount log with patch
umount_m.log : umount log with patch

TIA



On Sun, Jun 2, 2013 at 10:50 AM, John Spencer <maillist-musl@barfooze.de>wrote:

> On 06/02/2013 01:14 AM, plan9assembler wrote:
>
>>
>> i compile strace-4.7 to trace the bug, but get some build error:
>>
>
> use the version and patches from sabotage.
> even if the version used there is one release behind, it works.
>

[-- Attachment #1.2: Type: text/html, Size: 1788 bytes --]

[-- Attachment #2: util-linux_strace_log.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 121178 bytes --]

  reply	other threads:[~2013-06-02 10:55 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
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 [this message]
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=CAGSZau3L2cnbHjOvrvXxsigTWFd5bvWQ_0vBCgaBL7gn3HNSdQ@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).