From: David Woodhouse <dwmw2@infradead.org>
To: Jamie Clark <jclark@metaparadigm.com>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23aa1 ext3 oops
Date: Thu, 18 Dec 2003 06:25:09 +0000 [thread overview]
Message-ID: <1071728709.5316.2.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <3FE14706.3070003@metaparadigm.com>
On Thu, 2003-12-18 at 14:19 +0800, Jamie Clark wrote:
> The first oops ocurred after 4 or 5 days. My second run crashed in the
> first night, this time in filemap.c: precheck_file_write().
> This oops seemed to be at or near the first dereference of inode, before
> the f_flags test.
>
> /* FIXME: this is for backwards compatibility with 2.4 */
> if (!S_ISBLK(inode->i_mode) && (file->f_flags & O_APPEND))
> *ppos = pos = inode->i_size;
Odd. And what's 'inode' then? What compiler are you using?
> Is CONFIG_DEBUG_SLAB all that I need?
Yes, I believe so.
--
dwmw2
next prev parent reply other threads:[~2003-12-18 6:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 2:49 2.4.23pre6aa3 scsi oops Jamie Clark
2003-11-04 10:28 ` Andrea Arcangeli
2003-11-04 11:52 ` Jamie Clark
2003-11-04 12:48 ` Andrea Arcangeli
2003-11-27 3:21 ` 2.4.23pre6aa3 - possible ext3 deadlock Jamie Clark
2003-11-27 12:56 ` Jan Kara
2003-12-06 1:05 ` 2.4.23pre6aa3 scsi oops Andrea Arcangeli
2003-12-06 1:39 ` Jamie Clark
2003-12-11 2:33 ` 2.4.23aa1 ext3 oops Jamie Clark
2003-12-16 15:15 ` Marcelo Tosatti
2003-12-16 15:55 ` Jamie Clark
2003-12-17 11:42 ` David Woodhouse
2003-12-18 6:19 ` Jamie Clark
2003-12-18 6:25 ` David Woodhouse [this message]
2003-12-18 7:33 ` Jamie Clark
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=1071728709.5316.2.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=andrea@suse.de \
--cc=jclark@metaparadigm.com \
--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;
as well as URLs for NNTP newsgroup(s).