linux-kernel - Re: [PATCH] driver core: remove polling for driver_probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d82e647a0901290735p6cdfd80bw520a47aa3e73aa80@mail.gmail.com>
Date:	Thu, 29 Jan 2009 23:35:14 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	kay.sievers@...y.org, greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] driver core: remove polling for driver_probe_done

2009/1/29 Arjan van de Ven <arjan@...radead.org>:
> On Thu, 29 Jan 2009 23:15:10 +0800
> tom.leiming@...il.com wrote:
>
>> From: Ming Lei <tom.leiming@...il.com>
>>
>> This patch renames driver_probe_done to driver_probe_wait_done,
>> and make it wait on condition variable of probe done to remove
>> polling for it in fs initialization.
>>
>
> I do not see where you add the wake_up() for waking up the wait queue...
> .... are you sure this is going to work ?

really_probe always wake up the queue of probe_waitqueue,
but no one pend on it. This patch adds the waitting on the queue.

static int really_probe(struct device *dev, struct device_driver *drv)
{
...
done:
        atomic_dec(&probe_count);
        wake_up(&probe_waitqueue);
        return ret;
｝

>
> --
> Arjan van de Ven        Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>



-- 
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/