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

Bug#498134: marked as done (hang in cow_break_link())

Your message dated Wed, 7 Oct 2009 22:12:04 +0200
with message-id <20091007201204.GF5445@inutil.org>
and subject line Re: your mail
has caused the Debian Bug report #498134,
regarding hang in cow_break_link()
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.)


-- 
498134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498134
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-1-vserver-686
Version: 2.6.26-4
Severity: important

It appears that copy-on-write links don't always work, sometimes resulting
in a lock up.  They are supposed to work this way:

echo "foo" >a
ln a b
setattr --iunlink a
# Now both files are immutable but will break away on a write attempt.
echo "bar" >>a
# The files should be separated now...

Alas, this is not enough to reproduce.


-- Package-specific info:
** Version:
Linux version 2.6.26-1-vserver-686 (Debian 2.6.26-4) (waldi@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 15:12:13 UTC 2008

** Not tainted

** Kernel log:
[478478.685620] INFO: task bash:15850 blocked for more than 120 seconds.
[478478.685651] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[478478.685687] bash          D e7af588b     0 15850  15848
[478478.685714]        f79d0140 00000082 7fffffff e7af588b 0001952e f79d02cc c180c140 00000000
[478478.685761]        f741da80 dcbdfdf4 00000002 00000000 dcbdfdf4 00000000 e8524fe9 ee65bb44
[478478.685820]        ed859e60 ed859e68 ed859e64 f79d0140 c02ec62c d99e5e0c ed859e68 f79d0140
[478478.685878] Call Trace:
[478478.685958]  [<c02ec62c>] __mutex_lock_slowpath+0x50/0x7b
[478478.686002]  [<c02ec4c2>] mutex_lock+0xa/0xb
[478478.689522]  [<c01849d4>] lookup_create+0x14/0x75
[478478.690491]  [<c01867dc>] cow_break_link+0xd3/0x3f9
[478478.690491]  [<f8b7d9e6>] jfs_permission+0x0/0xa [jfs]
[478478.690491]  [<c0183c9a>] permission+0x1ff/0x239
[478478.690491]  [<c01858cb>] __link_path_walk+0xa9d/0xb7f
[478478.690491]  [<c011a636>] __wake_up+0x29/0x39
[478478.690491]  [<c019078e>] mntput_no_expire+0x13/0xd9
[478478.690491]  [<c0185a14>] path_walk+0x67/0x70
[478478.690491]  [<c018c973>] __d_lookup+0x98/0xf6
[478478.690491]  [<c0183859>] __lookup_hash+0x3c/0xdf
[478478.690491]  [<c0186e47>] do_filp_open+0x345/0x6d3
[478478.690491]  [<c0132616>] remove_wait_queue+0xc/0x34
[478478.690491]  [<c022da7c>] tty_ldisc_deref+0x4c/0x5b
[478478.690491]  [<c017b726>] do_sys_open+0x40/0xb0
[478478.690491]  [<c017b7da>] sys_open+0x1e/0x23
[478478.690491]  [<c0103853>] sysenter_past_esp+0x78/0xb1
[478478.690491]  =======================

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (501, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Tue, Sep 01, 2009 at 07:24:50PM +0200, Moritz Muehlenhoff wrote:
> On Sun, Sep 07, 2008 at 02:36:22PM +0200, Adam Borowski wrote:
> > Package: linux-image-2.6.26-1-vserver-686
> > Version: 2.6.26-4
> > Severity: important
> > 
> > It appears that copy-on-write links don't always work, sometimes resulting
> > in a lock up.  They are supposed to work this way:
> > 
> > echo "foo" >a
> > ln a b
> > setattr --iunlink a
> > # Now both files are immutable but will break away on a write attempt.
> > echo "bar" >>a
> > # The files should be separated now...
> > 
> > Alas, this is not enough to reproduce.
> 
> Does this still occur with later kernel versions, such as 2.6.30?

No further feedback, closing the bug. If the problem persists, please
reopen the bug.
 
Cheers,
        Moritz

--- End Message ---
Reply to: