From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guenter Roeck Subject: Re: [PATCH] eeprom: at24: Add support for large EEPROMs connected to SMBus adapters Date: Thu, 19 Mar 2015 10:43:14 -0700 Message-ID: <20150319174314.GA17329@roeck-us.net> References: <20150204233516.GA1677@katana> <20150205002630.GA396@roeck-us.net> <20150205144028.GA4865@katana> <20150205175326.GA26691@roeck-us.net> <20150212040126.GA1691@roeck-us.net> <20150216120951.GA2840@katana> <20150317042049.GA6765@roeck-us.net> <20150318132707.GD3580@katana> <550A4162.8000009@roeck-us.net> <20150319081612.GA900@katana> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150319081612.GA900@katana> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Wolfram Sang Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Thu, Mar 19, 2015 at 09:16:21AM +0100, 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! :) > Turns out this is really easy to reproduce. One process reads the eeprom over and over again, another runs i2cdump in a loop, and voila ... lots of corruptions. Scary, especially considering how wide-spread this kind of i2c access is in the kernel. Guenter