Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964905AbVJDS2R (ORCPT ); Tue, 4 Oct 2005 14:28:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964906AbVJDS2R (ORCPT ); Tue, 4 Oct 2005 14:28:17 -0400 Received: from kepler.fjfi.cvut.cz ([147.32.6.11]:13212 "EHLO kepler.fjfi.cvut.cz") by vger.kernel.org with ESMTP id S964902AbVJDS2Q (ORCPT ); Tue, 4 Oct 2005 14:28:16 -0400 Date: Tue, 4 Oct 2005 20:28:13 +0200 (CEST) From: Martin Drab To: "linux-os (Dick Johnson)" cc: Linux Kernel Mailing List Subject: Re: 2.4 in-kernel file opening In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1173 Lines: 35 On Tue, 4 Oct 2005, linux-os (Dick Johnson) wrote: > > On Tue, 4 Oct 2005, Martin Drab wrote: > > > On Tue, 4 Oct 2005, Martin Drab wrote: > > > >> On Tue, 4 Oct 2005, Martin Drab wrote: > >> ... > >>> things within the driver before the mmap() - I guess that should be > >>> possibble to do from within the fops->mmap(), but I also need to do > >>> something upon munmap()ping. Where should I place that? There doesn't seem > >>> to be any function that would be called upon user munmap(). :( > >> > >> Should this be placed at vmops->close()? > > > > Or does there have to be a separate ioctl call for that after the munmap() > > anyway? > > > > Martin > > Just grin and bear it. Do the right things at the right time. If you > need ioctl() just do it. It will save you loads of development and > debugging time. Further, somebody else will be able to maintain the > code when you get promoted. Right, OK. Thanks, Martin - 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/