From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 47731] Null pointer dereference at strchr
Date: Thu, 20 Sep 2012 01:21:11 +0000 (UTC) [thread overview]
Message-ID: <20120920012111.5D7DA11FAE2@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-47731-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=47731
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #1 from Theodore Tso <tytso@mit.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.
next prev parent reply other threads:[~2012-09-20 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 21:50 [Bug 47731] New: Null pointer dereference at strchr bugzilla-daemon
2012-09-20 1:21 ` bugzilla-daemon [this message]
2012-09-20 2:12 ` [Bug 47731] " bugzilla-daemon
2012-09-21 4:21 ` bugzilla-daemon
2012-09-21 4:42 ` bugzilla-daemon
2012-09-24 3:01 ` bugzilla-daemon
2012-10-15 21:18 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120920012111.5D7DA11FAE2@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.