linux-kernel - Re: [E1000-devel] [PATCH] RX initialization sequence fixed - enable RX after corresponding ring initialization only

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]

Date:	Fri, 19 Oct 2012 21:34:47 +0200
From:	Dmitry Fleytman <dmitry@...nix.com>
To:	Richard Davies <richard.davies@...stichosts.com>
Cc:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	linux-kernel@...r.kernel.org, e1000-devel@...ts.sourceforge.net,
	Chris Webb <chris.webb@...stichosts.com>
Subject: Re: [E1000-devel] [PATCH] RX initialization sequence fixed - enable
 RX after corresponding ring initialization only

Exactly. This patch is incorrect and should be ignored.

Dmitry.

On Fri, Oct 19, 2012 at 9:19 PM, Richard Davies
<richard.davies@...stichosts.com> wrote:
> Jeff Kirsher wrote:
>> Dmitry Fleytman wrote:
>> > Reported-by: Chris Webb <chris.webb@...stichosts.com>
>> > Reported-by: Richard Davies <richard.davies@...stichosts.com>
>> >
>> > Signed-off-by: Dmitry Fleytman <dmitry@...nix.com>
>> > ---
>> >  drivers/net/ethernet/intel/e1000/e1000_ethtool.c |    9 +++++----
>> >  drivers/net/ethernet/intel/e1000/e1000_main.c    |   18
>> > ++++++++++++++++--
>> >  2 files changed, 21 insertions(+), 6 deletions(-)
>>
>> I will add it to my queue.  Thanks!
>
> Hi Jeff,
>
> I hope it was already clear from the following discussion - this patch
> turned out to be a qemu-kvm bug and you do not need to apply it.
>
> Dmitry - please confirm.
>
> Richard.



-- 
Dmitry Fleytman
Technology Expert and Consultant,

Daynix Computing Ltd.

Cell: +972-54-2819481

Skype: dmitry.fleytman
--
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/