2013/3/17 Chris Wilson :
> On Mon, Mar 18, 2013 at 07:42:58AM +1000, Dave Airlie wrote:
>> On Mon, Mar 18, 2013 at 7:40 AM, Chris Wilson
>> wrote:
>> > On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
>> >> On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson > >> chris-wilson.co.uk>
2013/3/17 Chris Wilson ch...@chris-wilson.co.uk:
On Mon, Mar 18, 2013 at 07:42:58AM +1000, Dave Airlie wrote:
On Mon, Mar 18, 2013 at 7:40 AM, Chris Wilson ch...@chris-wilson.co.uk
wrote:
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
On Sat, Mar 16, 2013 at 11:19 AM, Chris
On Mon, Mar 18, 2013 at 7:40 AM, Chris Wilson
wrote:
> On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
>> On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson
>> wrote:
>> > If *userspace* doesn't request either IOC_IN | IOC_OUT in their ioctl
>> > command (which are seperate from the
On Mon, Mar 18, 2013 at 07:42:58AM +1000, Dave Airlie wrote:
> On Mon, Mar 18, 2013 at 7:40 AM, Chris Wilson
> wrote:
> > On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
> >> On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson >> chris-wilson.co.uk> wrote:
> >> > If *userspace*
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
> On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson
> wrote:
> > If *userspace* doesn't request either IOC_IN | IOC_OUT in their ioctl
> > command (which are seperate from the ioctl number), then kdata is set to
> > NULL.
>
> Doesn't
On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson
wrote:
> On Fri, Mar 15, 2013 at 04:49:42PM -0700, Ben Widawsky wrote:
>> On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
>> > On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
>> > > On Fri, Mar 15, 2013 at 08:24:03AM
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
> Doesn't that mean that we need these checks everywhere? Or at least a
> fixup in drm core proper?
>
> And I think we need to add trinity to our test setup eventually ;-)
Note that trinity's ioctl fuzzing is still very new
On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson ch...@chris-wilson.co.uk wrote:
On Fri, Mar 15, 2013 at 04:49:42PM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson ch...@chris-wilson.co.uk
wrote:
If *userspace* doesn't request either IOC_IN | IOC_OUT in their ioctl
command (which are seperate from the ioctl number), then kdata is set to
On Mon, Mar 18, 2013 at 7:40 AM, Chris Wilson ch...@chris-wilson.co.uk wrote:
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
On Sat, Mar 16, 2013 at 11:19 AM, Chris Wilson ch...@chris-wilson.co.uk
wrote:
If *userspace* doesn't request either IOC_IN | IOC_OUT in their ioctl
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
Doesn't that mean that we need these checks everywhere? Or at least a
fixup in drm core proper?
And I think we need to add trinity to our test setup eventually ;-)
Note that trinity's ioctl fuzzing is still very new (added
On Fri, Mar 15, 2013 at 04:49:42PM -0700, Ben Widawsky wrote:
> On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
> > On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> > > On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > > > That's what I thought too.
On Fri, Mar 15, 2013 at 04:49:42PM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
That's what I thought too. Looking at
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > That's what I thought too. Looking at the stack trace, the empirical
> > evidence is that we need the check.
> > -Chris
>
> I think we need to investigate the issue
On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
> On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> > On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > > That's what I thought too. Looking at the stack trace, the empirical
> > > evidence is that we need
On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> On Thu, Mar 14, 2013 at 09:50:04PM -0700, Ben Widawsky wrote:
> > On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> > > In order to prevent a potential NULL deference with hostile userspace,
> > > we need to check
On Thu, Mar 14, 2013 at 09:50:04PM -0700, Ben Widawsky wrote:
> On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> > In order to prevent a potential NULL deference with hostile userspace,
> > we need to check whether the ioctl was passed an invalid args pointer.
> >
> > Reported-by:
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
In order to prevent a potential NULL deference with hostile userspace,
we need to check whether the ioctl was passed an invalid args pointer.
Reported-by: Tommi Rantala tt.rant...@gmail.com
Link:
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
In order to prevent a potential NULL deference with hostile userspace,
we need to check whether the ioctl was passed an invalid args pointer.
Reported-by: Tommi Rantala tt.rant...@gmail.com
Link:
On Thu, Mar 14, 2013 at 09:50:04PM -0700, Ben Widawsky wrote:
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
In order to prevent a potential NULL deference with hostile userspace,
we need to check whether the ioctl was passed an invalid args pointer.
Reported-by: Tommi
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
That's what I thought too. Looking at the stack trace, the empirical
evidence is that we need the check.
-Chris
I think we need to investigate the issue more then,
On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
That's what I thought too. Looking at the stack trace, the empirical
evidence is that we need the
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> In order to prevent a potential NULL deference with hostile userspace,
> we need to check whether the ioctl was passed an invalid args pointer.
>
> Reported-by: Tommi Rantala
> Link:
>
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> In order to prevent a potential NULL deference with hostile userspace,
> we need to check whether the ioctl was passed an invalid args pointer.
>
> Reported-by: Tommi Rantala
> Link:
>
24 matches
Mail list logo