Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

[Rick Macklem]

NAGY Andreas wrote:
>Compiling with the last patch also failed:
>
>error: use of undeclared identifier 'NFSV4OPEN_WDSUPPFTYPE

If you apply the attached patch along with wantdeleg.patch, it should
build. At most, this will get rid of the warnings about invalid reason for
not issuing a delegation, so the wantdeleg*.patches probably aren't very
interesting.

rick



wantdeleg2.patch
Description: wantdeleg2.patch
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

[Rick Macklem]

NAGY Andreas wrote:
>Okay, that was the main reason for using NFS 4.1.
>Is it planned to implement it, or is the focus on pNFS?
Do the VMware people claim that this improves performance?
(I know nothing about the world of VMs, but for real hardware
 I can't see any advantage of having more than one TCP connection?
 As far as I know, the Linux client never tries to acquire a second TCP
 connection. I would have assumed trunking would be handled below
 TCP.)

This is the first client that I am aware of (and just yesterday when you pointed
it out) that uses BIND_CONN_TO_SESSION for an additional TCP connection.
(Up until now I was only aware of it being used for RDMA setups and I have no
 hardware to play with such things.)

If the VMware folk claim it does improve performance, I might get around to
it someday, although you are correct that I am working on pNFS support for the
server right now.

rick
[stuff snipped]

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: DDD hangs on start on 11.1-R

[John Baldwin]

On Monday, March 05, 2018 08:19:24 AM Daniel Eischen wrote:
> On Mon, 5 Mar 2018, Trond Endrest�l wrote:
> 
> > On Sat, 3 Mar 2018 18:09+0100, Holm Tiffe wrote:
> >
> >> can anyone get ddd get to work in 11.1-R or stable?
> >
> > I've more or less given up on devel/ddd, since it relies on the old
> > pty subsystem, now replaced by the new pts subsystem, to communicate
> > with gdb.
> >
> > I build custom kernels containing "device pty", but I'm not sure if
> > that directive is being honoured these days.
> >
> > It's a shame, 'cos ddd is very good at visualizing data structures.
> > Maybe it's possible to patch ddd to use pts instead of pty.
> 
> I used to like ddd also.  You might try devel/gps.  It's more
> than just a debugger, but you can use it just for debugging.
> Note, it's been a while since I've used it, but worked similarly
> to ddd.

I patched ddd to use pts (was a short patch) but it still hangs for me
with both old and new gdb.  I think it is unfortunately abandonware. :(

-- 
John Baldwin

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

[NAGY Andreas]

Okay, that was the main reason for using NFS 4.1.
Is it planned to implement it, or is the focus on pNFS?

Thanks,
Andi



Von: Rick Macklem 
Gesendet: 05.03.2018 11:49 nachm.
An: NAGY Andreas; 'freebsd-stable@freebsd.org'
Betreff: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi 
client

Nope, that isn't supported, rick
(Hope no one is too upset by a top post.)


From: NAGY Andreas 
Sent: Monday, March 5, 2018 8:22:10 AM
To: Rick Macklem; 'freebsd-stable@freebsd.org'
Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi 
client

Thanks, I am actually compiling with both patches.

I try now to get NFS 4.1 multipathing working. So I have now two connection on 
different subnets between the ESXi host and the FreeBSD host with exports for 
the same mountpoint on both subnets.
Now I get the following errors in the vmkernel.log:
2018-03-05T13:06:07.488Z cpu10:66503)WARNING: NFS41: NFS41_Bug:2361: BUG - 
Invalid BIND_CONN_TO_SESSION error: NFS4ERR_NOTSUPP

Is there session trunking available in the FreeBSD NFS41 implementation?

Br,
andi

-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Montag, 5. März 2018 02:16
To: NAGY Andreas ; 'freebsd-stable@freebsd.org' 

Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi 
client

