[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#481478: marked as done ([linux-image-2.6.25-2-686] invalid opcode)

Your message dated Fri, 2 Jan 2009 20:49:19 +0100
with message-id <20090102194919.GA11371@galadriel.inutil.org>
and subject line Re: [linux-image-2.6.25-2-686] invalid opcode
has caused the Debian Bug report #481478,
regarding [linux-image-2.6.25-2-686] invalid opcode
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
481478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481478
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.25-2-686
Version: 2.6.25-3
Severity: normal

--- Please enter the report below this line. ---
Hi, got this with the current kernel from sid:

 burek kernel: [ 3175.481342] ------------[ cut here ]------------                                burek
 burek kernel: [ 3175.481342] invalid opcode: 0000 [#1] SMP 
 burek kernel: [ 3175.481342] Process zsh (pid: 6877, ti=f31f8000 task=f30bd350 task.ti=f31f8000)
 burek kernel: [ 3175.481342] Stack: f0c319d8 c017ab6c 00000000 00000000 c030d757 bfbc0b74 00000000 00000000 
 burek kernel: [ 3175.481342]        c017b34f f31f9fa4 00000000 bfbc0b74 00000000 00000000 f31f8000 c010aa8d 
 burek kernel: [ 3175.481342]        00010000 00000000 bfbc0b74 00000000 c01077e4 bfbc0b74 00000000 bfbb7a10 
 burek kernel: [ 3175.481342] Call Trace:
 burek kernel: [ 3175.481342]  [<c017ab6c>] create_write_pipe+0x140/0x14b
 burek kernel: [ 3175.481342]  [<c017b34f>] do_pipe+0xf/0xd4
 burek kernel: [ 3175.481342]  [<c010aa8d>] sys_pipe+0xc/0x33
 burek kernel: [ 3175.481342]  [<c01077e4>] sysenter_past_esp+0x6d/0xa5
 burek kernel: [ 3175.481342]  =======================
 burek kernel: [ 3175.481342] Code: 3c 01 00 00 77 ff ff ff eb e0 e8 5c eb 12 00 31 c0 c3 85 c0 53 89 c3 74 59 8b 80 a0 00 00 00 83 bb 3c 01 00 00 40 8b 40 20 75 04 <0f> 0b eb fe 85 c0 74 0b 8b 50 10 85 d2 74 04 89 d8 ff d2 8d 43 
 burek kernel: [ 3175.481342] EIP: [<c018506b>] iput+0x19/0x62 SS:ESP 0068:f31f9f64

... and the shell died.  It also happened with 2.6.25-3~snapshot.11346 from
deb http://kernel-archive.buildserver.net/debian-kernel sid main a few times.
I'd used linux-image-2.6.24-1-686=2.6.24-5 before that, and had seen no
similar issues.

Regards,
Zoran
--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.25-2-686

Debian Release: lenny/sid
  990 testing         security.debian.org 
  990 testing         debian.iskon.hr 
  990 testing         buildd.emdebian.org 
  500 ubuntu-doko     people.ubuntu.com 
  500 kernel-dists-sid kernel-archive.buildserver.net 
  500 feisty          wine.budgetdedicated.com 
   50 unstable        debian.iskon.hr 
   50 unstable        debian-multimedia.org 
   50 unstable        buildd.emdebian.org 
   40 experimental    debian.iskon.hr 

--- Package information. ---
Depends                        (Version) | Installed
========================================-+-================
module-init-tools                        | 3.4-1
initramfs-tools               (>= 0.55)  | 0.92
 OR yaird                (>= 0.0.12-25)  | 
 OR linux-initramfs-tool                 |

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-1

On Sat, Nov 08, 2008 at 02:09:16AM +0000, Ben Hutchings wrote:
> The oops points to the following assertion in iput:
> 
> BUG_ON(inode->i_state == I_CLEAR);
> 
> which indicates a double-free.  That was probably introduced by:
> 
> commit 430e285e0817e3e18aadd814bc078d50d8af0cbf
> Author: Dave Hansen <haveblue@us.ibm.com>
> Date:   Fri Feb 15 14:37:26 2008 -0800
> 
>     [PATCH] fix up new filp allocators
>     
>     Some new uses of get_empty_filp() have crept in; switched
>     to alloc_file() to make sure that pieces of initialization
>     won't be missing.
>     
>     We really need to kill get_empty_filp().
>     
>     [AV] fixed dentry leak on failure exit in anon_inode_getfd()
> 
> and fixed by:
> 
> commit ed1524371716466e9c762808b02601d0d0276a92
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date:   Tue Apr 22 19:51:27 2008 -0400
> 
>     [PATCH] double-free of inode on alloc_file() failure exit in create_write_pipe()
>     
>     Duh...  Fortunately, the bug is quite recent (post-2.6.25) and, embarrassingly,
>     mine ;-/
>     
>     Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> 
> between 2.6.25 and 2.6.26.  So I think this can be closed with version
> 2.6.26-1 (if not earlier).

Thanks, closing the bug then.

Cheers,
        Moritz

--- End Message ---
Reply to: