Re: [PATCH] use NFS4_MAXMINOR instead of hard coded number

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

 



On Fri, Jan 24, 2014 at 8:28 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
> While we're at it, is there any harm to letting NFS4_MAXMINOR be much
> higher?  That would save the need to rebuild nfs-utils just because you
> want to test a kernel with new minor version support.

That does not work. This constant is used to generate the string to be
thrown into the kernel and the kernel complains about items in the
string it does not know about, even if they are disabled, like "-4.7".
It would work if at the same time you got a patch into the kernel that
it no longer complains about unknown items that are disabled.

Robert
--
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