linux-kernel - Re: [PATCH v2.6.36-rc7 2/2] shpchp: update workqueue usage

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: <20101015131714.432a7647@jbarnes-desktop>
Date:	Fri, 15 Oct 2010 13:17:14 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-pci@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Subject: Re: [PATCH v2.6.36-rc7 2/2] shpchp: update workqueue usage

On Fri, 15 Oct 2010 22:08:24 +0200
Tejun Heo <tj@...nel.org> wrote:

> Hello,
> 
> On 10/15/2010 09:52 PM, Jesse Barnes wrote:
> >> * Rename shpchp_wq to shpchp_ordered_wq and add non-ordered shpchp_wq
> >>   which is used instead of the system workqueue.  This is to remove
> >>   the use of flush_scheduled_work() which is deprecated and scheduled
> >>   for removal.
> >>
> >> * With cmwq in place, there's no point in creating workqueues lazily.
> >>   Create both shpchp_wq and shpchp_ordered_wq upfront.
> >>
> >> * Include workqueue.h from shpchp.h.
> > 
> > Applied these two, thanks.  I think Kenji-san will probably let me know
> > if pciehp suddenly breaks as a result. :)
> 
> Just in case, these are in no way aimed for v2.6.36.  They are at the
> earliest for v2.6.37-rc1.  Thanks a lot.

Of course, everything I've applied today has been for 2.6.37; 2.6.36 is
well closed now, there are no critical missing PCI fixes that I'm aware
of.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/