From: Laszlo Attila Toth <panther@balabit.hu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: David Miller <davem@davemloft.net>,
zdenek.kabelac@gmail.com, linux-kernel@vger.kernel.org,
Linus Torvalds <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 15:13:30 +0100 [thread overview]
Message-ID: <47B9928A.60202@balabit.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0802181441300.30955@jikos.suse.cz>
Jiri Kosina wrote:
> On Mon, 18 Feb 2008, Laszlo Attila Toth wrote:
>
>> 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.
>
> - write_lock_bh(&dev_base_lock);
> - dev->link_mode = nla_get_u8(tb[IFLA_LINKMODE]);
> - write_unlock_bh(&dev_base_lock);
> + if (dev->link_mode != nla_get_u8(tb[IFLA_LINKMODE])) {
> + write_lock_bh(&dev_base_lock);
> + dev->link_mode = nla_get_u8(tb[IFLA_LINKMODE]);
> + write_lock_bh(&dev_base_lock);
> + modified = 1;
> + }
> }
>
> 1) you are accessing dev->link_mode and tb[] outside the dev_base_lock
yes, because tb[IFLA_LINKMODE] is not used by someone else in this case
only dev->link_mode. Although its value is unpredictable in case of a
concurrent access in the condition, it does not affect the final value
of dev->link_mode but the length of the critical section remains
minimal. The if statement may be inside the lock.
> 2) there is obvious and immediate deadlock -- you acquire the
> dev_base_lock twice, without any unlock, just look at the chunk above
Indeed:
"Feb 16 16:51:49 sandman kernel: BUG: rwlock recursion on CPU#0,"
I missed it. I copied the code from another patch which didn't contain
the two locking statements and when I copied them back it became a
copy-paste bug.
> 3) even with this deadlock fixed, Rafael states that either NM or
> wpa_supplicant (I don't recall from top of my head) still don't work
That's bad. Does my suggestion solve the problem? Again:
- if (modified)
- netdev_state_change(dev);
+ if (modified && dev->flags & IFF_UP)
+ call_netdevice_notifiers(NETDEV_CHANGE, dev)
Regards,
Attila
next prev parent reply other threads:[~2008-02-18 14:13 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
2008-02-18 13:44 ` Jiri Kosina
2008-02-18 14:13 ` Laszlo Attila Toth [this message]
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=47B9928A.60202@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