From: Cong Wang <xiyou.wangcong@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Praveen Murali <pmurali@logicube.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] libsas: flush pending destruct work in sas_unregister_domain_devices()
Date: Tue, 28 Nov 2017 09:00:54 -0800 [thread overview]
Message-ID: <CAM_iQpV-uy9VXfVx9s5AX8TN5-0G=7Ny0uvmCCn7V7ys_gBbWw@mail.gmail.com> (raw)
In-Reply-To: <20171128082049.5smff3hvrkwrf77o@linux-x5ow.site>
On Tue, Nov 28, 2017 at 12:20 AM, Johannes Thumshirn <jthumshirn@suse.de> wrote:
> On Mon, Nov 27, 2017 at 04:24:45PM -0800, Cong Wang wrote:
>> We saw dozens of the following kernel waring:
>>
>> WARNING: CPU: 0 PID: 705 at fs/sysfs/group.c:224 sysfs_remove_group+0x54/0x88()
>> sysfs group ffffffff81ab7670 not found for kobject '6:0:3:0'
>> Modules linked in: cpufreq_ondemand x86_pkg_temp_thermal coretemp kvm_intel kvm microcode raid0 iTCO_wdt iTCO_vendor_support sb_edac edac_core lpc_ich mfd_core ioatdma i2c_i801 shpchp wmi hed acpi_cpufreq lp parport tcp_diag inet_diag ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel igb ptp pps_core i2c_algo_bit i2c_core crc32c_intel isci libsas scsi_transport_sas dca ipv6
>> CPU: 0 PID: 705 Comm: kworker/u240:0 Not tainted 4.1.35.el7.x86_64 #1
>
> This should by now be fixed with commit fbce4d97fd43 ("scsi: fixup kernel
> warning during rmmod()" which went into v4.14-rc6.
I don't see the full backtrace in commit fbce4d97fd43, but it is probably
not rmmod path in our case.
prev parent reply other threads:[~2017-11-28 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 0:24 [PATCH] libsas: flush pending destruct work in sas_unregister_domain_devices() Cong Wang
2017-11-28 8:20 ` Johannes Thumshirn
2017-11-28 11:18 ` John Garry
2017-11-28 17:04 ` Cong Wang
2017-12-07 13:37 ` John Garry
2017-12-07 22:57 ` Cong Wang
2017-12-08 0:40 ` Cong Wang
2017-12-08 1:04 ` Cong Wang
2017-12-08 7:54 ` Jason Yan
2017-12-09 19:51 ` Cong Wang
2017-11-28 17:00 ` Cong Wang [this message]
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='CAM_iQpV-uy9VXfVx9s5AX8TN5-0G=7Ny0uvmCCn7V7ys_gBbWw@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pmurali@logicube.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;
as well as URLs for NNTP newsgroup(s).