const laundering in nfs_parse_devname

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm playing around with some patches that will make strchr and friends
preserve constness (as in C++). Most of the fallout is trivially
fixable by changing a local "char *" to a "const char *". But in
nfs_parse_devname, there's a comma = strchr(dev_name, ',') after which
we may write to dev_name via comma, and I can't figure out if that's
ok. Does VFS expect the dev_name string to stay intact, or is the
constness mostly a matter of "you normally [won't have to/should not]
change this, but you can if you know what you're doing"?

Rasmus
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux