From: malware@t-online.de (Michael Mueller)
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in __mark_inode_dirty (2.4.2-pre3)
Date: Sun, 11 Mar 2001 22:39:24 +0100 [thread overview]
Message-ID: <200103112139.WAA08138@fire.malware.de> (raw)
In-Reply-To: <200103111232.NAA02902@fire.malware.de>
Hi,
i wrote:
> EIP: 0010:[__mark_inode_dirty+92/112]
> EFLAGS: 00010202
> eax: 00000000 ebx: cc85b240 ecx: cc85b428 edx: cc85b248
> esi: c15dc200 edi: 00000001 ebp: c361dfa4 esp: c361df24
^^^^^^^^
This is a bit-flipper. There is a valid super-block entry at c14dc200.
Michael
prev parent reply other threads:[~2001-03-11 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-11 12:32 Oops in __mark_inode_dirty (2.4.2-pre3) Michael Mueller
2001-03-11 21:39 ` Michael Mueller [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=200103112139.WAA08138@fire.malware.de \
--to=malware@t-online.de \
--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