From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 51391] BUG: unable to handle kernel NULL pointer dereference
Date: Fri, 7 Dec 2012 17:10:51 +0000 (UTC) [thread overview]
Message-ID: <20121207171051.26AA711FB81@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51391-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=51391
--- Comment #3 from Theodore Tso <tytso@mit.edu> 2012-12-07 17:10:50 ---
I just built 3.2.29, and running under KVM, I created a file system, mounted it
with -o nodev, and then unmounted it. It didn't crash.
I then mounted it without nodev, ran "mknod /mnt/null c 3 1" to create a
/dev/null character device, unmounted the file system, remounted it with -o
nodev, tried writing to /mnt/null, which failed as it should, and then
unmounted the file system. Still no crash.
Can you tell me if there was anything else special about how you ran your test?
Did it fail right on the mount? Was this the root file system that you were
testing trying to mount -o nodev, etc.?
--
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-12-07 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:21 [Bug 51391] New: BUG: unable to handle kernel NULL pointer dereference bugzilla-daemon
2012-12-07 16:15 ` [Bug 51391] " bugzilla-daemon
2012-12-07 16:23 ` bugzilla-daemon
2012-12-07 16:25 ` bugzilla-daemon
2012-12-07 17:10 ` bugzilla-daemon [this message]
2012-12-07 17:12 ` bugzilla-daemon
2012-12-07 17:39 ` bugzilla-daemon
2012-12-07 18:04 ` bugzilla-daemon
2012-12-07 18:15 ` bugzilla-daemon
2012-12-07 20:13 ` bugzilla-daemon
2012-12-10 8:23 ` bugzilla-daemon
2013-02-11 10:04 ` 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=20121207171051.26AA711FB81@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).