From: ebiederm@xmission.com (Eric W. Biederman)
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [-next July 9 - s390 ] Badness at fs/sysfs/symlink.c:82 during qeth initalization
Date: Fri, 09 Jul 2010 03:39:24 -0700 [thread overview]
Message-ID: <m14og95483.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4C36F974.4030608@in.ibm.com> (Sachin Sant's message of "Fri\, 09 Jul 2010 15\:57\:00 +0530")
Sachin Sant <sachinp@in.ibm.com> writes:
> 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
Ugh. It looks like the warning is correct and I have a regression
in 2.6.35 that was overlooked because I did not closely test
CONIFG_SYSFS_DEPRECATED. I will see if I can cook up a proper
patch shortly.
Eric
next prev parent reply other threads:[~2010-07-09 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 5:01 linux-next: Tree for July 9 Stephen Rothwell
2010-07-09 9:45 ` [-next July 9 - s390 ] Badness at fs/sysfs/symlink.c:82 during qeth initalization Sachin Sant
2010-07-09 10:08 ` Eric W. Biederman
2010-07-09 10:27 ` Sachin Sant
2010-07-09 10:39 ` Eric W. Biederman [this message]
2010-07-09 14:28 ` Greg KH
2010-07-09 15:33 ` Martin Schwidefsky
2010-07-09 15:59 ` Greg KH
2010-07-09 15:56 ` Sachin Sant
2010-07-11 22:27 ` linux-next: Tree for July 9 (serial/max3107) Randy Dunlap
2010-07-19 16:16 ` Randy Dunlap
2010-07-19 16:31 ` Alan Cox
2010-07-11 22:29 ` linux-next: Tree for July 9 (staging/batman-adv and staging/dt3155) Randy Dunlap
2010-07-11 22:33 ` linux-next: Tree for July 9 (staging/ti_st) Randy Dunlap
2010-07-19 15:54 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m14og95483.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sachinp@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.