linux-kernel - Re: [git pull] drm fixes

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: <CAPM=9twbX+eDG=DE8FSU7HUoe1dQ=9bx1QQw5T6nKAjQdSgi4w@mail.gmail.com>
Date:	Tue, 6 Dec 2011 16:36:33 +0000
From:	Dave Airlie <airlied@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm fixes

>
> What the heck is up?

Well I do care about kexec but only due to being forced into caring
about it for a certain enterprise distro that uses it a lot, so maybe
I was a bit biased in this case, and I dislike random memory
corruptions due to my subsystem even in the kexec case. Writing a
random 0 dword somewhere in memory isn't that pretty and no fun to
track down, when the kexec looks like it succeeds.

But I've no problem leaving it sitting around until -next.

The kzalloc->kcalloc ones are partly better integer overflow defence
where userspace passes in a number of objects but I just need to make
sure they are that and not cleanups, but I haven't gotten around to it
yet.

Cool I'll resend just the Intel and obvious radeon one and stick the
others into -next.

Dave.
--
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/