[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023060750-unpledged-effective-bd95@gregkh>
Date: Wed, 7 Jun 2023 21:07:09 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Rishabh Bhatnagar <risbhat@...zon.com>
Cc: sfrench@...ba.org, stable@...r.kernel.org,
linux-cifs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5.4 0/2] Backport few dfs related fixes to cifs
On Wed, Jun 07, 2023 at 06:53:11PM +0000, Rishabh Bhatnagar wrote:
> Recently we have been seeing kernel panic in cifs_reconnect function
> while accessing tgt_list. Looks like tgt_list is not initialized
> correctly. There are fixes already present in 5.10 and later trees.
> Backporting them to 5.4
>
> CIFS VFS: \\172.30.1.14 cifs_reconnect: no target servers for DFS
> failover
> BUG: unable to handle page fault for address: fffffffffffffff8
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 260e067 P4D 260e067 PUD 2610067 PMD 0
> Oops: 0000 [#1] SMP PTI
> RIP: 0010:cifs_reconnect+0x51d/0xef0 [cifs]
> RSP: 0018:ffffc90000693da0 EFLAGS: 00010282
> RAX: fffffffffffffff8 RBX: ffff8887fa63b800 RCX: fffffffffffffff8
> Call Trace:
> cifs_handle_standard+0x18d/0x1b0 [cifs]
> cifs_demultiplex_thread+0xa5c/0xc90 [cifs]
> kthread+0x113/0x130
>
> *** BLURB HERE ***
No blurb?
And this says 5.4, yet your patches say 5.10?
Totally confused...
greg k-h
Powered by blists - more mailing lists