From: Dave Young <hidave.darkstar@gmail.com>
To: linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Chris Wright <chrisw@sous-sol.org>
Subject: Regression - Xorg start failed
Date: Sun, 13 Feb 2011 14:22:14 +0800 [thread overview]
Message-ID: <20110213062213.GA2525@darkstar.dhcp.inet.fi> (raw)
Hi
With kernel built from current linus's tree, I can not start xorg,
it failed with:
Backtrace:
0: X(xorg_backtrace+0x26) [0x4e8bb6]
1: X(xf86SigHandler+0x39) [0x489989]
2: /lib64/libc.so.6 [0x7f077a6b9f30]
3: /usr/lib64/libpciaccess.so.0(pci_device_get_bridge_buses+0xf1) [0x7f077c101fd1]
4: X(initPciBusState+0x8d) [0x470abd]
5: X(xf86AccessInit+0xe) [0x48e26e]
6: X(InitOutput+0x108b) [0x466bfb]
7: X(main+0x20e) [0x42ceee]
8: /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f077a6a5526]
9: X [0x42c529]
Fatal server error:
Caught signal 11. Server aborting
The graphic driver I used is intel (i915)
Finally I bisected it, results:
47970b1b2aa64464bc0a9543e86361a622ae7c03 is first bad commit
commit 47970b1b2aa64464bc0a9543e86361a622ae7c03
Author: Chris Wright <chrisw@sous-sol.org>
Date: Thu Feb 10 15:58:56 2011 -0800
pci: use security_capable() when checking capablities during config space read
Eric Paris noted that commit de139a3 ("pci: check caps from sysfs file
open to read device dependent config space") caused the capability check
to bypass security modules and potentially auditing. Rectify this by
calling security_capable() when checking the open file's capabilities
for config space reads.
Reported-by: Eric Paris <eparis@redhat.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Signed-off-by: James Morris <jmorris@namei.org>
:040000 040000 e14ad9470ca5f84f13cd31eaf5def16d40bc54f1 cbf987647b8052214dd928c87c6becfb639e4ca2 M drivers
Any idea?
--
Thanks
Dave
next reply other threads:[~2011-02-13 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 6:22 Dave Young [this message]
2011-02-13 7:53 ` Dave Airlie
2011-02-13 15:50 ` Linus Torvalds
2011-02-14 0:35 ` Chris Wright
2011-02-14 1:04 ` James Morris
2011-02-15 1:21 ` [PATCH v3] pci: use security_capable() when checking capablities during config space read Chris Wright
2011-02-15 9:39 ` James Morris
2011-02-16 6:24 ` Alex Riesen
2011-02-14 5:38 ` Regression - Xorg start failed Dave Young
2011-02-14 16:56 ` Chris Wright
2011-02-13 23:31 ` Chris Wright
2011-02-13 23:34 ` Dave Airlie
2011-02-13 23:35 ` Chris Wright
2011-02-13 8:15 ` Alex Riesen
2011-02-13 20:26 Sedat Dilek
2011-02-14 16:01 Sedat Dilek
2011-02-14 16:20 ` Chris Wright
2011-02-14 16:35 ` Sedat Dilek
2011-02-14 16:57 ` Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110213062213.GA2525@darkstar.dhcp.inet.fi \
--to=hidave.darkstar@gmail.com \
--cc=airlied@linux.ie \
--cc=chrisw@sous-sol.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®