Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Shyam Prasad N <nspmangalore@gmail.com>,
	CIFS <linux-cifs@vger.kernel.org>,
	Enzo Matsumiya <ematsumiya@suse.de>
Subject: Re: Deadlock in Ubuntu 5.4 kernel
Date: Thu, 29 Dec 2022 09:16:54 -0300	[thread overview]
Message-ID: <87a6364d6x.fsf@cjr.nz> (raw)
In-Reply-To: <CANT5p=qEwppcgZvbdLaABb6M-pRxyDQ05oHOb523n34tYyDqcw@mail.gmail.com>

Shyam Prasad N <nspmangalore@gmail.com> writes:

> A customer reported this deadlock in a Kubernetes setup running on Ubuntu-18.04.
> This must be a 5.4 kernel, running this code:
> https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/bionic
>
> Based on the stack, it appears to be a hang in DFS reconnect codepath,
> trying to access the DFS cache lock in dfs_cache_update_vol.
>
> Can you tell if this is a known issue that has been fixed since?

Looks like this has been fixed by

        06d57378bcc9 ("cifs: Fix potential deadlock when updating vol in cifs_reconnect()")

> And if Ubuntu should backport any fix to 5.4?

I would say so.  It would probably also require others dfs related
patches to be backported in addition to the above.

> I could not find the function in the mainline codebase.

Yes, it has changed alot.

  reply	other threads:[~2022-12-29 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29  3:26 Deadlock in Ubuntu 5.4 kernel Shyam Prasad N
2022-12-29 12:16 ` Paulo Alcantara [this message]
2022-12-30  3:33   ` Shyam Prasad N

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=87a6364d6x.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=ematsumiya@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.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