linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] proc: test /proc/self/syscall
Date: Fri, 18 May 2018 14:22:37 +0530	[thread overview]
Message-ID: <CA+G9fYv3rqfZBMK=Sbr1b3QxkW51917wU1esGuXtPN-irNq01w@mail.gmail.com> (raw)
In-Reply-To: <20180514200335.GA2050@avx2>

On 15 May 2018 at 01:33, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Tue, May 15, 2018 at 12:34:18AM +0530, Naresh Kamboju wrote:
>> Hi Alexey,
>>
>> On 27 February 2018 at 02:51, Alexey Dobriyan <adobriyan@gmail.com> wrote:
>> > Read from /proc/self/syscall should yield read system call and correct
>> > args in the output as current is reading /proc/self/syscall.
>>
>> Is this test expected to work on arm32 bit architecture ?
>> I have tested on arm32 devices and it returns 1 and reported as FAIL.
>>
>> Strace output:
>> <snip>
>> munmap(0xb6f4a000, 13514)               = 0
>> open("/proc/self/syscall", O_RDONLY)    = 3
>> read(3, "3 0x3 0xbeacfbe0 0x40 0x3 0xbeac"..., 64) = 64
>
> Yes! Obviously, it was tested on x86_64 only.
>
> arch/arm/tools/syscall.tbl shows read is #3
> and pointer looks 32-bit, so what's wrong?

Please ignore the strace output because test return 0 for strace process.

Here is the modified test case with more prints, which shows test case failed
due to third condition is true.
strncmp() return 3.
Is strncmp() implementation different on 32 and 64 bit architecture in glibc ?

Test case and output:
https://pastebin.com/grL2TUzs

- Naresh

      reply	other threads:[~2018-05-18  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 21:21 [PATCH 2/2] proc: test /proc/self/syscall Alexey Dobriyan
2018-05-14 19:04 ` Naresh Kamboju
2018-05-14 20:03   ` Alexey Dobriyan
2018-05-18  8:52     ` Naresh Kamboju [this message]

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='CA+G9fYv3rqfZBMK=Sbr1b3QxkW51917wU1esGuXtPN-irNq01w@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@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).