public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dylan Taft <soundmanok@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc2-mm1
Date: Wed, 18 Oct 2006 22:44:34 +0000 (UTC)	[thread overview]
Message-ID: <loom.20061019T004316-648@post.gmane.org> (raw)
In-Reply-To: 4534E773.9060600@shadowen.org

Andy Whitcroft <apw <at> shadowen.org> writes:

> 
> Seeing this on a couple of x86_64's so far, probabally widespread:
> 
> BUG: warning at fs/inode.c:1389/i_size_write()
> 
> elm3b6:
> 
> Call Trace:
>  [<ffffffff8028207d>] i_size_write+0x51/0x73
>  [<ffffffff8028ddfb>] generic_commit_write+0x35/0x49
>  [<ffffffff802e78d1>] ext2_commit_chunk+0x32/0x6d
>  [<ffffffff802e86a0>] ext2_make_empty+0x160/0x179
>  [<ffffffff802eb734>] ext2_mkdir+0xb5/0x121
>  [<ffffffff80278926>] vfs_mkdir+0x6a/0xaa
>  [<ffffffff80278a12>] sys_mkdirat+0xac/0xfd
>  [<ffffffff80272607>] vfs_stat+0x14/0x16
>  [<ffffffff8021b703>] sys32_stat64+0x1a/0x34
>  [<ffffffff80278a76>] sys_mkdir+0x13/0x15
>  [<ffffffff8021b212>] ia32_sysret+0x0/0xa
> 
> This first one does not look so unreasonable, the inode is new and has
> not yet been instantiated?  But I'm no fs locking expert ...
> 
> BUG: warning at fs/inode.c:1389/i_size_write()
> 
> bl6-13:
> 
> Call Trace:
>  [<ffffffff80298a44>] i_size_write+0x45/0x57
>  [<ffffffff802a116b>] simple_commit_write+0x3b/0x47
>  [<ffffffff8028d96b>] __page_symlink+0xb5/0x150
>  [<ffffffff8030b742>] ramfs_symlink+0x4d/0xb7
>  [<ffffffff8028e547>] vfs_symlink+0xd4/0x144
>  [<ffffffff80290d4e>] sys_symlinkat+0x86/0xd2
>  [<ffffffff808e3c33>] do_header+0x70/0x1d2
>  [<ffffffff808e2bd5>] do_symlink+0x4b/0x7b
>  [<ffffffff808e2a55>] write_buffer+0x1d/0x2b
>  [<ffffffff808e2acf>] flush_window+0x6c/0xca
>  [<ffffffff808e3097>] inflate_codes+0x38f/0x3ec
>  [<ffffffff808e428a>] inflate_dynamic+0x4f5/0x541
>  [<ffffffff808e479a>] unpack_to_rootfs+0x4c4/0x923
>  [<ffffffff808e4c83>] populate_rootfs+0x8a/0xde
>  [<ffffffff8020715a>] init+0x114/0x346
>  [<ffffffff8020a925>] child_rip+0xa/0x15
>  [<ffffffff803e0d6e>] acpi_ds_init_one_object+0x0/0x82
>  [<ffffffff803e0d6e>] acpi_ds_init_one_object+0x0/0x82
>  [<ffffffff80207046>] init+0x0/0x346
>  [<ffffffff8020a91b>] child_rip+0x0/0x15
> 
> -apw
> 



I get this too, running an intel core duo on an asus p5b, but everything is 
running 32bit compiled programs., same kernel as well.

BUG: warning at fs/inode.c:1389/i_size_write()
 [<c017d450>] i_size_write+0x70/0x80
 [<c01ab051>] ext3_journalled_commit_write+0xf1/0x120
 [<c01aab80>] commit_write_fn+0x0/0x70
 [<c01aaf60>] ext3_journalled_commit_write+0x0/0x120
 [<c0171b50>] __page_symlink+0x90/0x170
 [<c01aed00>] ext3_symlink+0x80/0x1c0
 [<c012d298>] __capable+0x8/0x20
 [<c01aec80>] ext3_symlink+0x0/0x1c0
 [<c01726a0>] vfs_symlink+0x80/0xa0
 [<c01747e2>] sys_symlinkat+0xb2/0xe0
 [<c011cd2c>] do_page_fault+0x32c/0x630
 [<c0174830>] sys_symlink+0x20/0x30
 [<c0103252>] sysenter_past_esp+0x5f/0x85
 =======================






  parent reply	other threads:[~2006-10-18 22:50 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17  6:06 2.6.19-rc2-mm1 Andrew Morton
     [not found] ` <a44ae5cd0610170003r77595cc0p8ed66badde952859@mail.gmail.com>
2006-10-17  7:36   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17  8:41 ` 2.6.19-rc2-mm1 Brice Goglin
2006-10-17 12:54   ` [PATCH] backlight users need to select BACKLIGHT_CLASS_DEVICE Andy Whitcroft
2006-10-17 13:17 ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-17 14:23 ` 2.6.19-rc2-mm1 Andy Whitcroft
2006-10-17 16:07   ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:22   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:44   ` Dylan Taft [this message]
2006-10-17 15:45 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:29   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-20 13:40     ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-17 19:37 ` 2.6.19-rc2-mm1 Jeremy Fitzhardinge
2006-10-17 20:22   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 10:05     ` 2.6.19-rc2-mm1 Michael Ellerman
2006-10-18 19:05       ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17 19:53 ` [2.6.19-rc2-mm1] error: too few arguments to function ‘crypto_alloc_hash’ Andrew James Wade
2006-10-17 21:19   ` Edward Shishkin
2006-10-18 16:53     ` Andrew James Wade
2006-10-18 15:33 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 15:48   ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:15     ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:26       ` 2.6.19-rc2-mm1 Chris Mason
2006-10-18 17:32       ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:41         ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:56           ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:58         ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:14           ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 18:22             ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:31             ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 23:59               ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 22:44           ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 23:01             ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 23:25               ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19  0:07                 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19  0:21                   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 15:28                     ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19 12:32                 ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-19 16:18                   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:57                     ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-18 18:27 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 19:18   ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 19:33     ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 19:42       ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 20:20         ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 20:26         ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 22:23           ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:05             ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-19 18:10               ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-20  7:37                 ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-18 20:22       ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 18:42 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 21:44   ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:29     ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:41       ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:46         ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:57           ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:04             ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:12               ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 14:45 ` 2.6.19-rc2-mm1 // errors in verify_redzone_free() Mariusz Kozlowski
2006-10-19 17:03   ` Andrew Morton
2006-10-19 17:17     ` Jean Tourrilhes
2006-10-19 17:25       ` Andrew Morton
2006-10-19 17:47         ` Jean Tourrilhes
2006-10-19 18:31           ` Mariusz Kozlowski
2006-10-19 18:33             ` Jean Tourrilhes
2006-10-19 17:33       ` Mariusz Kozlowski

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=loom.20061019T004316-648@post.gmane.org \
    --to=soundmanok@yahoo.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