From: Hajime Tazaki<thehajime@gmail.com>
To: johannes@sipsolutions.net
Cc: rrs@debian.org, anton.ivanov@kot-begemot.co.uk,
chris.obbard@collabora.com, linux-um@lists.infradead.org,
983379@bugs.debian.org
Subject: Re: linux uml segfault
Date: Sat, 06 Mar 2021 07:25:43 +0900 [thread overview]
Message-ID: <m2tupp44rc.wl-thehajime@gmail.com> (raw)
In-Reply-To: <5fee882c709f6c9d061b58a0e7b3110b3afbb96e.camel@sipsolutions.net>
might be late, but I'll give it a try with your dlopen reproducer.
-- Hajime
On Sat, 06 Mar 2021 05:22:19 +0900,
Johannes Berg wrote:
>
> On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:
> >
> > objcopy (from binutils) can localize symbols (i.e., objcopy -L
> > sem_init $orig_file $new_file).
>
> This doesn't seem to be sufficient.
>
> > It also does renaming symbols. But
> > not sure this is the ideal solution.
>
> Even that doesn't seem to actually work/help? I still get libcom_err
> trying to call UML's sem_init, even after doing
> objcopy --redefine-sym sem_init=uml_sem_init
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-03-05 22:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 8:06 linux uml segfault Ritesh Raj Sarraf
2021-02-23 10:50 ` Anton Ivanov
2021-02-23 12:12 ` Christopher Obbard
2021-02-23 12:24 ` Anton Ivanov
2021-02-23 17:19 ` Anton Ivanov
2021-02-23 17:26 ` Ritesh Raj Sarraf
2021-02-23 18:02 ` Anton Ivanov
2021-02-24 11:44 ` Anton Ivanov
2021-03-02 9:09 ` Ritesh Raj Sarraf
2021-03-02 11:34 ` Anton Ivanov
2021-03-02 14:23 ` Ritesh Raj Sarraf
2021-03-02 17:05 ` Anton Ivanov
2021-03-02 17:27 ` Ritesh Raj Sarraf
2021-03-03 9:30 ` Anton Ivanov
2021-03-03 10:45 ` Bug#983379: " Ritesh Raj Sarraf
2021-03-03 10:53 ` Anton Ivanov
2021-03-03 22:40 ` Johannes Berg
2021-03-04 5:38 ` Hajime Tazaki
2021-03-04 7:45 ` Anton Ivanov
2021-03-04 7:47 ` Johannes Berg
2021-03-04 8:05 ` Benjamin Berg
2021-03-04 18:41 ` Anton Ivanov
2021-03-05 9:59 ` Anton Ivanov
2021-03-05 10:07 ` Johannes Berg
2021-03-05 17:39 ` Anton Ivanov
2021-03-05 18:32 ` Johannes Berg
2021-03-05 19:03 ` Anton Ivanov
2021-03-05 20:06 ` Johannes Berg
2021-03-05 20:07 ` Johannes Berg
2021-03-05 20:22 ` Johannes Berg
2021-03-05 22:25 ` Hajime Tazaki [this message]
2021-03-07 12:22 ` Hajime Tazaki
2021-03-07 12:56 ` Johannes Berg
2021-03-04 7:28 ` Anton Ivanov
2021-03-04 7:43 ` Johannes Berg
2021-03-05 19:54 ` Johannes Berg
2021-03-05 20:43 ` [PATCH] um: mark all kernel symbols as local Johannes Berg
2021-03-05 20:54 ` Anton Ivanov
2021-03-06 10:51 ` Ritesh Raj Sarraf
2021-03-08 10:29 ` Bug#983379: " Ritesh Raj Sarraf
2021-03-08 10:33 ` Johannes Berg
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=m2tupp44rc.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=983379@bugs.debian.org \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=chris.obbard@collabora.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=rrs@debian.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