From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [patch] rewrite rd Date: Mon, 14 Jan 2008 09:47:55 -0700 Message-ID: <20080114164754.GL18741@parisc-linux.org> References: <20071204042628.GA26636@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Christian Borntraeger , "Eric W. Biederman" , Andrew Morton , rob@landley.net, Jens Axboe To: Nick Piggin Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:46085 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751525AbYANQr4 (ORCPT ); Mon, 14 Jan 2008 11:47:56 -0500 Content-Disposition: inline In-Reply-To: <20071204042628.GA26636@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Dec 04, 2007 at 05:26:28AM +0100, Nick Piggin wrote: > +static void copy_to_brd(struct brd_device *brd, const void *src, > + sector_t sector, size_t n) > +{ > + struct page *page; > + void *dst; > + unsigned int offset = (sector & (PAGE_SECTORS-1)) << SECTOR_SHIFT; > + size_t copy; > + > + copy = min((unsigned long)n, PAGE_SIZE - offset); > + page = brd_lookup_page(brd, sector); > + BUG_ON(!page); > + > + dst = kmap_atomic(page, KM_USER1); > + memcpy(dst + offset, src, copy); > + kunmap_atomic(dst, KM_USER1); You're using kmap_atomic, but I see no reason you can't be preempted. Don't you need to at least disable preemption while you have stuff atomically kmapped? -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."