linux-ext4 - [Bug 47731] Null pointer dereference at strchr

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2012 01:21:11 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 47731] Null pointer dereference at strchr

https://bugzilla.kernel.org/show_bug.cgi?id=47731


Theodore Tso <tytso@....edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu




--- Comment #1 from Theodore Tso <tytso@....edu>  2012-09-20 01:21:10 ---
Is this repeatable?   I'm having a lot of trouble figuring out the stack trace,
since strchr isn't used anywhere in the code path involved with printing the
ext4 mount options while returning the contents of /proc/mounts (which is
obviously what is going on).

The only strchr that looks even vaguely possible is the one used by
seq_escape() in fs/seq_file, which is called by mangle() and which is called by
show_vfsmnt() in fs/namespace.c.   But the stack trace doesn't look consistent
with that, either.   Part of the problem is between the inline functions, and
the function pointers used by show_vfsmnt, the stack dump in the OOPS message
can be quite misleading.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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