From: Dave Jones <davej@redhat.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Clayton <andrew@digital-domain.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: drm lockups since 2.6.11-bk2
Date: Tue, 15 Mar 2005 11:53:37 -0500 [thread overview]
Message-ID: <20050315165337.GG15531@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503151610560.443@skynet>
On Tue, Mar 15, 2005 at 04:15:42PM +0000, Dave Airlie wrote:
>
> > >
> > > I might get time to do a code review, my main worry is that all the
> > > problems reported with those patches in -mm made it into the patchset that
> > > went into Linus.. mainly things like forgetting to memset certain
> > > structures to 0 and sillies like that...
> >
> > I saw one report where the recent drm security hole fix broke dri
> > for one user. Whilst it seems an isolated incident, could this have
> > more impact than we first realised ?
>
> the radeon security changes? I've gotten no bad feedback on those neither
> has dri-devel, so I've assumed they were all fine (usually radeon bug
> reports get back fairly quickly as everyone has one ..),
>
> the multi-bridge stuff is definitely broken as I've seen radeon and r128
> reports on it .. and it looks most like 2.6.11-bk2 broke things and I
> haven't merged anything until -bk7 ...
Wait, -bk2 broke things ? The big agp changes went into -bk3,
so this seems odd.
Dave
next prev parent reply other threads:[~2005-03-15 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 10:38 Dave Airlie
2005-03-15 14:36 ` Dave Jones
2005-03-15 16:15 ` Dave Airlie
2005-03-15 16:41 ` Dave Jones
2005-03-15 16:53 ` Dave Jones [this message]
2005-03-15 16:56 ` Dave Airlie
2005-03-15 17:00 ` Andrew Clayton
2005-03-15 18:03 ` Jesse Barnes
2005-03-15 19:25 ` Andrew Morton
2005-03-15 19:36 ` Jesse Barnes
2005-03-15 23:27 ` Andrew Morton
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=20050315165337.GG15531@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=andrew@digital-domain.net \
--cc=dri-devel@lists.sourceforge.net \
--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®