linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trevor Hemsley <trevor.hemsley@ntlworld.com>
To: linux-nfs@vger.kernel.org
Subject: Crash in nfsd on kernel > 5.19
Date: Wed, 15 Mar 2023 22:01:19 +0000	[thread overview]
Message-ID: <6d3d381d-84b4-98c7-e6b2-a3b1ad25409b@ntlworld.com> (raw)


Hi

I am not subscribed to this list so please cc me on any replies.

I have a problem using a media player called Kodi when it plays a media 
file that is hosted on an NFS share. Reverting to 
kernel-5.19.16-200.fc36.x86_64 fixes the problem so I suspect this is a 
change made between 5.19 and 6.0.

I'm running libreelec 10.$latest as the client, which is distro 
specifically to allow kodi to run, and the problem is easily 
reproducible from there. All it takes is to play any movie/tv episode 
from an NFS share on a Fedora 36 host and attempt to fast forward the 
motion. Within a second or two, it crashes nfsd on the host. This 
started happening when Fedora updated from kernel 5.19.x to 6.0.x. My 
first crash was on kernel 6.0.9 and it has happened with each 6.0.x 
minor update and with 6.1.x since.

I raised a bugzilla entry 
https://bugzilla.redhat.com/show_bug.cgi?id=2148276 to report this and 
it has seen no traction. There are a few crashes detailed in the ticket. 
Several others have "me too'ed" that bugzilla and the latest example is 
from an untainted kernel 6.1.15-200.fc37.x86_64. I figure it's time to 
try reporting it here instead.

Am happy to test any patches if I can make them apply to the current 
Fedora 6.1.18 (latest) source

Trevor

             reply	other threads:[~2023-03-15 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 22:01 Trevor Hemsley [this message]
2023-03-15 23:51 ` Crash in nfsd on kernel > 5.19 Chuck Lever III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6d3d381d-84b4-98c7-e6b2-a3b1ad25409b@ntlworld.com \
    --to=trevor.hemsley@ntlworld.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).