linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: sedat.dilek@gmail.com
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, sfr@canb.auug.org.au,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [next-20101038] Call trace in ext4
Date: Thu, 28 Oct 2010 14:55:31 -0400	[thread overview]
Message-ID: <20101028185531.GE6814@thunk.org> (raw)
In-Reply-To: <AANLkTi=O1a3ZWg500OgPPLDxQeoEUsRdqGwzcgNmc8RD@mail.gmail.com>

On Thu, Oct 28, 2010 at 08:34:19PM +0200, Sedat Dilek wrote:
> 
> One minute after I sent the mail, I ran into the error.
> Now, I could start my IRC-client for a while... till crash.

Yeah, the patchesin ext4/next are just things to fix compiling without
CONFIG_BLOCK or CONFIG_EXT4_FS_XATTR.  It doesn't make any code
changes at all.

					- Ted

      reply	other threads:[~2010-10-28 18:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 10:05 [next-20101038] Call trace in ext4 Sedat Dilek
2010-10-28 10:34 ` [next-20101028] " Sedat Dilek
2010-10-28 15:08   ` Sedat Dilek
2010-10-28 15:27     ` Ted Ts'o
2010-10-28 17:52 ` [next-20101038] " Markus Trippelsdorf
2010-10-28 18:01   ` Ted Ts'o
2010-10-28 18:16     ` Eric Sandeen
2010-10-28 19:32     ` Ted Ts'o
2010-10-28 19:36       ` Eric Sandeen
2010-10-28 19:54         ` Ted Ts'o
2010-10-28 19:54       ` Sedat Dilek
2010-10-28 20:05         ` Ted Ts'o
2010-10-28 20:15           ` Sedat Dilek
2010-10-28 20:37             ` Ted Ts'o
2010-10-28 21:02               ` Sedat Dilek
2010-10-28 21:06                 ` Ted Ts'o
2010-10-28 21:17                   ` Sedat Dilek
2010-10-28 18:20   ` Sedat Dilek
2010-10-28 18:34     ` Sedat Dilek
2010-10-28 18:55       ` Ted Ts'o [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=20101028185531.GE6814@thunk.org \
    --to=tytso@mit.edu \
    --cc=arnd@arndb.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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).