[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100709155941.GA2086@kroah.com>
Date: Fri, 9 Jul 2010 08:59:41 -0700
From: Greg KH <greg@...ah.com>
To: Martin Schwidefsky <schwidefsky@...ibm.com>
Cc: Sachin Sant <sachinp@...ibm.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-s390@...r.kernel.org, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [-next July 9 - s390 ] Badness at fs/sysfs/symlink.c:82 during
qeth initalization
On Fri, Jul 09, 2010 at 05:33:26PM +0200, Martin Schwidefsky wrote:
> On Fri, 9 Jul 2010 07:28:18 -0700
> Greg KH <greg@...ah.com> wrote:
>
> > On Fri, Jul 09, 2010 at 03:57:00PM +0530, Sachin Sant wrote:
> > > Eric W. Biederman wrote:
> > >>> With today's next(20100709) qeth interface fails to initialize
> > >>> with following Badness message:
> > >>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
> > >>>
> > >>
> > >> Is this with CONFIG_SYSFS_DEPRECATED set?
> > >>
> > >> I think I may have made my warning check a little extra strict.
> > >>
> > > Yes.
> > >
> > > CONFIG_SYSFS_DEPRECATED=y
> > > CONFIG_SYSFS_DEPRECATED_V2=y
> >
> > Why do you have those options enabled? Does your userspace really
> > require them? I want to remove those options soon, and it would be good
> > to find out what is still relying on them.
> >
> > If you disable those options, does it then work?
>
> The default configuration for s390 does not have the options enabled and
> with a recent userspace everything works just fine. From my point of view
> the two options can be removed.
Wonderful, thanks for letting me know.
Sachin, care to disable them in your image as well?
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