r336243 ian July 13, 2018, 4:37 p.m.
r336242 ian July 13, 2018, 4:33 p.m.
newer versions of gpart that show mbr efi partition types with the name
'efi' rather than as '!239'.
r336241 ian July 13, 2018, 4:32 p.m.
r336240 ian July 13, 2018, 4:30 p.m.
newer versions of gpart that show mbr efi partition types with the name
'efi' rather than as '!239'.
r336239 rmacklem July 13, 2018, 12:39 p.m.
an I/O attempt on a DS to the server via LayoutReturn.

The current FreeBSD client can generate these errors for an operational
DS while doing a recovery of a mirror after a mirrored DS has been repaired.
I am not sure why these errors occur, but my best current guess is a race
between the Layout Recall issued by the kernel code run from pnfsdscopymr(8)
and a Read operation on the DS for the file bing copied.
The errrors are not fatal, since the client falls back on doing I/O through
the MDS, which can do the I/O successfully as a proxy. (The fact that the
MDS can do this indicates that the file does still exist on the functioning
This patch only affects behaviour of the pNFS client and only when using
Flexible File layouts.

MFC after:	2 weeks
r336238 brooks July 13, 2018, 11:32 a.m.
In practice, this moves the padding from below the canary to above
execpathp has no impact on stack consumption.

Submitted by:		Wuyang-Chung (via github pull request #159)
MFC after:	1 week
r336237 trociny July 13, 2018, 7:08 a.m.
Reviewed By:	pjd
Approved By:	pjd
Differential Revision:	https://reviews.freebsd.org/D11531
r336236 delphij July 13, 2018, 2:02 a.m.
If the number of FATs field in the boot sector is zero, give
an appropriate error code.

Obtained from:	Android https://android.googlesource.com/platform/external/fsck_msdos/+/6c29bbe8d58e6fe8755935a04166ecf82ff31f47%5E%21/
MFC after:	2 weeks
r336232 mjg July 12, 2018, 10:48 p.m.
The optimisation seen with malloc cannot be used here as zone sizes are
now known at compilation. Thus bzero by hand to get the optimisation
r336231 mjg July 12, 2018, 10:35 p.m.
See r333052.
r336230 mjg July 12, 2018, 10:34 p.m.
No functional changes.
r336229 rmacklem July 12, 2018, 8:46 p.m.
Without this patch, the NFSv4.1 pNFS client shared a single TCP connection
for all DSs that resided on the same machine. This made disabling one of
the DSs impossible. Although unlikely, it is possible that the storage
subsystem has failed in such a way that the storage for one DS on a machine
is no longer functioning correctly, but the storage used by another DS on
the same machine is still ok. For this case, it would be nice if a system
can fail one of the DSs without failing them all.
This patch changes the default behaviour to use separate TCP connections
for each DS even if they reside on the same machine.
I do not believe that this will be a problem for extant pNFS servers, but
a sysctl can be set to restore the old behaviour if this change causes a
problem for an extant pNFS server.
This patch only affects the NFSv4.1 pNFS client.

MFC after:	2 weeks
r336227 dim July 12, 2018, 7:02 p.m.
Request init/fini array on FreeBSD 12 and later


  It seems a bad idea to change the default in the middle of a release
  branch due to possible changes in global ctor / dtor ordering between
  .ctors and .init_array. With FreeBSD 11.0's release imminent lets
  change the default now for FreeBSD 12 (the current development
  stream) and later.

  FreeBSD rtld has supported .init_array / .fini_array for many years.
  As of Jan 1 2017 all supported FreeBSD releases and branches will
  have support.

  Reviewers: dim, brooks, arichardson

  Reviewed By: dim, brooks, arichardson

  Subscribers: bsdjhb, krytarowski, emaste, cfe-commits

  Differential Revision: https://reviews.llvm.org/D24867

Requested by:	jhb
MFC after:	3 days
r336226 markj July 12, 2018, 6:48 p.m.
Reported by:	scan-build, via Mark Millard
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D16180
r336225 markj July 12, 2018, 6:44 p.m.
Submitted by:	Greg V <greg@unrelenting.technology>
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D15398