bugDazuko - Bugs: bug #22294, FreeBSD panic due to how path...

 
 

bug #22294: FreeBSD panic due to how path names get resolved in 2.3.4(-pre1)

Submitted by:  None
Submitted on:  Tue 12 Feb 2008 03:37:52 PM UTC  
 
Status: NoneAssigned to: John Ogness <ogman>
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 07 Jun 2008 12:15:56 AM UTC, comment #3:

With the 2.3.5 release, this problem has been fixed (by reverting to the old method).

John Ogness <ogman>
Project AdministratorIn charge of this item.
Wed 13 Feb 2008 11:40:16 AM UTC, comment #2:

just noticed that the patches name is misleading, but that
should not matter since the comment at the top explains
what it's about :)

Anonymous
Wed 13 Feb 2008 11:27:47 AM UTC, comment #1:

Here is a patch which uses the new approach to resolve
path names on Linux only (currently all Linux variants,
but refining the conditions should easily be possible)
while it sticks with the old approach (referred to as
"anon resolve") on all other platforms. This default
can be overridden by the "--{enable,disable}-anon-resolve"
configure options, the summary will reflect the status.

The patch explicitly inserts -U... in the Makefile when
the new approach should be used. This is a difference
against an unpatched dazuko version, but should result
in the same behaviour. Optionally that -U... case could
be removed from the Makefile generation and only the -D...
will be inserted.

(file #15031)

Anonymous
Tue 12 Feb 2008 03:37:52 PM UTC, original submission:

FreeBSD kernels panic with dazuko 2.3.4-pre1 when
registered daemons start to use the kernel module.
Version 2.3.3 works fine. Adding the -DANONYMOUS_RESOLVE
compile time option to the 2.3.4-pre1 build works, too.
Which suggests that the panic occurs due to the recent
change in how the path names get resolved.

The attached file shows a post mortem debug session on
the saved core. Unfortunately the dazuko.ko module does
not contain enough debug information to resolve the line
numbers. But the affected namei() call is the one at the
very top of the freebsd_get_filename_full_fileinfo()
routine (that was determined by the "user space" seg flag
data in the nameidata structure).

The module seems to try to lookup the "/dev/null" path
spec, while the lookup() routine already fails for the
"dev" part of the path. The panic string is "lockmgr:
thread 0xc3809600, not exclusive lock holder 0xc3809900
unlocking".

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #15031:  patch-anon-resolve-on-linux-only.diff added by None (4KiB - application/octet-stream)
file #15029:  freebsd62-dazuko234pre1-panic-dump.txt added by None (4KiB - text/plain - post mortem debug session on FreeBSD 6.2 with Dazuko 2.3.4-pre1)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by ogman (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 07 Jun 2008 12:15:56 AM UTCogmanAssigned toNone=>ogman
      Open/ClosedOpen=>Closed
    Wed 13 Feb 2008 11:27:47 AM UTCNoneAttached File-=>Added patch-anon-resolve-on-linux-only.diff, #15031
    Tue 12 Feb 2008 03:37:53 PM UTCNoneAttached File-=>Added freebsd62-dazuko234pre1-panic-dump.txt, #15029

    Back to the top


    Powered by Savane 3.1-cleanup1