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] [day] [month] [year] [list]
Date:	Sun, 25 Jul 2010 16:05:45 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Dan Carpenter <error27@...il.com>
Cc:	David Airlie <airlied@...ux.ie>, Eric Anholt <eric@...olt.net>,
	Zhenyu Wang <zhenyuw@...ux.intel.com>, nanhai.zou@...el.com,
	Benny Halevy <bhalevy@...asas.com>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	"Jin, Gordon" <gordon.jin@...el.com>
Subject: Re: [patch] i915: take struct_mutex in i915_dma_cleanup()

On Wed, 23 Jun 2010 08:47:18 -0700, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> Reminds me, Gordon can you add module unload testing to your set of
> basic daily tests?  To unload you need to unbind the fbcon interface
> first, my script is like this:
> 
> echo 0 > /sys/class/vtconsole/vtcon1/bind
> rmmod i915
> rmmod drm_kms_helper
> rmmod drm
> modprobe i915
> echo 1 > /sys/class/vtconsole/vtcon1/bind

To which we could even add a kmemleak check.
After rmmod drm and before reloading i915:
echo scan > /sys/kernel/debug/kmemleak
cat /sys/kernel/debug/kmemleak > `hostname`-leaks.txt

If the output is not empty, file a bug. [Of course this means having to
compile kmemleak into the kernel. The DEBUG_KMEMLEAK option is found under
Kernel Hacking.] And since each generation has slightly different
initialization stanzas, we need to repeat the test on all platforms.
-- 
Chris Wilson, Intel Open Source Technology Centre
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