From: Greg KH <gregkh@linuxfoundation.org>
To: Chenglong Tang <chenglongtang@google.com>
Cc: regressions@lists.linux.dev, pc@manguebit.com,
linkinjeon@kernel.org, dhowells@redhat.com,
linux-cifs@vger.kernel.org, Oleksandr Tymoshenko <ovt@google.com>,
Robert Kolchmeyer <rkolchmeyer@google.com>
Subject: Re: Fwd: kernel panic caused by recent changes in fs/cifs
Date: Wed, 10 Apr 2024 10:26:35 +0200 [thread overview]
Message-ID: <2024041005-marbled-lavish-047d@gregkh> (raw)
In-Reply-To: <CAOdxtTZfo59ZUxTgbWOybqyL3XHKyiudVthTLaU8jYRhiAqXvA@mail.gmail.com>
On Tue, Apr 09, 2024 at 11:45:06PM -0700, Chenglong Tang wrote:
> ---------- Forwarded message ---------
> From: Chenglong Tang <chenglongtang@google.com>
> Date: Tue, Apr 9, 2024 at 11:43 PM
> Subject: kernel panic caused by recent changes in fs/cifs
> To: <samba-technical-owner@lists.samba.org>
>
>
> Hi, developers,
>
> This is Chenglong Tang from the Google Container Optimized OS team. We
> recently received a kernel panic bug from the customers regarding cifs.
>
> This happened since the backport of following changes in cifs(in our kernel
> COS-5.10.208 and COS-5.15.146):
>
> cifs: Fix non-availability of dedup breaking generic/304:
> https://lore.kernel.org/r/3876191.1701555260@warthog.procyon.org.uk/
> smb: client: fix potential NULL deref in parse_dfs_referrals(): Upstream
> commit 92414333eb375ed64f4ae92d34d579e826936480
> ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE: Upstream
> commit 13736654481198e519059d4a2e2e3b20fa9fdb3e
> smb: client: fix NULL deref in asn1_ber_decoder(): Upstream commit
> 90d025c2e953c11974e76637977c473200593a46
> smb: a few more smb changes...
>
> The line that crashed is line 197 in fs/cifs/dfs_cache.c
> ```
> if (unlikely(strcmp(cp->charset, cache_cp->charset))) {
> ```
> I attached the dmesg and backtrace for debugging purposes. Let me know if
> you need more information.
Do you know which commit caused this problem?
And 5.15 and 5.10 are very old kernels, does this still happen in the
latest kernel releases?
thanks,
greg k-h
prev parent reply other threads:[~2024-04-10 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOdxtTaceuB9fvnEcoTVO6t0V_90UbLM3dyLbE_CK7uRe1bn=Q@mail.gmail.com>
2024-04-10 6:45 ` Fwd: kernel panic caused by recent changes in fs/cifs Chenglong Tang
2024-04-10 8:26 ` Greg KH [this message]
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=2024041005-marbled-lavish-047d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenglongtang@google.com \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ovt@google.com \
--cc=pc@manguebit.com \
--cc=regressions@lists.linux.dev \
--cc=rkolchmeyer@google.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).