Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 23 Mar 2001 06:02:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 23 Mar 2001 06:01:51 -0500 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:5389 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Fri, 23 Mar 2001 06:01:42 -0500 Subject: Re: [CHECKER] 4 warnings in kernel/module.c To: yjf@stanford.edu (Junfeng Yang) Date: Fri, 23 Mar 2001 11:03:49 +0000 (GMT) Cc: linux-kernel@vger.kernel.org, mc@cs.stanford.edu In-Reply-To: from "Junfeng Yang" at Mar 23, 2001 02:41:40 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Hi, we modified the block checker and run it again on linux 2.4.1. (The > block checker flags an error when blocking functions are called with > either interrupts disabled or a spin lock held. ) lock_kernel() isnt a spinlock as such. > 2. Can functions like kmem_cache_create, kmem_cache_alloc, alloc_page > block? They may block unless GFP_ATOMIC is specified in the arguments. Alan - 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/