linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bhatnagar, Rishabh" <risbhat@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <sfrench@samba.org>, <stable@vger.kernel.org>,
	<linux-cifs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5.4 0/2] Backport few dfs related fixes to cifs
Date: Wed, 7 Jun 2023 13:20:23 -0700	[thread overview]
Message-ID: <de36d593-5f1e-bb9b-6b70-8be0b783c5f4@amazon.com> (raw)
In-Reply-To: <2023060750-unpledged-effective-bd95@gregkh>


On 6/7/23 12:07 PM, Greg KH wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> 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

These patches are applicable for 5.4. Will send another version with 
that fixed.
Apologies for the mess.


  reply	other threads:[~2023-06-07 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 18:53 [PATCH 5.4 0/2] Backport few dfs related fixes to cifs Rishabh Bhatnagar
2023-06-07 18:53 ` [PATCH 5.10 1/2] cifs: get rid of unused parameter in reconn_setup_dfs_targets() Rishabh Bhatnagar
2023-06-07 18:53 ` [PATCH 5.10 2/2] cifs: handle empty list of targets in cifs_reconnect() Rishabh Bhatnagar
2023-06-07 19:07 ` [PATCH 5.4 0/2] Backport few dfs related fixes to cifs Greg KH
2023-06-07 20:20   ` Bhatnagar, Rishabh [this message]
2023-06-07 20:36     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-06-01 20:58 Rishabh Bhatnagar

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=de36d593-5f1e-bb9b-6b70-8be0b783c5f4@amazon.com \
    --to=risbhat@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=stable@vger.kernel.org \
    /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 NNTP newsgroup(s).