linux-kernel - Re: ixgbe: fix possible data corruption in read_i2c

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

Message-ID: <CAKocOONU=S7w2bDc1Hf+PqP=pjJ14sdKOVC4UZH7ymx6h+vcyA@mail.gmail.com>
Date:	Thu, 21 Feb 2013 10:36:38 -0700
From:	Shuah Khan <shuahkhan@...il.com>
To:	jeffrey.t.kirsher@...el.com, emil.s.tantilov@...el.com,
	phillip.j.schmitt@...el.com
Cc:	linux-kernel@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
	stable <stable@...r.kernel.org>
Subject: Re: ixgbe: fix possible data corruption in read_i2c_byte

On Wed, Feb 20, 2013 at 8:33 PM, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org> wrote:
> Gitweb:     http://git.kernel.org/linus/;a=commit;h=d0310dc415a670ae2b2e27076b4685d988830479
> Commit:     d0310dc415a670ae2b2e27076b4685d988830479
> Parent:     4c696ca9fbabc5f94a3c6db7f009e73f0ef21831
> Author:     Emil Tantilov <emil.s.tantilov@...el.com>
> AuthorDate: Fri Jan 18 02:16:41 2013 +0000
> Committer:  Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> CommitDate: Fri Feb 15 23:16:09 2013 -0800
>
>     ixgbe: fix possible data corruption in read_i2c_byte
>
>     This patch makes sure that the SW lock is released after all i2c
>     operations complete in the retry code path.
>
>     Signed-off-by: Emil Tantilov <emil.s.tantilov@...el.com>
>     Tested-by: Phil Schmitt <phillip.j.schmitt@...el.com>
>     Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>

Jeff,

Should this patch be considered for stable? This patch applied cleanly
to 3.7 and 3.4. I haven't done any testing yet.

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