From: Will Deacon <will.deacon@arm.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: Commit breaks strace: ARM: entry: allow ARM-private syscalls to be restarted
Date: Wed, 18 Sep 2013 10:17:49 +0100 [thread overview]
Message-ID: <20130918091748.GA1783@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20130917215749.GA11109@obsidianresearch.com>
On Tue, Sep 17, 2013 at 10:57:49PM +0100, Jason Gunthorpe wrote:
> Hi Will,
Hi Jason,
> I was just testing v3.12-rc1 (on kirkwood) and noticed that strace is
> not working:
Thanks for the report!
> $ strace /bin/ls
> mmap2(0xb6f79000, 9552, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6f79000
> close(3) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6fad000
> set_tls(0xb6fad4c0, 0xb6fadb98, 0xb6fb1050, 0xb6fad4c0, 0xb6fb1050) = -1 ENOSYS (Function not implemented)
> writev(2, [{"cannot set up thread-local stora"..., 36}, {"unknown error", 13}, {"\n", 1}], 3cannot set up thread-local storage: unknown error
> ) = 50
> exit_group(127) = ?
> +++ exited with 127 +++
>
> I determined that reverting your commit below makes strace work again.
> I've tested 3.10.12 and it is OK.
Hmm, so if you don't run with strace, does `/bin/ls' work as expected? From
the trace above, it seems that set_tls is failing rather than anything in
strace (unless of course, the trace is just plain wrong).
> This happens with the latest git head for strace, as well as the 4.7
> release.
>
> Hopefully you can cook up a fix :)
I'll take a look today, thanks.
Will
next prev parent reply other threads:[~2013-09-18 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 21:57 Commit breaks strace: ARM: entry: allow ARM-private syscalls to be restarted Jason Gunthorpe
2013-09-18 9:17 ` Will Deacon [this message]
2013-09-18 9:50 ` Will Deacon
2013-10-04 17:24 ` Arokux X
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=20130918091748.GA1783@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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