All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Network Development <netdev@vger.kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Wireless List <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>
Subject: Re: [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7)
Date: Fri, 14 Oct 2016 10:42:41 +0200	[thread overview]
Message-ID: <1476434561.31114.7.camel@sipsolutions.net> (raw)
In-Reply-To: <CAKv+Gu_v+4D_7EvRkrSrStheuP1L-oPh=o7Ub+NU7-wgLYks4w@mail.gmail.com> (sfid-20161014_104110_693126_BE54E499)

On Fri, 2016-10-14 at 09:41 +0100, Ard Biesheuvel wrote:

> > I assume the stack buffer itself is not the problem here, but aad,
> > which is allocated on the stack one frame up.
> > Do we really need to revert the whole patch to fix that?
> 
> Ah never mind, this is about 'odata'. Apologies, should have read
> first

Right, odata also goes into an sg list and further on.

I think we should wait for Herbert to chime in before we do any further
work though, perhaps he has any better ideas.

johannes

  reply	other threads:[~2016-10-14  8:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 15:03 [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7) Sergey Senozhatsky
2016-10-10 15:30 ` Sergey Senozhatsky
2016-10-12  9:05   ` Johannes Berg
2016-10-12 14:12     ` Sergey Senozhatsky
2016-10-12 14:22       ` Johannes Berg
2016-10-13  5:39         ` Andy Lutomirski
2016-10-13  6:02           ` Johannes Berg
2016-10-13 13:42             ` Sergey Senozhatsky
2016-10-13 13:45               ` Sergey Senozhatsky
2016-10-13 13:45               ` Johannes Berg
2016-10-13 15:00                 ` Sergey Senozhatsky
2016-10-13 15:04                   ` Sergey Senozhatsky
2016-10-13 21:49                 ` Andy Lutomirski
2016-10-14  7:25                   ` Johannes Berg
2016-10-14  8:28                     ` Johannes Berg
2016-10-14  8:39                       ` Ard Biesheuvel
2016-10-14  8:41                         ` Ard Biesheuvel
2016-10-14  8:42                           ` Johannes Berg [this message]
2016-10-14  8:47                             ` Ard Biesheuvel
     [not found]                               ` <CAKv+Gu896xme5sd5i8hs7tA=Xt=qQKCiAx7fQg1ZECn50NttbQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-14  8:55                                 ` Johannes Berg
2016-10-14  8:55                                   ` Johannes Berg
2016-10-14  9:05                                   ` Ard Biesheuvel
2016-10-14  9:10                                     ` Johannes Berg
2016-10-14  9:21                                       ` Ard Biesheuvel
2016-10-14  9:25                                         ` Johannes Berg
2016-10-14  9:35                                           ` Ard Biesheuvel
2016-10-14 10:00                                             ` Johannes Berg
2016-10-14 11:11                                               ` Ard Biesheuvel
2016-10-14  8:53                     ` Johannes Berg
2016-10-14  8:39                   ` Sergey Senozhatsky
2016-10-14  8:45                     ` Johannes Berg

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=1476434561.31114.7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ard.biesheuvel@linaro.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=j@w1.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=netdev@vger.kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.