linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [PATCH] [RFC] EEE PC hangs when booting off battery
Date: Tue, 28 Apr 2009 11:27:32 +0100	[thread overview]
Message-ID: <49F6DA14.7030608@tuffmail.co.uk> (raw)
In-Reply-To: <1240912688.28835.10.camel@johannes.local>

Johannes Berg wrote:
> It seems the only reason lockdep doesn't warn is the detour to userspace
> (modprobe) and the waiting for a userspace task (waiting isn't lockdep
> annotated and I don't think it can be)
>
> It seems you cannot load a module while under _any_ lock, ever, since
> userspace might turn around and do something that requires that lock? I
> think we should probably add a warning to the code that waits for the
> userspace task:
>
> 	debug_check_no_locks_held(current);
>
> Or not? Some purely internal locks _might_ be ok... but how could you
> verify that?
>
>   
>> - ieee80211_wep_init(), which is called with rtnl_lock() held, is
>> blocked in request_module() [waiting for modprobe to load a crypto module].
>>     
>
> Right.
>
>   
>> - modprobe is blocked in a call to flush_workqueue(), caused by closing
>> a TTY.
>>     
>
> Can you point out where? I can't find that.
>   

I posted the calltraces earlier at
<http://marc.info/?l=linux-wireless&m=124074566523506&w=2>.

wait_for_completion
flush_cpu_workqueue
? wq_barrier_func
flush_workqueue
flush_scheduled_work
tty_ldisc_release
? tty_fasyc
tty_release_dev
? free_pgtables
tty_release
__fput
filp_close
sys_close
syscall_call


>> - worker_thread is blocked because the workqueue item linkwatch_event()
>> is blocked on rtnl_lock.
>>     
>
> This I know about.
>
>   
>> I've hacked up a test patch to move wep_init() outside of rtnl_lock, and
>> it solved the problem.  My one caveat is that it would probably be
>> cleaner to move it after rtnl_unlock(), instead of before rtnl_lock(). 
>> I just wasn't 100% sure if that would be safe.  Here's the patch:
>>     
>
> That doesn't seem relevant, this just does some initialisation. However,
> you definitely missed adding a call to wep_free().
>   

Hah, I should have realized something was wrong when I noticed I was
removing more lines that I added. 

The crypto init does cause the module load:

wait_for_completion
call_usermodehelper_exec
__request_module
crypto_larval_lookup
? extract_entropy
crypto_alg_mod_lookup
crypto_alloc_base
ieee80211_wep_init
ieee80211_register_hw
? ath5k_hw_set_bss
ath5k+pci_probe
local_pci_probe
pci_device_probe
driver_probe_device
__driver_attach
bus_for_each_dev
driver_attach
? __driver_attach
buad_add_driver
driver_register
? ktime_get_ts
__pci_register_driver
init_ath5k_pci
_stext
? init_ath5k_pci
? proc_create_data
? register_ieq_proc
kernel_init


Thanks
Alan


  reply	other threads:[~2009-04-28 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49E065CF.6040408@tuffmail.co.uk>
     [not found] ` <200904140859.02188.bjorn.helgaas@hp.com>
     [not found]   ` <20090414081728.10de978a@infradead.org>
     [not found]     ` <200904140948.37633.bjorn.helgaas@hp.com>
     [not found]       ` <49E5F01B.2060201@tuffmail.co.uk>
     [not found]         ` <49EF0ABD.2080801@tuffmail.co.uk>
2009-04-26 11:34           ` EEE PC hangs when booting off battery Alan Jenkins
2009-04-28  9:19             ` [PATCH] [RFC] " Alan Jenkins
2009-04-28  9:58               ` Johannes Berg
2009-04-28 10:27                 ` Alan Jenkins [this message]
2009-04-28 10:35                   ` Johannes Berg
2009-04-29 11:14                   ` Alan Jenkins
2009-04-29 11:20                     ` Johannes Berg
2009-05-15 21:48                     ` Rafael J. Wysocki
2009-05-16  8:39                       ` Alan Jenkins

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=49F6DA14.7030608@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=arjan@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).