NAGY Andreas wrote:
[stuff snipped]
>In the source I saw nfs_async = 0; is it right that NFS will work in async 
>mode if I >compile the kernel with nfs_async = 1?
>
>I know the risk of running it async, but is it not the same risk having the 
>datastore >connected via iSCSI which standard is also not sync?
If you want to use it, you can just set it by setting the sysctl 
vfs.nfsd.async=1.
- If the server crashes/reboots you can lose data. Also, after the reboot, the
  client will only see an temporarily unresponsive server and will not have any
  indication of data loss.
  (I am not familiar with iSCSI, so I can't comment on how safe that is.)
- If you are using ZFS, there is also a ZFS config (sync=disabled). I'm not a 
ZFS
  guy, so I don't know anything more, but I'm sure others reading this list can
  tell you how to set it.
[more stuff snipped]
>So far I did not see any issue with the mount. Only in the vmkernel.log there 
>are >often following entrees:
>WARNING: NFS41: NFS41ValidateDelegation:608: Server returned improper
>>reason for no delegation: 2
The attached patch *might* get rid of these, although I don't think it matters 
much, since it is just complaining about the "reason" the server returns for 
not issuing a delegation (issuing delegations is entirely at the discretion of 
the server and is disabled by default).
[more stuff snipped]
Good luck with it, rick
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Call for Testing: 11.1-RELEASE Meltdown/Spectre mitigation merge

[Ed Maste]

Background
--

A number of issues relating to speculative execution were found last
year and publicly announced January 3rd. A variety of techniques used to
mitigate these issues have been committed to FreeBSD-CURRENT and have
been merged to the stable/11 branch.

The changes will be merged and released as an update to FreeBSD
11.1-RELEASE in the near future, but the candidate patch is now
available for broader testing.

The patch addresses these issues:

CVE-2017-5754 (Meltdown)


This issue relies on a speculative execution of instructions that
attempt to read kernel memory, but fault. Although the architectural
state is as expected (the faulting instruction is not retired), cache or
other microarchitectureal state is changed and may be used to observe
privileged data.

The mitigation is known as Page Table Isolation (PTI). PTI largely
separates kernel and user mode page tables, so that even during
speculative execution most of the kernel's data is unmapped and not
accessible.

A demonstration of the Meltdown vulnerability is available at
https://github.com/dag-erling/meltdown. A positive result is definitive
(that is, the vulnerability exists with certainty). A negative result
indicates either that the CPU is not affected, or that the test is not
capable of demonstrating the issue on the CPU (and may need to be
modified).

CVE-2017-5715 (Spectre V2)
--

Spectre V2 uses branch target injection to speculatively execute kernel
code at an address under an attacker's control.

There are two common mitigations for Spectre V2. This patch includes a
mitigation using Indirect Branch Restricted Speculation, a feature
available via a microcode update from processor manufacturers. The
alternate mitigation, Retpoline, is a feature available in newer
compilers and is available in FreeBSD-CURRENT now. It will be made
available in stable branches in the future.

Patch
-

The patch against 11.1-RELEASE is available at
https://people.freebsd.org/~emaste/patches/amd64_11.1_meltdown.3.patch

A patched kernel will automatically enable PTI on Intel CPUs, and the
status can be checked via the vm.pmap.pti sysctl:

# sysctl vm.pmap.pti
vm.pmap.pti: 1

The default setting can be overridden by setting loader tunable
vm.pmap.pti to 1 or 0 in /boot/loader.conf. This setting takes effect
only at boot.

The patch includes the IBRS mitigation for Spectre V2. To use the
mitigation the system must have an updated microcode; with older
microcode a patched kernel will function without the mitigation.

IBRS can be disabled via the hw.ibrs_disable sysctl (and tunable), and
the status can be checked via the hw.ibrs_active sysctl. IBRS may be
enabled or disabled at runtime. Additional detail on microcode updates
will follow.

Limitations
---

This patch applies only to 11.1-RELEASE. It does not include mitigations
for architectures other than amd64 (x86_64). Work on other branches,
architectures and vulnerabilities is ongoing, and will be available at a
later date.

Testing
---

We are soliciting functionality and performance results from testing
this 11.1-RELEASE patch under a variety of workloads. If you have the
ability to test, please apply the patch and run the system with your
usual workload and follow up with details, either here or directly to
me.

Benchmark data from our testing will soon be shared more widely. In
brief, the PTI mitigation shows on the order of a 30% impact on system
call microbenchmarks, to 1% to 2% for realistic workloads.

This work is supported by the FreeBSD Foundation.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Torfinn Ingolfsen]

On Fri, 2 Mar 2018 11:33:57 -0800
Pete Wright  wrote:

> 
> Hey there - thanks for testing!  I would recommend posting an issue on
> the Github repo for this.  If you could be sure to include which
> revision you are running (11-stable or 12-current revision) in addition
> to the version of the port/pkg you have install that'd be helpful.

Done.
Issue 38: https://github.com/FreeBSDDesktop/kms-drm/issues/38

HTH
-- 
Torfinn Ingolfsen 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 183817] [mac] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817

Kubilay Kocak  changed:

   What|Removed |Added

  Flags|mfc-stable9?, mfc-stable10? |mfc-stable10+,
   ||mfc-stable11+
Summary|[patch] [mac] [panic]   |[mac] kernel compiled with
   |kernel compiled with|options INVARIANTS and
   |options INVARIANTS and  |MAC_PORTACL panices if
   |MAC_PORTACL panices if  |loader loads mac_portacl.ko
   |loader loads mac_portacl.ko |too
   |too |
   Keywords|needs-qa, patch |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"