On Sat, Jul 15, 2017 at 10:53:27AM +0200, Michal Kubecek wrote:
>On Sat, Jul 15, 2017 at 01:26:27AM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Michal Kubeček
>>
>> [ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
>>
>> Our customer encountered stuck NFS
On Sat, Jul 15, 2017 at 10:53:27AM +0200, Michal Kubecek wrote:
>On Sat, Jul 15, 2017 at 01:26:27AM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Michal Kubeček
>>
>> [ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
>>
>> Our customer encountered stuck NFS writes for blocks
On Sat, Jul 15, 2017 at 01:26:27AM +, Levin, Alexander (Sasha Levin) wrote:
> From: Michal Kubeček
>
> [ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
>
> Our customer encountered stuck NFS writes for blocks starting at specific
> offsets w.r.t. page boundary
On Sat, Jul 15, 2017 at 01:26:27AM +, Levin, Alexander (Sasha Levin) wrote:
> From: Michal Kubeček
>
> [ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
>
> Our customer encountered stuck NFS writes for blocks starting at specific
> offsets w.r.t. page boundary caused by
From: Michal Kubeček
[ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
Our customer encountered stuck NFS writes for blocks starting at specific
offsets w.r.t. page boundary caused by networking stack sending packets via
UFO enabled device with wrong checksum. The
From: Michal Kubeček
[ Upstream commit a5cb659bbc1c8644efa0c3138a757a1e432a4880 ]
Our customer encountered stuck NFS writes for blocks starting at specific
offsets w.r.t. page boundary caused by networking stack sending packets via
UFO enabled device with wrong checksum. The problem can be
6 matches
Mail list logo