Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932349AbZJHOut (ORCPT ); Thu, 8 Oct 2009 10:50:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758311AbZJHOut (ORCPT ); Thu, 8 Oct 2009 10:50:49 -0400 Received: from smtp.ispras.ru ([83.149.198.201]:50125 "EHLO smtp.ispras.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758308AbZJHOus (ORCPT ); Thu, 8 Oct 2009 10:50:48 -0400 From: Alexander Strakh Organization: ISP RAS To: Vladimir Shebordaev , Mauro Carvalho Chehab , linux-media@vger.kernel.org, Linux Kernlel Mailing List Subject: [BUG] radio-gemtek-pci.c: double mutex_lock Date: Thu, 8 Oct 2009 18:52:50 +0000 User-Agent: KMail/1.10.3 (Linux/2.6.27.29-0.1-default; KDE/4.1.3; x86_64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910081852.50816.strakh@ispras.ru> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1098 Lines: 34 KERNEL_VERSION: 2.6.31 DESCRIBE: In driver ./drivers/media/radio/radio-gemtek-pci.c mutex_lock is called first time in line 184, then in line 186 gemtek_pci_setfrequency is called. 182 static void gemtek_pci_unmute(struct gemtek_pci *card) 183 { 184 mutex_lock(&card->lock); 185 if (card->mute) { 186 gemtek_pci_setfrequency(card, card->current_frequency); 187 card->mute = false; 188 } 189 mutex_unlock(&card->lock);190 } In gemtek_pci_setfrequency we call mutex_lock again in line 152 144 static void gemtek_pci_setfrequency(struct gemtek_pci *card, unsigned long frequency) 145 { 146 int i; 147 u32 value = frequency / 200 + 856; 148 u16 mask = 0x8000; 149 u8 last_byte; 150 u32 port = card->iobase; 151 152 mutex_lock(&card->lock); Found by : Linux Driver Verification project -- 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/