Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Jul 2019 18:38:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 234134] Increase VM_MAX_NAMELEN value
Message-ID:  <bug-234134-27103-3FVWBS5uSU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-234134-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-234134-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234134

--- Comment #14 from commit-hook@freebsd.org ---
A commit references this bug:

Author: scottl
Date: Fri Jul 12 18:37:57 UTC 2019
New revision: 349948
URL: https://svnweb.freebsd.org/changeset/base/349948

Log:
  Tie the name limit of a VM to SPECNAMELEN from devfs instead of a
  hard-coded value. Don't allocate space for it from the kernel stack.
  Account for prefix, suffix, and separator space in the name. This
  takes the effective length up to 229 bytes on 13-current, and 37 bytes
  on 12-stable. 37 bytes is enough to hold a full GUID string.

  PR:           234134
  MFC after:    1 week
  Differential Revision:        http://reviews.freebsd.org/D20924

Changes:
  head/sys/amd64/include/vmm.h
  head/sys/amd64/include/vmm_dev.h
  head/sys/amd64/vmm/vmm_dev.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234134-27103-3FVWBS5uSU>