linux-kernel - Re: Incorrect size checks on mmap() for sysfs PCI resource files is breaking X?

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]

Message-ID: <20101116075959.GS14383@tux1.beaverton.ibm.com>
Date:	Mon, 15 Nov 2010 23:59:59 -0800
From:	"Darrick J. Wong" <djwong@...ibm.com>
To:	Dave Airlie <airlied@...il.com>
Cc:	Martin Wilck <martin.wilck@...fujitsu.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: Incorrect size checks on mmap() for sysfs PCI resource files
	is breaking X?

On Tue, Nov 16, 2010 at 05:53:35PM +1000, Dave Airlie wrote:
> On Tue, Nov 16, 2010 at 5:22 PM, Darrick J. Wong <djwong@...ibm.com> wrote:
> > Hi,
> >
> > I just loaded 2.6.37-rc2 on my machines, and I noticed that X no longer starts.
> > Running an strace of the X server shows that it's doing this:
> 
> Can you poinpoint when it went wrong? does 2.6.36 work okay?

Yes, 2.6.36 is ok.  2.6.37-rc1 was ok too.

> Just trying to figure out where the regression arrived.

Looks like it's commit 3b519e4ea618b6943a82931630872907f9ac2c2b which went in
11 Nov 2010.  I just submitted a patch that fixes it, at least for me.

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