From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?B?7ZmN7IugIHNoaW4gaG9uZw==?= <hongshin@gmail.com>
Subject: BUG? deadlock bug at generic_shutdown_
Date: Thu, 30 Jul 2009 12:29:57 +0900
Message-ID: <2014bcab0907292029o6617b6a7n944cbd28edd39c10@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-gx0-f213.google.com ([209.85.217.213]:50990 "EHLO
	mail-gx0-f213.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753691AbZG3D35 (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 29 Jul 2009 23:29:57 -0400
Received: by gxk9 with SMTP id 9so2259583gxk.13
        for <linux-fsdevel@vger.kernel.org>; Wed, 29 Jul 2009 20:29:58 -0700 (PDT)
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Hi. I am reporting a suspected deadlock bug.

generic_shutdown_super() acquires lock_super(sb)
and then acquires lock_kernel().

However, do_remount() acquires lock_super() while
it holds lock_kernel().

Therefore, concurrent execution of generic_shutdown_super()
and do_remount() may result deadlock.

Please examine this report. Thank you.

Sincerely
Shin Hong