From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
falemi@asu.edu, driver-core@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] general protection fault in sysfs_do_create_link_sd
Date: Fri, 28 Aug 2026 07:59:38 +0200 [thread overview]
Message-ID: <2026082813-rephrase-superjet-82bb@gregkh> (raw)
In-Reply-To: <CA+0ovChyLaYfEN19Fomt6qWx6dYtX47Ptyaej3gfMeNGB1xoFg@mail.gmail.com>
On Fri, Aug 28, 2026 at 05:50:00AM +0000, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/188-general-protection-fault-in-sysfs-do-create-link-sd/
>
> Oops: general protection fault, probably for non-canonical address
> 0xdffffc0000000006: 0000 [#1] SMP KASAN NOPTI
> KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]
> RIP: 0010:sysfs_do_create_link_sd+0x4b/0x110 fs/sysfs/symlink.c:35
> Call Trace:
> sysfs_do_create_link_sd+0x4b/0x110 fs/sysfs/symlink.c:35
> nfs_sysfs_link_rpc_client+0x3a3/0x590 fs/nfs/sysfs.c:343
> nfs_init_server fs/nfs/client.c:770 [inline]
> nfs_create_server+0x7e8/0x2110 fs/nfs/client.c:1155
> nfs3_create_server+0x1e/0x180 fs/nfs/nfs3client.c:56
> nfs_try_get_tree+0x1fa/0x11a0 fs/nfs/super.c:981
> vfs_get_tree+0x8f/0x290 fs/super.c:1754
> do_new_mount+0x341/0xd80 fs/namespace.c:3834
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
Please stop sending random callbacks, instead send proper patches, as
this helps no one.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-28 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:50 [BUG] general protection fault in sysfs_do_create_link_sd Farhad Alemi
2026-08-28 5:59 ` Greg Kroah-Hartman [this message]
2026-08-28 6:33 ` Greg Kroah-Hartman
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=2026082813-rephrase-superjet-82bb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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