Bug 141091 - [patch] [nullfs] fix panics with DIAGNOSTIC enabled
Summary: [patch] [nullfs] fix panics with DIAGNOSTIC enabled
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 1.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-02 03:00 UTC by Gleb Kurtsou
Modified: 2018-01-03 05:13 UTC (History)
0 users

See Also:


Attachments
file.diff (765 bytes, patch)
2009-12-02 03:00 UTC, Gleb Kurtsou
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gleb Kurtsou freebsd_committer 2009-12-02 03:00:12 UTC
null_checkvp function shouldn't be called from null_lock and null_unlock (through NULLVPTOLOWERVP(vp) macro)

null_lock and null_unlock code expects that some of "usual" assumptions on vnodes do not hold, e.g. during node creation and reclaim lower vnode can be null, etc.

example panic backtraces:

http://lists.freebsd.org/pipermail/freebsd-fs/2009-November/007176.html

Fix: disable vnode checks in null_lock and null_unlock

Patch attached with submission follows:
How-To-Repeat: recompile kernel with
options INVARIANT_SUPPORT
options INVARIANTS
options DIAGNOSTIC
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-12-02 04:55:31 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:15 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped