public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Attila Toth <panther@balabit.hu>
To: David Miller <davem@davemloft.net>, zdenek.kabelac@gmail.com
Cc: jkosina@suse.cz, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: My system stops during startup with curretn git tree of 2.6.25-rc2
Date: Mon, 18 Feb 2008 14:06:17 +0100	[thread overview]
Message-ID: <47B982C9.60207@balabit.hu> (raw)
In-Reply-To: <20080217.183621.110686685.davem@davemloft.net>

David Miller wrote:
> From: Jiri Kosina <jkosina@suse.cz>
> Date: Sun, 17 Feb 2008 13:04:59 +0100 (CET)
> 
>> On Sun, 17 Feb 2008, Zdenek Kabelac wrote:
>>
>>> It looks like there is something weird as my systems stops when the swap 
>>> is mounted. I've played bisection game and this is the commit which 
>>> makes the system unusable:
>>> # bad: [45b503548210fe6f23e92b856421c2a3f05fd034] [RTNETLINK]: Send a
>>> single notification on device state changes.
>>> git-bisect bad 45b503548210fe6f23e92b856421c2a3f05fd034
>>> I've tried to reverse this commit - and it has compiled & worked.
>> This commit is completely broken (it, for example, breaks locking around 
>> dev->link_mode), as has been already mentioned by Rafael at 
>> http://lkml.org/lkml/2008/2/15/542
>>
>> Dave, do you have a proper fix queued? Otherwise I would propose just to 
>> revert it completely from Linus' tree for now.
> 
> I just reverted and I'll push that to Linus.
> 

Okay, but I can't figure out what's the problem with it. I don't have 
wireless card on my linux box also I can't test it but everything else 
works. Swap is mounted.


The concurrency cannot be a problem because the write operation is 
protected by a lock.

My only idea is the notification itself, because the netdev_state_change 
function is used which calls rtmsg_ifinfo too.

void netdev_state_change(struct net_device *dev)
{
         if (dev->flags & IFF_UP) {
                 call_netdevice_notifiers(NETDEV_CHANGE, dev);
                 rtmsg_ifinfo(RTM_NEWLINK, dev, 0);
         }
}

Also last lines of my patch could be instead of
         if (modified)
                 netdev_state_change(dev);

the following:
if (modified && dev->flags & IFF_UP) {
   call_netdevice_notifiers(NETDEV_CHANGE, dev);
}

Regards,
Attila

  reply	other threads:[~2008-02-18 13:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 10:55 My system stops during startup with curretn git tree of 2.6.25-rc2 Zdenek Kabelac
2008-02-17 12:04 ` Jiri Kosina
2008-02-18  2:36   ` David Miller
2008-02-18 13:06     ` Laszlo Attila Toth [this message]
2008-02-18 13:44       ` Jiri Kosina
2008-02-18 14:13         ` Laszlo Attila Toth
2008-02-18 16:41           ` Rafael J. Wysocki
2008-02-18 17:03             ` Laszlo Attila Toth
2008-02-18 17:06               ` Rafael J. Wysocki
2008-02-19  4:51               ` David Miller
2008-02-19 10:54                 ` Jens Axboe
2008-02-19 11:11                   ` David Miller
2008-02-19 11:12                     ` Jens Axboe

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=47B982C9.60207@balabit.hu \
    --to=panther@balabit.hu \
    --cc=davem@davemloft.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zdenek.kabelac@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox