From: "Robert Merrill" <grievre@gmail.com>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: NFS bug?
Date: Thu, 20 Apr 2006 11:02:03 -0700 [thread overview]
Message-ID: <b3be17f30604201102jff51794r52dd3024d631051e@mail.gmail.com> (raw)
In-Reply-To: <1145555789.8136.13.camel@lade.trondhjem.org>
On 4/20/06, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> Given that you are reporting an error with copy_from_user, then it is
> _definitely_ of interest to figure out what your glibc is telling the
> kernel to copy.
execve("./a.out", ["./a.out", "foo"], [/* 16 vars */]) = 0
uname({sys="Linux", node="soda", ...}) = 0
brk(0) = 0x804a000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
old_mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7f5f000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=20397, ...}) = 0
old_mmap(NULL, 20397, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f5a000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260O\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1270928, ...}) = 0
old_mmap(NULL, 1276892, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e22000
old_mmap(0xb7f50000, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12e000) = 0xb7f50000
old_mmap(0xb7f58000, 7132, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f58000
close(3) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7e21000
mprotect(0xb7f50000, 20480, PROT_READ) = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e218e0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7f5a000, 20397) = 0
open("foo", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0666, st_size=512, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
brk(0) = 0x804a000
brk(0x806f000) = 0x806f000
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 21), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7f5e000
write(1, "0\n", 20
) = 2
getdents64(3, <unfinished ...>
+++ killed by SIGSEGV +++
next prev parent reply other threads:[~2006-04-20 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 16:37 Robert Merrill
2006-04-20 16:41 ` Trond Myklebust
[not found] ` <b3be17f30604200953i652e14a2n908f1a066ffe4e7f@mail.gmail.com>
[not found] ` <1145555789.8136.13.camel@lade.trondhjem.org>
2006-04-20 18:02 ` Robert Merrill [this message]
2006-04-20 18:10 ` Trond Myklebust
2006-04-20 18:14 ` Robert Merrill
2006-04-20 19:20 ` Trond Myklebust
2006-04-20 20:29 ` Robert Merrill
2006-04-21 7:55 ` Andrew Morton
2006-04-21 14:07 ` Trond Myklebust
2006-04-21 16:43 ` Joshua Hudson
2006-04-21 18:31 ` Andrew Morton
2006-04-21 19:34 ` Trond Myklebust
2006-04-23 7:29 ` Robert Merrill
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=b3be17f30604201102jff51794r52dd3024d631051e@mail.gmail.com \
--to=grievre@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®