netdev - Question about locks in qdisc

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-next>] [day] [month] [year] [list]

Date:	Mon, 27 Apr 2009 12:48:57 -0700
From:	Tom Herbert <therbert@...gle.com>
To:	netdev@...r.kernel.org
Subject: Question about locks in qdisc_restart

In qdisc_restart the qdisc lock is released before taking the
netif_tx_lock, and only acquired again after unlocking the
netif_tx_lock.  There's a comment with the function that
"qdisc_lock(q) and netif_tx_lock are mutually exclusive, if one is
grabbed, another must be free."  Can anyone tell me the motivation for
this restriction?  We are seeing some performance improvements by
holding the lock through qdisc_restart, and I'm not sure why this
would be bad to do.

Thanks,
Tom
--
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