linux-kernel - RE: VFs go missing with latest kernel

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

Date:	Wed, 1 Feb 2012 18:02:58 +0000
From:	"Rose, Gregory V" <gregory.v.rose@...el.com>
To:	David Ahern <daahern@...co.com>
CC:	'LKML' <linux-kernel@...r.kernel.org>
Subject: RE: VFs go missing with latest kernel

> -----Original Message-----
> From: David Ahern [mailto:daahern@...co.com]
> Sent: Wednesday, February 01, 2012 9:58 AM
> To: Rose, Gregory V
> Cc: 'LKML'
> Subject: Re: VFs go missing with latest kernel
> 
> On 02/01/2012 10:47 AM, Rose, Gregory V wrote:
> > I found this in the log file you sent me.  I had missed it yesterday.
> >
> > [   15.835223] igb 0000:07:00.0: 7 pre-allocated VFs found - override
> max_vfs setting of 7
> > [   15.835393] igb 0000:07:00.0: 7 VFs allocated
> >
> > I think that must be a bug in the code that searches for VFs already
> allocated and is the source of your problem.  I'll keep you updated on
> what I find but it has to be a bug in the VF device lookups.
> 
> Confused. What is pre-allocating the VFs during boot? Looking at my
> rc-scripts I am only set MAC addresses at boot. No VMs have been started
> yet. This setup has worked fine with Fedora 14 and 3.0 kernels; it's
> really the move to 3.3-rc that I hit the problem.

Nothing is pre-allocating the VFs.  That is the bug, the function I wrote to find pre-allocated VFs is messed up somehow.  Since it (mistakenly) thinks it's already found pre-allocated VFs, it doesn't call pci_enable_sriov() to allocate them.

- Greg

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