linux-kernel - Re: [PATCH] omapdrm: use alloc_ordered_workqueue() instead of UNBOUND w/ max

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: <CAO8GWqmBakf9gLmFh7q3DWWkAzSiUoa09F2dP8MJ2B5E_66fRA@mail.gmail.com>
Date:	Thu, 23 Aug 2012 15:08:59 -0500
From:	"Clark, Rob" <rob@...com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Tony Lindgren <tony@...mide.com>, linux-omap@...r.kernel.org,
	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH] omapdrm: use alloc_ordered_workqueue() instead of UNBOUND
 w/ max_active = 1

On Wed, Aug 22, 2012 at 6:49 PM, Tejun Heo <tj@...nel.org> wrote:
> This is an equivalent conversion and will ease scheduled removal of
> WQ_NON_REENTRANT.
>
> Only compile tested.
>
> Signed-off-by: Tejun Heo <tj@...nel.org>

I've tested it

Signed-off-by: Rob Clark <rob@...com>

> ---
>  drivers/staging/omapdrm/omap_drv.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/omapdrm/omap_drv.c b/drivers/staging/omapdrm/omap_drv.c
> index 4beab94..672cb3a 100644
> --- a/drivers/staging/omapdrm/omap_drv.c
> +++ b/drivers/staging/omapdrm/omap_drv.c
> @@ -571,8 +571,7 @@ static int dev_load(struct drm_device *dev, unsigned long flags)
>
>         dev->dev_private = priv;
>
> -       priv->wq = alloc_workqueue("omapdrm",
> -                       WQ_UNBOUND | WQ_NON_REENTRANT, 1);
> +       priv->wq = alloc_ordered_workqueue("omapdrm", 0);
>
>         INIT_LIST_HEAD(&priv->obj_list);
>
--
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/