Linux NFS development
 help / color / mirror / Atom feed
From: Harald Dunkel <harri@afaics.de>
To: NeilBrown <neilb@suse.de>
Cc: syzbot <syzbot+b568ba42c85a332a88ee@syzkaller.appspotmail.com>,
	Jeff Layton <jlayton@kernel.org>,
	Dai.Ngo@oracle.com, chuck.lever@oracle.com, kolga@netapp.com,
	linux-nfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tom@talpey.com
Subject: Re: [syzbot] [nfs?] INFO: task hung in nfsd_umount
Date: Fri, 4 Oct 2024 14:21:32 +0200	[thread overview]
Message-ID: <0c765314-3e78-4c2f-8280-9ae337ff0bf6@afaics.de> (raw)
In-Reply-To: <d8e1e97f-997f-4dca-8b3f-0628a3783957@afaics.de>

On 2024-10-02 16:06:14, Harald Dunkel wrote:
> PS: dmesg -T attached as well.

PPS: I learned another thing today: I have to disable kernel
logging in the containers. Sorry about that. The nfsd died
again today, but I doubt that the new log files are very useful.
Please mail if you are interested.

The NFS server has been rebooted (without imklog syslog module
in the containers) and the watchdog has been started again.


Regards

Harri

  reply	other threads:[~2024-10-04 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-07  4:37 [syzbot] [nfs?] INFO: task hung in nfsd_umount syzbot
2024-07-07 10:49 ` Jeff Layton
2024-07-08  0:07   ` NeilBrown
2024-09-21  7:58     ` Harald Dunkel
2024-09-28  7:41       ` Harald Dunkel
2024-09-28 22:23         ` NeilBrown
2024-09-29  8:23           ` Harald Dunkel
2024-09-29  9:59             ` NeilBrown
2024-10-01 10:21               ` Harald Dunkel
2024-10-02 13:55                 ` Harald Dunkel
2024-10-02 14:06                   ` Harald Dunkel
2024-10-04 12:21                     ` Harald Dunkel [this message]
2024-10-04 23:37                     ` NeilBrown
2024-10-07 10:51                       ` Harald Dunkel
2024-10-07 18:54                         ` Harald Dunkel
2026-08-16 10:14 ` syzbot

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=0c765314-3e78-4c2f-8280-9ae337ff0bf6@afaics.de \
    --to=harri@afaics.de \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=syzbot+b568ba42c85a332a88ee@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tom@talpey.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