Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1231936
| From | Sedat Dilek <sedat.dilek@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 |
| Date | 2015-09-24 10:20 +0200 |
| Message-ID | <qc9V0-5OU-5@gated-at.bofh.it> (permalink) |
| References | <q6KNB-i6-43@gated-at.bofh.it> <q6Yxb-3aF-1@gated-at.bofh.it> <qc8vU-3GJ-19@gated-at.bofh.it> <qc9BE-5cV-9@gated-at.bofh.it> <qc9Lj-5Dv-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Sep 24, 2015 at 10:03 AM, Jiri Kosina <jikos@kernel.org> wrote: > On Thu, 24 Sep 2015, Jiri Kosina wrote: > >> > >> [ 24.705767] [<ffffffff8149287d>] dump_stack+0x7d/0xa0 >> > >> [ 24.705774] [<ffffffff810cbf7a>] ___might_sleep+0x28a/0x2a0 >> > >> [ 24.705779] [<ffffffff810cbc7f>] __might_sleep+0x4f/0xc0 >> > >> [ 24.705784] [<ffffffff810ae8ff>] start_flush_work+0x2f/0x290 >> > >> [ 24.705789] [<ffffffff810ae8ac>] flush_work+0x5c/0x80 >> > >> [ 24.705792] [<ffffffff810ae86a>] ? flush_work+0x1a/0x80 >> > >> [ 24.705799] [<ffffffff810eddcd>] ? trace_hardirqs_off+0xd/0x10 >> > >> [ 24.705804] [<ffffffff810ad938>] ? try_to_grab_pending+0x48/0x360 >> > >> [ 24.705810] [<ffffffff81917e13>] ? _raw_spin_lock_irqsave+0x73/0x80 >> > >> [ 24.705814] [<ffffffff810aecf9>] __cancel_work_timer+0x179/0x260 >> >> This one is even more strange. It says that flush_work() is being called >> from __cancel_work_timer() with IRQs disabled, but flags are explicitly >> restored just one statement before that, and usbhid_close() explicitly >> calls cancel_work_sync() after unconditionally enabling interrupts. >> >> So I am not able to make any sense of either of the traces really. >> >> Are you seeing this with the same .config with GCC-compiled kernel as >> well? > > Actually could you please provide disassembly of your > __cancel_work_timer()? > Disassembly of which file - corresponding workqueue or hid file? > One explanation would be LLVM not considering local_irq_restore() a > compiler memory barrier, but I am pretty sure it'll expose much more > breakage if that'd be the case. > Can you point me where I can find more informations about "compiler memory barrier" or explain in a few words if possible? Thanks. I can provide the files this evening... /me in front of a Windows machine. - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-24 10:00 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-24 10:10 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-24 10:20 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-24 10:30 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-25 08:50 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-25 14:10 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-25 14:20 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-25 14:20 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-25 14:50 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-25 14:50 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Jiri Kosina <jikos@kernel.org> - 2015-09-25 15:20 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-25 15:20 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-27 10:40 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-25 14:40 +0200
Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680 Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-24 10:10 +0200
csiph-web