linux-kernel - Re: [BUG] Upon hitting ^c, inotify blocks on mutex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081217194855.GA11188@flint.arm.linux.org.uk>
Date:	Wed, 17 Dec 2008 19:48:56 +0000
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Linux Kernel List <linux-kernel@...r.kernel.org>, stable@...nel.org
Cc:	Al Viro <viro@....linux.org.uk>
Subject: Re: [BUG] Upon hitting ^c, inotify blocks on mutex_lock

On Sat, Dec 13, 2008 at 04:41:23PM +0000, Russell King wrote:
> Today, having had gthumb running for a while, I hit ^c expecting it to
> quit.  The result was a process with zero VSZ and RSS, and it sitting
> in run state.  Only possible recovery action seems to be a reboot.

Al Viro looked into this, and suggested that 711a49a might fix the
problem.  I've just tested this on top of 2.6.27.8, and it does
indeed appear to fix the problem.  Suggest it should be included
in the next stable kernel.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/