Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261262AbUKSJBT (ORCPT ); Fri, 19 Nov 2004 04:01:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261318AbUKSJBT (ORCPT ); Fri, 19 Nov 2004 04:01:19 -0500 Received: from asplinux.ru ([195.133.213.194]:48393 "EHLO relay.asplinux.ru") by vger.kernel.org with ESMTP id S261262AbUKSJBR (ORCPT ); Fri, 19 Nov 2004 04:01:17 -0500 Message-ID: <419DB6BA.5040901@sw.ru> Date: Fri, 19 Nov 2004 12:02:50 +0300 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: [BUG?] dev_close() is called with locks held Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 542 Lines: 20 Hello, looks like a bug in 2.4/2.6 kernels: 1. dev_close() function is blocking. it calls schedule() inside and calls blocking dev_deactivate() function. 2. But... call chain dev_ioctl() -> dev_ifsioc() -> dev_change_flags() calls dev_close() under read_lock(&dev_base_lock)... Bug? Kirill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/