"Garrett D'Amore" <[EMAIL PROTECTED]> writes:
> Artem Kachitchkine wrote:
>>
>>> [EMAIL PROTECTED]> pfexec truss -f -t mount mount -F pcfs -o ro
>>> /dev/dsk/c2t0d0p0:1 /mnt
>>> 3708: mount("/dev/dsk/c2t0d0p0:1", "/mnt", MS_OPTIONSTR, "pcfs",
>>> 0x00000000, 0, 0x08063240, 1024) Err#30 EROFS
>>> mount: Read-only file system
>>
>> As another data point, submitter of 6642367 reports the same issue
>> with USB-connected SD media on snv_79 and claims that it used to work
>> on snv_64a.
>>
>> -Artem
>
> Furthermore, I can now confirm *verified* with kmdb that sdopen() is
> called with FWRITE. On the same call stack, the mount options is
> verified to contain MS_RDONLY at the pcfs_mount() call site. So the
> problem must lie within pcfs kernel code (and pcfs_vfsops.c most likley)
> itself.
>
> I'll take a look at that bug and update it appropriately.
It looks like a moderately recent change to pcfs splits out the mount
option parsing into a separate routine (pcfs_parse_mntopts), which
will set VFS_RDONLY if MS_RDONLY was passed down.
This is called *AFTER* the device has been opened in pcfs_mount,
however. So the device would get opened R/W even if you passed down
readonly.
I could be wrong though, this is from reading the code and a handful
of recent diffs, rather than test-n-verify.
-- Rich
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
