Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

Hi Chuck, On 17.05.2018 16:15, Chuck Lever wrote: > Just a shot in the dark: Wondering if v3.16 needs > > commit ea96d1ecbe4fcb1df487d99309d3157b4ff5fc02 > Author: Anna Schumaker > AuthorDate: Fri Apr 3 14:35:59 2015 -0400 > Commit: Trond Myklebust

Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

> On May 17, 2018, at 3:53 AM, Moritz Schlarb wrote: > > Hi everyone, > > there might be a regression coming from this patch: > Since it got included in 3.16.54, our clients running a recent 3.16 > kernel (like from Debian jessie-security) did not follow NFS 4.1 >

Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail

Any news to fix this behavior? Greetings...

Bug#898907: ethtool -K tso setting output noise msg "Cannot get device udp-fragmentation-offload settings: Operation not supported"

Package: ethtool Version: 1:4.8-1+b1 # uname -a Linux debian 4.16.0-0.bpo.1-arm64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) aarch64 GNU/Linux udp-fragmentation-offload is remove by the kernel. ethtool should remvoe it. related patch link: http://patchwork.ozlabs.org/patch/814796/ debian

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Hi, Using 10% of RAM for /run is a good default, but not suitable for all systems. 10% might be too small for system with less memory (e.g. virtual machine with 160 MiB RAM) or too big (VM host with 256/512 GiB RAM). A too small /run partition leads to not enough space on it. If the /run

Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

Hi everyone, there might be a regression coming from this patch: Since it got included in 3.16.54, our clients running a recent 3.16 kernel (like from Debian jessie-security) did not follow NFS 4.1 referrals (issued by nfs-ganesha) anymore. I have built that exact Debian kernel package with just

Bug#898165: marked as forwarded (linux-image-3.16.0-6-amd64: can't mount NFS shares via nfs referrals)

Your message dated Thu, 17 May 2018 09:53:33 +0200 with message-id <19d4d696-3abc-42cd-28fb-86a24b572...@uni-mainz.de> has caused the report #898165, regarding linux-image-3.16.0-6-amd64: can't mount NFS shares via nfs referrals to be marked as having been forwarded to the upstream software