All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: John <therealgraysky@proton.me>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: kernel panic when starting nfsd on OpenWrt with kernel 6.12.19
Date: Sat, 22 Mar 2025 13:33:02 -0400	[thread overview]
Message-ID: <9e7a546c-a192-4e8b-bbd6-a3aaedb5e013@oracle.com> (raw)
In-Reply-To: <yW5ewBN3-dAMHSq9KmbFRPRt_fK0FTmuqclUbu4K1kZPcfB6DmXRPOVC_OAwh1waQz2Of0qUDqxQ3YL-NBULF9H6-HMdVjixFAad20f5sUY=@proton.me>

On 3/22/25 1:20 PM, John wrote:
> 
> 
> On Saturday, March 22nd, 2025 at 10:49 AM, Chuck Lever <chuck.lever@oracle.com> wrote:
>>
>> I recommend bisecting between 6.6 and 6.12.19 to locate the culprit.
>>
>> When you have that information, open a bug on bugzilla.kernel.org under
>> Filesystems/NFSD and attach your information there.
> 
> Wish I could, but the way OpenWrt is designed, moving from one kernel branch to another is major undertaking often requiring months of tweaks 1,000s of patches, Makefiles, config files, etc.
> 
> I have been reading up on NFSv4 and am wondering if there is a way to simply disable the callback function. Could that work-around this crash?
> 
> Unfortunately, OpenWrt's nfs-kernel-server package does not ship nor use something like /etc/nfs.conf. At the link below you can see their init script to start nfsd. Many thank for any ideas.
> 
> https://github.com/openwrt/packages/blob/master/net/nfs-kernel-server/files/nfsd.init

Open a bug anyway, please. I have a nightly CI for NFSD that has not
crashed on v6.12 LTS, so this is a new and unseen issue.

Thanks for the report!


-- 
Chuck Lever

  reply	other threads:[~2025-03-22 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 10:05 kernel panic when starting nfsd on OpenWrt with kernel 6.12.19 John
2025-03-22 14:49 ` Chuck Lever
2025-03-22 17:20   ` John
2025-03-22 17:33     ` Chuck Lever [this message]
2025-03-22 18:06     ` Chuck Lever
2025-03-22 18:52       ` John

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=9e7a546c-a192-4e8b-bbd6-a3aaedb5e013@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=therealgraysky@proton.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.