From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Carl-Daniel Hailfinger" <c-d.hailfinger.devel.2006@gmx.net>
Cc: "Eric Sesterhenn" <snakebyte@gmx.de>,
linux-ntfs-dev@lists.sourceforge.net,
"Anton Altaparmakov" <aia21@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image
Date: Mon, 7 Jul 2008 15:33:42 +0200 [thread overview]
Message-ID: <19f34abd0807070633y337486cek34f8fea6bbbf37f1@mail.gmail.com> (raw)
In-Reply-To: <48721996.8050708@gmx.net>
On Mon, Jul 7, 2008 at 3:26 PM, Carl-Daniel Hailfinger
<c-d.hailfinger.devel.2006@gmx.net> wrote:
>> which is...
>>
>> vi->i_mtime = ntfs2utc(si->last_data_change_time);
>>
>> which is probably what is causing the NULL pointer dereference.
>>
>
> The problem of this theory is that there is no NULL pointer dereference,
> unless you meant "invalid memory access".
Oops, yeah. I skipped a line, but page fault nonetheless ;-)
The rest of the theory should still hold. The pointer being
dereferenced is held in %eax, which is c6798550. This fits with the
reported address:
[ 76.583958] BUG: unable to handle kernel paging request at c6798558
...
[ 76.584019] EAX: c6798550 EBX: 00000000 ECX: c678b000 EDX: c678b038
Thanks for the correction.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-07 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 17:21 Eric Sesterhenn
2008-07-07 8:07 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2008-07-07 12:24 ` Eric Sesterhenn
2008-07-07 13:03 ` Vegard Nossum
2008-07-07 13:26 ` Carl-Daniel Hailfinger
2008-07-07 13:33 ` Vegard Nossum [this message]
2008-07-07 13:21 ` Carl-Daniel Hailfinger
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=19f34abd0807070633y337486cek34f8fea6bbbf37f1@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=aia21@cam.ac.uk \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=snakebyte@gmx.de \
/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
Powered by JetHome