[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130725200845.GA19591@kroah.com>
Date: Thu, 25 Jul 2013 13:08:45 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Sony Chacko <sony.chacko@...gic.com>
Cc: Rajesh Borundia <rajesh.borundia@...gic.com>,
Shahed Shaikh <shahed.shaikh@...gic.com>,
Jitendra Kalsaria <jitendra.kalsaria@...gic.com>,
Dept-Eng Linux Driver <Linux-Driver@...gic.com>,
netdev <netdev@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: qlcnic binary sysfs file abuse
On Thu, Jul 25, 2013 at 07:37:46PM +0000, Sony Chacko wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@...uxfoundation.org]
> > Sent: Saturday, July 06, 2013 5:30 PM
> > To: Rajesh Borundia; Shahed Shaikh; Jitendra Kalsaria; Sony Chacko; Dept-Eng
> > Linux Driver
> > Cc: netdev; linux-kernel
> > Subject: qlcnic binary sysfs file abuse
> >
> > I was doing a kernel-wide audit on all of the binary sysfs files, and noticed a
> > metric ton of them in the qlcnic driver.
> >
> > So, any objection to me just deleting these entirely? Or, if they really are
> > needed, can I just move them to debugfs, which is where I think they should
> > have been from the beginning?
>
> Some applications are using these files, please move them to debugfs.
What applications care about the internal data structures of the kernel
driver? What can those applications do with that information? What
happens when you have a 64bit kernel on a 32bit userspace? How about
endian issues on different processor types? That sounds like a
nightmare to even consider getting correct...
Anyway, I'll move them to debugfs, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists