Date: Wed, 8 Sep 2004 11:47:39 +0100
From: viro@parcelfarce.linux.theplanet.co.uk
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] to add device+inode check to ipt_owner.c - HACKED UP
Message-ID: <20040908104739.GX23987@parcelfarce.linux.theplanet.co.uk>
References: <20040908100946.GA9795@lkcl.net> <20040908103922.GD9795@lkcl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040908103922.GD9795@lkcl.net>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 898
Lines: 26

On Wed, Sep 08, 2004 at 11:39:22AM +0100, Luke Kenneth Casson Leighton wrote:
> +static int
> +match_inode(const struct sk_buff *skb, const char *devname, unsigned long i_num)
> +{
> +	struct task_struct *g, *p;
> +	struct files_struct *files;
> +	/*
> +	struct inode *inode;
> +	struct super_block *sb;
> +	struct block_device *bd;
> +	*/
> +	int i;
> +	read_lock(&tasklist_lock);
> +
> +	/* lkcl: these are fairly obvious (just obtuse): hunt for the
> +	 * filesystem device, then its superblock, then the inode is
> +	 * relevant to that superblock, _then_ we can find the inode.
> +	bd = bdget(dev);


... the hell?  Where does that "dev" come from?
-
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/