linux-ext4 - smatch stuff: -next: null dereference in ext4

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

Date:	Sat, 1 Jan 2011 16:40:13 +0300
From:	Dan Carpenter <error27@...il.com>
To:	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: smatch stuff: -next: null dereference in ext4_readdir()

Hi Ted,

There is a NULL dereference introduced in linux-next "ext4: Use
ext4_error_file() to print the pathname to the corrupted inode"

fs/ext4/dir.c +170 ext4_readdir(59) error: potential null derefence 'bh'.
   168                  if (!bh) {
   169                          if (!dir_has_error) {
   170                                  EXT4_ERROR_FILE(filp, bh->b_blocknr,
                                                              ^^^^^^^^^^^^^
	"bh" is null here.

   171                                                  "directory contains a "
   172                                                  "hole at offset %Lu",
   173                                             (unsigned long long) filp->f_pos);
   174                                  dir_has_error = 1;

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html