[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081017074453.GA4850@kroah.com>
Date: Fri, 17 Oct 2008 00:44:53 -0700
From: Greg KH <greg@...ah.com>
To: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>
Cc: Joel Becker <joel.becker@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
"Linux-iSCSI.org Target Dev"
<linux-iscsi-target-dev@...glegroups.com>,
SCST-Devel <scst-devel@...ts.sourceforge.net>,
Alan Stern <stern@...land.harvard.edu>,
Andrew Morton <akpm@...l.org>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] [ConfigFS]: Allow symbolic links from a SysFS struct
kobject source.
On Thu, Oct 16, 2008 at 11:55:55PM -0700, Nicholas A. Bellinger wrote:
> Hi Joel, Greg and Co,
>
> Here is the the first working code for allowing configfs to handle
> symlinks from sysfs struct kobject based code. Here is the commit:
> passing struct kobject into generic target_core_mod subsystem plugins
> for locating struct block_device and struct scsi_device..
Um, no.
You are trying to create symlinks dynamically across superblocks and
mount points? As one of your #warning states, this isn't possible to do
correctly, nor is it even a good idea.
So I'd have to reject this patch, sorry.
What is the problem you are attempting to solve here?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists