public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vadim Lobanov <vlobanov@speakeasy.net>
To: sharyath@in.ibm.com
Cc: Sergey Vlasov <vsu@altlinux.ru>, Pavel Emelianov <xemul@sw.ru>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Patch to fixe Data Acess error in dup_fd
Date: Wed, 15 Nov 2006 00:15:40 -0800	[thread overview]
Message-ID: <1163578540.4987.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1163576300.8208.14.camel@legolas.in.ibm.com>

On Wed, 2006-11-15 at 13:08 +0530, Sharyathi Nagesh wrote:
>    This is very interesting: after reading through I am feeling there is high chance this 
> could as well be a memory corruption issue. But if the issue is memory getting corrupted 
> what could be the possible reasons.
>    I had observed random slab corruption issues in the machine, could
> that may have resulted in corruption, we may be opening up larger issues
> here about which I am not much aware of, 

I'm guessing that you've already tried this, but it never hurts to be
sure: does this machine pass memtest? :)

>    The kernel version on which it is tested is: 2.6.18-1 (Distro   
>    variant)

Unless someone recognizes special magic values from the register dumps
to point at any particular part of the kernel, the corruption could be
coming from almost anywhere. If noone has any better guesses, then
narrowing down the problem might be worthwhile: grab a vanilla
non-distro 2.6.18-1 kernel (from kernel.org) and see if you can
reproduce the problem with that, and then try to find the previous
release where the problem disappears. Or use git instead, which folks
say can do this bisection process rather well. :)

Thanks,
-- Vadim Lobanov


  reply	other threads:[~2006-11-15  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  9:32 Patch to fixe Data Acess error in dup_fd 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 [this message]
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

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=1163578540.4987.7.camel@localhost.localdomain \
    --to=vlobanov@speakeasy.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sharyath@in.ibm.com \
    --cc=torvalds@osdl.org \
    --cc=vsu@altlinux.ru \
    --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