[Bug 212156] Problem with camperiphunit() interpretation of device hints

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Aug 25 17:40:53 UTC 2016


            Bug ID: 212156
           Summary: Problem with camperiphunit() interpretation of device
           Product: Base System
           Version: 10.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: mbrian at netapp.com

There's an issue with the way camperiphunit interprets device hints.
First, I discovered this because the cam(4) documentation lists the hint
name as:

when the code looks for:
(I've reported that separately).

However, the code in cam_periph.c (camperiphunit()) does:

        for (wired = 0; resource_find_dev(&i, dname, &dunit, NULL, NULL) == 0;
             wired = 0) {
                if (resource_string_value(dname, dunit, "at", &strval) == 0) {
                        if (strcmp(strval, pathbuf) != 0)
                if (resource_int_value(dname, dunit, "target", &val) == 0) {
                        if (val != target)
                if (resource_int_value(dname, dunit, "lun", &val) == 0) {
                        if (val != lun)
                if (wired != 0) {
                        unit = dunit;

This works correctly if all three hints exist and match. However, if one of
the hints does not exist (since it has the wrong name), this code will still
match. Then net result is that with several device that differ only by lun
number, all will match the first set of hints and an attempt will be made
to assign duplicate da<n> unit numbers.

I suspect that if (wired != 0) should be if (wired ==3).

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list