linux-kernel - Re: [PATCH][PCI]: Introduce pci_find_capability

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: <20080516191015.GB8111@ghostprotocols.net>
Date:	Fri, 16 May 2008 16:10:15 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, linux-rt-users@...r.kernel.org,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH][PCI]: Introduce pci_find_capability_cached and make
	MSI use it

Em Fri, May 16, 2008 at 12:01:48PM -0700, Jesse Barnes escreveu:
> On Friday, May 16, 2008 11:33 am Arnaldo Carvalho de Melo wrote:
> > > There are a few other common cap checks, but I don't think they compare
> > > to MSI in terms of latency sensitivity (though I didn't audit all the
> > > CAP_ID_EXP checks, there are quite a few of those).
> > >
> > > Since we know MSI is a problem, let's just go with fixing that for now. 
> > > If we find that other caps are also causing problems we can revisit
> > > caching all of them; the patch is simple enough.
> >
> > Do you want me to submit another patch or can you cook up one?
> 
> I can hack it up, probably not until Monday though (I'll be out of town this 
> weekend).

OK, for now this patch should be in the next rt patchset, we'll drop it
when you get The Right Thing merged 8)

- Arnaldo
--
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/