linux-kernel - UDF possible NULL pointer usage

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>] [day] [month] [year] [list]

Date:	Sun, 18 Mar 2007 11:36:16 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Ben Fennema <bfennema@...con.csc.calpoly.edu>
Cc:	linux-kernel-list <linux-kernel@...r.kernel.org>
Subject: UDF possible NULL pointer usage

Hi Ben,

you know the udf_fill_inode() in inode.c does not
check if memory allocation failed:

	UDF_I_DATA(inode) = kmalloc(inode->i_sb->s_blocksize -
	sizeof(struct extendedFileEntry), GFP_KERNEL);

so the question I have is - what kind of handler there
should be: just exit out from the function or mark
the inode as bad?

		Cyrill

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