netdev - Re: r8169: is the work queue is initialized at wrong place?

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: <20130718215343.GA25075@electric-eye.fr.zoreil.com>
Date:	Thu, 18 Jul 2013 23:53:43 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Peter Wu <lekensteyn@...il.com>
Cc:	netdev@...r.kernel.org,
	Realtek linux nic maintainers <nic_swsd@...ltek.com>
Subject: Re: r8169: is the work queue is initialized at wrong place?

Peter Wu <lekensteyn@...il.com> :
[...]
> However, this queue is only initialized in rtl_open:
> 
> 6673         INIT_WORK(&tp->wk.work, rtl_task);
> 6674 
> 6675         smp_mb();
> 
> Shouldn't this INIT_WORK be done in rtl_init_one ?

(or cancel_work_sync in rtl8169_close to reduce the scope)

I do not see how the current code could hurt but it's really ugly.

> I do not know what this smp_mb is used for in this context, so I leave
> an appropriate patch up to you.

It does not cost much and it enforces an initialized state. IRQ - real
or shared ones - and napi poll could happen really soon after this point.
There is probably some implicit memory barrier the driver could rely on.
It would be a bit hackish though.

I'll check the history and cook a patch.

Thanks.

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html