Re: BUG: using smp_processor_id() in preemptible code in tipc_crypto_xmit

2020-10-09 Thread syzbot
syzbot suspects this issue was fixed by commit: commit bb8872a1e6bc911869a729240781076ed950764b Author: Tuong Lien Date: Sat Aug 29 19:37:55 2020 + tipc: fix using smp_processor_id() in preemptible bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100f5bb850 start commi

Re: BUG: using smp_processor_id() in preemptible code in tipc_crypto_xmit

2020-07-22 Thread syzbot
syzbot has bisected this issue to: commit e1f32190cf7ddd55778b460e7d44af3f76529698 Author: Tuong Lien Date: Fri Nov 8 05:05:12 2019 + tipc: add support for AEAD key setting via netlink bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11b738a090 start commit: 11ba4688

Re: BUG: using smp_processor_id() in preemptible code in tipc_crypto_xmit

2020-07-13 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:4437dd6e Merge tag 'io_uring-5.8-2020-07-12' of git://git... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13a4773f10 kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203

Re: BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc

2020-06-05 Thread Eric Biggers
On Fri, Jun 05, 2020 at 04:29:22AM -0700, Matthew Wilcox wrote: > On Thu, Jun 04, 2020 at 08:55:55PM -0700, Eric Biggers wrote: > > Possibly a bug in lib/radix-tree.c? this_cpu_ptr() in > > radix_tree_node_alloc() > > can be reached without a prior preempt_disable(). Or is the caller of > > idr_

Re: BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc

2020-06-05 Thread Matthew Wilcox
On Thu, Jun 04, 2020 at 08:55:55PM -0700, Eric Biggers wrote: > Possibly a bug in lib/radix-tree.c? this_cpu_ptr() in radix_tree_node_alloc() > can be reached without a prior preempt_disable(). Or is the caller of > idr_alloc() doing something wrong? Yes, the idr_alloc() call is plainly wrong:

Re: BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc

2020-06-04 Thread syzbot
syzbot has bisected this bug to: commit e42671084361302141a09284fde9bbc14fdd16bf Author: Manivannan Sadhasivam Date: Thu May 7 12:53:06 2020 + net: qrtr: Do not depend on ARCH_QCOM bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e2221210 start commit: acf25aa6 Mer

Re: BUG: using smp_processor_id() in preemptible code in debug_smp_processor_id

2020-06-04 Thread Eric Biggers
On Thu, Jun 04, 2020 at 07:42:18AM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:065fcfd4 selftests: net: ip_defrag: ignore EPERM > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=15c3e51610 > kernel config: ht

Re: BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc

2020-06-04 Thread Eric Biggers
[+Cc Matthew Wilcox] Possibly a bug in lib/radix-tree.c? this_cpu_ptr() in radix_tree_node_alloc() can be reached without a prior preempt_disable(). Or is the caller of idr_alloc() doing something wrong? On Thu, Jun 04, 2020 at 07:02:18PM -0700, syzbot wrote: > Hello, > > syzbot found the foll

Re: BUG: using smp_processor_id() in preemptible

2018-01-11 Thread Eric Dumazet
On Thu, 2018-01-11 at 10:31 -0200, Ricardo Nabinger Sanchez wrote: > Greetings, > > I'm getting occasional video lock-ups, and while checking logs I found > these: > > === > [ 297.445296] BUG: using smp_processor_id() in preemptible [] code: > claws-mail/1635 > [ 297.445319] caller is

Re: BUG: using smp_processor_id() in preemptible [00000000]

2017-10-08 Thread Jakub Kicinski
On Sun, 8 Oct 2017 20:47:10 -0700, Eric Dumazet wrote: > This was discussed/reported earlier today by Ido. > > https://patchwork.ozlabs.org/patch/823011/ > > We will submit an official fix shortly. Ah, sorry, I missed that!

Re: BUG: using smp_processor_id() in preemptible [00000000]

2017-10-08 Thread Eric Dumazet
On Sun, Oct 8, 2017 at 8:43 PM, Jakub Kicinski wrote: > Hi! > > This appeared in net-next over the weekend - looks likely related to > this set... > > [ 164.456668] BUG: using smp_processor_id() in preemptible [] code: > sshd/1255 > [ 164.472259] caller is ip6_pol_route+0xe88/0x4a80 > [

Re: BUG: using smp_processor_id() in preemptible [00000001] code: ipcomp/2801

2005-08-17 Thread Herbert Xu
Ken-ichirou MATSUZAWA <[EMAIL PROTECTED]> wrote: > > It seems that because ipcomp_alloc_tfms() calls smp_processor_id(), > but a comment says not need locking. Is this right? Yes the comment is right. I'll fix it up. Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV