netdev - RE: [Intel-wired-lan] NULL dereference on v4.1.x while enabling VF

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: <F6FB0E698C9B3143BDF729DF2228664691EA7CAF@ORSMSX116.amr.corp.intel.com>
Date:	Fri, 6 May 2016 16:26:24 +0000
From:	"Skidmore, Donald C" <donald.c.skidmore@...el.com>
To:	William Dauchy <wdauchy@...il.com>
CC:	NETDEV <netdev@...r.kernel.org>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
	Alex Duyck <aduyck@...antis.com>
Subject: RE: [Intel-wired-lan] NULL dereference on v4.1.x while enabling VF

Hey William,

My validation hasn't be able to recreate the dereference on v4.1.x, v4.5.x or net_next.  Where exactly did you place the two line script in your rc scripts.  Our validation was able to run it as soon as ~14 second after the first boot message logged in dmesg.  Is this anywhere close to where you were executing it?  Likewise he has attempted running at both run level 3 and 5 in case that changed any of the times of how soon the rc scripts are executed.  So the more detail you can give of setup the more it might help us recreate what you are seeing.

Thanks,
-Don Skidmore <donald.c.skidmore>

 

> -----Original Message-----
> From: William Dauchy [mailto:wdauchy@...il.com]
> Sent: Tuesday, May 03, 2016 5:33 AM
> To: Skidmore, Donald C <donald.c.skidmore@...el.com>
> Cc: NETDEV <netdev@...r.kernel.org>; intel-wired-lan@...ts.osuosl.org;
> Alex Duyck <aduyck@...antis.com>
> Subject: Re: [Intel-wired-lan] NULL dereference on v4.1.x while enabling VF
> 
> Hello Don,
> 
> Thank you for your reply.
> 
> On Mon, May 2, 2016 at 11:33 PM, Skidmore, Donald C
> <donald.c.skidmore@...el.com> wrote:
> > Thanks for reporting the dereference.  Could you provide a little more
> detail on how you created this issue?  Are you just running the two
> commands (ip, sriov_numvfs) in some rc script and if you put a few second
> sleep in front of it you don't see the failure?
> 
> Your understanding is correct; a rc script is run with ip and echo in numvfs
> commands. I tried to reduce it to the minimum. If I put a sleep
> 20 in front of it, it does not crash. I also forgot to add I did not had the issue
> in 3.14.x with the same script.
> 
> Best,
> --
> William