linux-kernel - Re: [PATCH] eeprom: at24: Add support for large EEPROMs connected to SMBus adapters

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:	Thu, 19 Mar 2015 06:30:14 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Wolfram Sang <wsa@...-dreams.de>
CC:	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] eeprom: at24: Add support for large EEPROMs connected
 to SMBus adapters

On 03/19/2015 01:16 AM, Wolfram Sang wrote:
>
>> I don't call that multi-master, though, so I guess we may have a bit of a
>> terminology problem.
>
> This is definately not a multi-master issue, I agree. It is just
> another issue I saw when thinking about your patch thoroughly again.
>
>> I'll see what I can come up with, but I am not sure if I'll find the time
>> before the 4.1 commit window opens. Company has a working solution (kind of),
>> so now I'll have to do this on my own time ;-).
>
> But their solution is buggy and needs a fix! :)
>
I ended up looking into this last night, and actually have some untested code.

However, looking through the kernel, the problem it solves turns out to be
wide-spread. Almost every caller of i2c_smbus_read_byte() does the call as
part of a call sequence, and thus has that very same problem. That includes,
for example, the max1363 and the ds2482 drivers, both of which are used
in our system. So, while the solution may be buggy, that bug is wide-spread
and no one really seems to care about it (or did not realize it). This gives
"needs a fix" a completely different scope.

Given that, I may spend some time trying to see if I can reproduce the problem
before trying to fix it.

Thanks,
Guenter

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