From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+4bbc13a207327f82b3b0@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ceph?] [fs?] INFO: task hung in ceph_mdsc_pre_umount
Date: Wed, 7 Feb 2024 18:58:01 +0800 [thread overview]
Message-ID: <20240207105801.878-1-hdanton@sina.com> (raw)
In-Reply-To: <0000000000001524350610a52994@google.com>
On Mon, 05 Feb 2024 08:43:25 -0800
> HEAD commit: 076d56d74f17 Add linux-next specific files for 20240202
> git tree: linux-next
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1255e7c4180000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 076d56d74f17
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -1999,6 +1999,8 @@ static int try_to_grab_pending(struct wo
*/
pwq = get_work_pwq(work);
if (pwq && pwq->pool == pool) {
+ unsigned long work_data;
+
debug_work_deactivate(work);
/*
@@ -2016,11 +2018,12 @@ static int try_to_grab_pending(struct wo
list_del_init(&work->entry);
+ work_data = *work_data_bits(work);
/* work->data points to pwq iff queued, point to pool */
set_work_pool_and_keep_pending(work, pool->id);
/* must be the last step, see the function comment */
- pwq_dec_nr_in_flight(pwq, *work_data_bits(work));
+ pwq_dec_nr_in_flight(pwq, work_data);
raw_spin_unlock(&pool->lock);
rcu_read_unlock();
--
next prev parent reply other threads:[~2024-02-07 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 16:43 [syzbot] [ceph?] [fs?] INFO: task hung in ceph_mdsc_pre_umount syzbot
2024-02-06 4:52 ` Hillf Danton
2024-02-06 15:37 ` syzbot
2024-02-07 10:58 ` Hillf Danton [this message]
2024-02-07 11:55 ` 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=20240207105801.878-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+4bbc13a207327f82b3b0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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