On (10/13/16 22:42), Sergey Senozhatsky wrote:
> On (10/13/16 08:02), Johannes Berg wrote:
> > On Wed, 2016-10-12 at 22:39 -0700, Andy Lutomirski wrote:
> > > In a pinch, I have these patches sitting around:
> > >
> > > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commit/?h=x86/vmap_stack&id=0a39cfa6fbb5d5635c85253cc7d6b44b54822afd
> > > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commit/?h=x86/vmap_stack&id=bf8cfa200b5a01383ea39fc8ce2f32909767baa8
> > That truly sounds like something we'd rather avoid in the TX/RX paths
> > though, which should perform well.
> didn't fix.
> so I finally had some time to do a better bug-reporter job.
> I added a bunch of printk-s and several virt_addr_valid()-s
> to ieee80211_aes_ccm_encrypt().
> and right befoe the Oops I see the following report from
> FAIL: 00004100002cba02 > ffffc900802cba02 || 1 -> (00004100002cba02 >> 39)
> == 130
that `(00004100002cba02 >> 39) == 130' part is
(addr >> boot_cpu_data.x86_phys_bits)