Linux 2.6.31.1

2009-09-24T15:45:25Z

Linux 2.6.31

2009-09-09T22:13:59Z

Linux 2.6.31-rc9

2009-09-05T23:38:12Z

Linux 2.6.31-rc8

2009-08-28T00:59:04Z

Linux 2.6.31-rc7

2009-08-22T01:00:46Z

Linux 2.6.31-rc6

2009-08-13T22:43:34Z

Linux 2.6.31-rc5

2009-08-01T00:40:45Z

Linux 2.6.31-rc4

2009-07-23T02:32:59Z

Add '-fno-delete-null-pointer-checks' to gcc CFLAGS

2009-07-16T16:19:16Z

Turning on this flag could prevent the compiler from optimising away some "useless" checks for null pointers. Such bugs can sometimes become exploitable at compile time because of the -O2 optimisation. See http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html An example that clearly shows this 'problem' is commit 6bf67672. static void __devexit agnx_pci_remove(struct pci_dev *pdev) { struct ieee80211_hw *dev = pci_get_drvdata(pdev); - struct agnx_priv *priv = dev->priv; + struct agnx_priv *priv; AGNX_TRACE; if (!dev) return; + priv = dev->priv; By reverting this patch, and compile it with and without -fno-delete-null-pointer-checks flag, we can see that the check for dev is compiled away. call printk # - testq %r12, %r12 # dev - je .L94 #, movq %r12, %rdi # dev, Clearly the 'fix' is to stop using dev before it is tested, but building with -fno-delete-null-pointer-checks flag at least makes it harder to abuse. Signed-off-by: Eugene Teo Acked-by: Eric Paris Acked-by: Wang Cong Signed-off-by: Linus Torvalds

Linux 2.6.31-rc3

2009-07-14T01:18:52Z

user/sven/linux.git/Makefile, branch v2.6.31.1