linux-kernel - Re: [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules

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: <5012460.vcYIRW5pg5@xrated>
Date:	Thu, 03 Sep 2015 11:20:54 +0200
From:	Hans-Peter Jansen <hpj@...la.net>
To:	Tejun Heo <tj@...nel.org>
Cc:	tim.gardner@...onical.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules

On Dienstag, 4. August 2015 14:05:20 Tejun Heo wrote:
> On Tue, Aug 04, 2015 at 11:26:04AM -0600, tim.gardner@...onical.com wrote:
> > From: Tim Gardner <tim.gardner@...onical.com>
> > 
> > Commit 37b1ef31a568fc02e53587620226e5f3c66454c8 ("workqueue: move
> > flush_scheduled_work() to workqueue.h") moved the exported non GPL
> > flush_scheduled_work() from a function to an inline wrapper.
> > Unfortunately, it directly calls flush_workqueue() which is a GPL
> > function.
> > This has the effect of changing the licensing requirement for this
> > function
> > and makes it unavailable to non GPL modules.
> > 
> > See commit ad7b1f841f8a54c6d61ff181451f55b68175e15a ("workqueue: Make
> > schedule_work() available again to non GPL modules") for precedent.
> > 
> > Cc: Tejun Heo <tj@...nel.org>
> > Signed-off-by: Tim Gardner <tim.gardner@...onical.com>
> 
> Applied to wq/for-4.3.
> 
> Thanks.

Tejun, mind CCing stable in this regard? 

As things stand right now, it's activily deferring 4.2 rollout for (evil, 
sure) nvidia users like me. 

Thanks,
Pete
--
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/