linux-kernel - Re: [bug] CONFIG_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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090129161418.5ced2911@hyperion.delvare>
Date:	Thu, 29 Jan 2009 16:14:18 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Stephen Hemminger <shemminger@...tta.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [bug] CONFIG_I2C_VIAPRO=y breaks skge

On Thu, 29 Jan 2009 15:27:59 +0100, Ingo Molnar wrote:
> 
> * Jean Delvare <khali@...ux-fr.org> wrote:
> > This VIA chipset is the bridge over which the bugs run. Blaming on it 
> > for the problem you've hit would be similar to blaming the USB host 
> > controller driver for a bug that is in the USB keyboard or mouse driver.
> > 
> > The "other I2C drivers" don't run frequently at all now that you've 
> > disabled i2c-viapro. Without an I2C bus to probe on the machine, these 
> > drivers don't do anything.
> 
> ah, okay - i see - what i thought to be a surgical workaround has cut off 
> the whole leg. Will go back to find the ailing muscle instead.

Exactly.

> > So, again, if you are still willing to help me solve the problem, please 
> > boot the bad kernel and run:
> > 
> > $ ls -l /sys/bus/i2c/devices/*/driver
> > 
> > Then we'll know which drivers attached to I2C devices on your SMBus. 
> > Figuring out which one shouldn't have will likely be straightforward.
> 
> will take some time - but i'll revisit it.
> 
> Could you give me a short list of I2C driver .config options i should 
> disable one by one (instead of viapro) ?

I can't tell you before you give me the output of
  ls -l /sys/bus/i2c/devices/*/driver
for the broken system.

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