mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	Ismail D?nmez <ismail@pardus.org.tr>,
	Adrian Bunk <bunk@stusta.de>, Thomas Meyer <thomas@m3y3r.de>,
	Tobias Diedrich <ranma@tdiedrich.de>
Subject: Re: [PATCH 2.6.21-rc4] ieee1394: fix oops on "modprobe -r ohci1394" after network class_device conversion
Date: Sun, 13 May 2007 13:43:50 +0200	[thread overview]
Message-ID: <4646F9F6.3040308@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.f2e7e842cff5a275@s5r6.in-berlin.de>

I wrote on 2007-03-21:
> On 20 Mar, Greg KH wrote:
>> On Tue, Mar 20, 2007 at 10:43:22PM +0100, Stefan Richter wrote:
>>> @@ -586,7 +586,10 @@ static void ether1394_add_host (struct h
>>>          }
>>>  
>>>  	SET_MODULE_OWNER(dev);
>>> +#if 0
>>> +	/* FIXME - Is this the correct parent device anyway? */
>>>  	SET_NETDEV_DEV(dev, &host->device);
>>> +#endif
>> That's interesting.  What does 'tree /sys/class/net/' look like with
>> this patch applied?  Does the eth1394 device now live off in
>> /sys/device/virtual?
> 
> Yes.
> 
> lrwxrwxrwx  1 root root 0 Mär 21 01:02 eth0 -> ../../devices/pci0000:00/0000:00:0b.0/eth0/
> lrwxrwxrwx  1 root root 0 Mär 21 01:02 eth1 -> ../../devices/virtual/net/eth1/
> lrwxrwxrwx  1 root root 0 Mär 21 01:02 lo -> ../../devices/virtual/net/lo/
> 
> (eth1 is IP over 1394 alias eth1394. eth0 is an actual ethernet
> interface.)
> 
> And eth1/device (ex -> ../../../devices/pci*___*/fw-host*) is now gone.
> Would anybody miss it?
> 
>> If so, I guess this is ok for now as we can wait for the rewrite of the
>> ieee1394 subsystem to get the linking done correctly :)
> 
> That's my hope too.

Alas there is some userspace breakage:
https://bugs.gentoo.org/show_bug.cgi?id=177199

| Ethernet over firewire devices (driver: eth1394) have - starting with
kernel
| 2.6.21 - no longer a proper parent-device/subsystem in sysfs.
|
| The code change resulting in this is:
[...]
| This missing parent-device breaks persistence-net, as that adds
DRIVERS=="?*"
| to the generated rules, but the driver-attribute resides in the
parent-device
| that no longer is available now.
|
| This leads to not matching the existing rule, but at every boot
running into
| the code to get a new number for the interface, and thus enlarging the
ruleset
| with one line at every boot.

I didn't notice this problem on my own Gentoo box here.  But then I
rarely reboot and don't automatically load eth1394 anymore since I
applied a post-2.6.21 patch which uncouples ieee1394 from eth1394.  I
still load it manually for frequent testing though.
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

  reply	other threads:[~2007-05-13 11:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14  4:42 Ooops with suspend to RAM Ismail Dönmez
2007-03-14 11:14 ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Stefan Richter
2007-03-14 11:45   ` oops in __nodemgr_remove_host_dev Stefan Richter
2007-03-14 16:58   ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Ismail Dönmez
2007-03-14 18:25     ` Stefan Richter
2007-03-14 22:51       ` Ismail Dönmez
2007-03-15  0:08         ` Stefan Richter
2007-03-15  0:14           ` Stefan Richter
2007-03-15  0:45           ` Ismail Dönmez
2007-03-15  0:49           ` Ismail Dönmez
2007-03-16 19:46             ` Stefan Richter
2007-03-20 21:43             ` [PATCH 2.6.21-rc4] ieee1394: fix oops on "modprobe -r ohci1394" after network class_device conversion Stefan Richter
2007-03-20 22:26               ` Ismail Dönmez
2007-03-21 18:11                 ` Stefan Richter
2007-03-20 23:34               ` Greg KH
2007-03-21  0:16                 ` Stefan Richter
2007-05-13 11:43                   ` Stefan Richter [this message]
2007-05-20 20:21                     ` Stefan Richter
2007-03-14 11:50 ` Ooops with suspend to RAM Adrian Bunk
2007-03-14 16:59   ` Ismail Dönmez

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=4646F9F6.3040308@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=ismail@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=ranma@tdiedrich.de \
    --cc=thomas@m3y3r.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®