From: Sharyathi Nagesh <sharyath@in.ibm.com>
To: linux-kernel@vger.kernel.org, Sergey Vlasov <vsu@altlinux.ru>
Cc: Vadim Lobanov <vlobanov@speakeasy.net>,
Zhao Yu Wang <wangzyu@cn.ibm.com>, Pavel Emelianov <xemul@sw.ru>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: Patch to fixe Data Acess error in dup_fd
Date: Thu, 04 Jan 2007 18:40:06 +0530 [thread overview]
Message-ID: <1167916207.3495.19.camel@legolas.in.ibm.com> (raw)
In-Reply-To: <1163768910.12593.19.camel@legolas.in.ibm.com>
Excuse me for the late response
On Fri, 2006-11-17 at 18:38 +0530, Sharyathi Nagesh wrote:
> > I'm guessing that you've already tried this, but it never hurts to be
> > sure: does this machine pass memtest? :)
Machine passes memtest without fail, even after running for many
hours.
Since the problem looked genuine to me and may hit again in future
do let me know how I should improve the patch. Please let us know of the
opinion...
---------------------------------------------------------------------
To restate the problem:
Data access error was observed after testing IO and TCP Stress test for
more than 72 hrs over ppc-64 machine.
[c00000007ce2fa70] c000000000060d28 .dup_fd+0x1d8/0x39c (unreliable)
[c00000007ce2fb30] c000000000060f48 .copy_files+0x5c/0x88
[c00000007ce2fbd0] c000000000061f5c .copy_process+0x574/0x1520
[c00000007ce2fcd0] c000000000062f88 .do_fork+0x80/0x1c4
[c00000007ce2fdc0] c000000000011790 .sys_clone+0x5c/0x74
[c00000007ce2fe30] c000000000008950 .ppc_clone+0x8/0xc
--- Exception: c00 (System Call) at 000000000fee9c60
The location of the problem was
-----------
for (i = open_files; i != 0; i--) {
struct file *f = *old_fds++;
if (f) {
get_file(f); <== Get file does increment of f_count of
struct file
} else {
-----------
in kernel/fork.c.Accessing f_count gives Data access error as 'struct file' pointer f is
pointing to invalid location
Regards
Sharyathi Nagesh
prev parent reply other threads:[~2007-01-04 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 9:32 Sharyathi Nagesh
2006-11-14 15:16 ` Sergey Vlasov
2006-11-14 18:49 ` Vadim Lobanov
2006-11-14 20:42 ` Sergey Vlasov
2006-11-14 21:35 ` Vadim Lobanov
2006-11-15 7:38 ` Sharyathi Nagesh
2006-11-15 8:15 ` Vadim Lobanov
2006-11-15 9:03 ` Sharyathi Nagesh
2006-11-17 13:08 ` Sharyathi Nagesh
2006-11-17 19:26 ` Vadim Lobanov
2007-01-04 13:10 ` Sharyathi Nagesh [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=1167916207.3495.19.camel@legolas.in.ibm.com \
--to=sharyath@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vlobanov@speakeasy.net \
--cc=vsu@altlinux.ru \
--cc=wangzyu@cn.ibm.com \
--cc=xemul@sw.ru \
/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®