Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #82611 > unrolled thread

Bug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2024-05-28 21:30 +0200
Last post2024-05-28 21:30 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel Salvatore Bonaccorso <carnil@debian.org> - 2024-05-28 21:30 +0200
    Processed: Re: Bug#1072097: nfs-common: NFS mounted share via DNS  name crashed OS kernel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-05-28 21:30 +0200

#82611 — Bug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-05-28 21:30 +0200
SubjectBug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel
Message-ID<IJaGd-gtjn-3@gated-at.bofh.it>
Control: reassign -1 src:linux 6.1.90-1
Control: tags -1 + moreinfo

Hi,

On Tue, May 28, 2024 at 02:42:43PM +0300, Дмитрий Сергеевич wrote:
> 
> Package: nfs-common
> Version: 1:2.6.2-4
> Severity: normal
>  
> Dear Maintainer,
>  
> *** Reporter, please consider answering these questions, where appropriate ***
>  
>    * What led up to the situation?
> nfs call
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    * What was the outcome of this action?
> мая 28 03:13:18 mail-m kernel: INFO: task kworker/u8:10:182389 blocked for more than 120 seconds.
> мая 28 03:13:18 mail-m kernel:       Tainted: G           OE  X   6.1.0-21-amd64 #1 Debian 6.1.90-1
> мая 28 03:13:18 mail-m kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> мая 28 03:13:18 mail-m kernel: task:kworker/u8:10   state:D stack:0     pid:182389 ppid:2      flags:0x00004000
> мая 28 03:13:18 mail-m kernel: Workqueue: rpciod rpc_async_schedule [sunrpc]
> мая 28 03:13:18 mail-m kernel: Call Trace:
> мая 28 03:13:18 mail-m kernel:  <TASK>
> мая 28 03:13:18 mail-m kernel:  __schedule+0x34d/0x9e0
> мая 28 03:13:18 mail-m kernel:  schedule+0x5a/0xd0
> мая 28 03:13:18 mail-m kernel:  schedule_timeout+0x118/0x150
> мая 28 03:13:18 mail-m kernel:  wait_for_completion_state+0x14b/0x220
> мая 28 03:13:18 mail-m kernel:  call_usermodehelper_exec+0x16a/0x1a0
> мая 28 03:13:18 mail-m kernel:  call_sbin_request_key+0x359/0x500
> мая 28 03:13:18 mail-m kernel:  request_key_and_link+0x6ab/0x7d0
> мая 28 03:13:18 mail-m kernel:  ? keyring_alloc+0x70/0x70
> мая 28 03:13:18 mail-m kernel:  ? key_default_cmp+0x20/0x20
> мая 28 03:13:18 mail-m kernel:  request_key_tag+0x43/0xa0
> мая 28 03:13:18 mail-m kernel:  nfs_idmap_get_key+0x1a2/0x210 [nfsv4]
> мая 28 03:13:18 mail-m kernel:  nfs_map_name_to_uid+0x140/0x180 [nfsv4]
> мая 28 03:13:18 mail-m kernel:  decode_getfattr_attrs+0xd69/0x1120 [nfsv4]
> мая 28 03:13:18 mail-m kernel:  decode_getfattr_generic.constprop.0+0x129/0x210 [nfsv4]
> мая 28 03:13:18 mail-m kernel:  nfs4_xdr_dec_close.part.0+0x7d/0x120 [nfsv4]
> мая 28 03:13:18 mail-m kernel:  call_decode+0x203/0x220 [sunrpc]
> мая 28 03:13:18 mail-m kernel:  ? rpc_decode_header+0x570/0x570 [sunrpc]
> мая 28 03:13:18 mail-m kernel:  __rpc_execute+0xc0/0x4a0 [sunrpc]
> мая 28 03:13:18 mail-m kernel:  rpc_async_schedule+0x29/0x40 [sunrpc]
> мая 28 03:13:18 mail-m kernel:  process_one_work+0x1c4/0x380
> мая 28 03:13:18 mail-m kernel:  worker_thread+0x4d/0x380
> мая 28 03:13:18 mail-m kernel:  ? rescuer_thread+0x3a0/0x3a0
> мая 28 03:13:18 mail-m kernel:  kthread+0xd7/0x100
> мая 28 03:13:18 mail-m kernel:  ? kthread_complete_and_exit+0x20/0x20
> мая 28 03:13:18 mail-m kernel:  ret_from_fork+0x1f/0x30
> мая 28 03:13:18 mail-m kernel:  </TASK>
>    * What outcome did you expect instead?

kernel above is tained, does this happens as well when not loading the
out-of-tree modules? 

Is this reproducible and is it a regression from which previous
kernel? 

Regards,
Salvatore

[toc] | [next] | [standalone]


#82612 — Processed: Re: Bug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-05-28 21:30 +0200
SubjectProcessed: Re: Bug#1072097: nfs-common: NFS mounted share via DNS name crashed OS kernel
Message-ID<IJaGd-gtjn-9@gated-at.bofh.it>
In reply to#82611
Processing control commands:

> reassign -1 src:linux 6.1.90-1
Bug #1072097 [nfs-common] nfs-common: NFS mounted share via DNS name crashed OS kernel
Bug reassigned from package 'nfs-common' to 'src:linux'.
No longer marked as found in versions nfs-utils/1:2.6.2-4.
Ignoring request to alter fixed versions of bug #1072097 to the same values previously set
Bug #1072097 [src:linux] nfs-common: NFS mounted share via DNS name crashed OS kernel
Marked as found in versions linux/6.1.90-1.
> tags -1 + moreinfo
Bug #1072097 [src:linux] nfs-common: NFS mounted share via DNS name crashed OS kernel
Added tag(s) moreinfo.

-- 
1072097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072097
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web