linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Jörg Otte" <jrg.otte@gmail.com>,
	"Johannes Stezenbach" <js@linuxtv.org>,
	"Patrick Boettcher" <patrick.boettcher@posteo.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Michael Krufky" <mkrufky@linuxtv.org>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: Problem with VMAP_STACK=y
Date: Fri, 7 Oct 2016 08:11:36 -0300	[thread overview]
Message-ID: <20161007081136.1eb8fae9@vento.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1610070952010.31629@cbobk.fhfr.pm>

Em Fri, 7 Oct 2016 09:52:56 +0200 (CEST)
Jiri Kosina <jikos@kernel.org> escreveu:

> On Thu, 6 Oct 2016, Mauro Carvalho Chehab wrote:
> 
> > I can't see any other obvious error on the conversion. You could try to 
> > enable debug options at DVB core/dvb-usb and/or add some printk's to the 
> > driver and see what's happening.
> 
> Mauro, also please don't forget that there are many more places in 
> drivers/media that still perform DMA on stack, and so have to be fixed for 
> 4.9 (as VMAP_STACK makes that to be immediately visible problem even on 
> x86_64, which it wasn't the case before).

Yes, I'm aware of that. I'm doing the conversion of drivers under dvb-usb,
at:
	https://git.linuxtv.org/mchehab/experimental.git/log/?h=media_dmastack_fixes

I'll be sending the patches to the ML after ready.

I'll then take a look on other USB drivers that use the stack. I guess
the non-USB media drivers are safe from this issue.

Thanks,
Mauro

  reply	other threads:[~2016-10-07 11:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADDKRnB1=-zj8apQ3vBfbxVZ8Dc4DJbD1MHynC9azNpfaZeF6Q@mail.gmail.com>
2016-10-04 13:26 ` Problem with VMAP_STACK=y Jiri Kosina
2016-10-04 16:11   ` Jörg Otte
2016-10-05  7:26     ` Jiri Kosina
2016-10-05  7:34       ` Patrick Boettcher
2016-10-05  7:50         ` Jiri Kosina
2016-10-05  9:04           ` Mauro Carvalho Chehab
2016-10-05 11:21             ` Mauro Carvalho Chehab
2016-10-05 15:21             ` Jörg Otte
2016-10-05 15:53               ` Andy Lutomirski
2016-10-05 16:45                 ` Jörg Otte
2016-10-05 16:55                   ` Andy Lutomirski
2016-10-05 18:29             ` Johannes Stezenbach
2016-10-05 18:55               ` Mauro Carvalho Chehab
2016-10-06  8:30                 ` Jörg Otte
2016-10-06 17:17                   ` Mauro Carvalho Chehab
2016-10-07  7:52                     ` Jiri Kosina
2016-10-07 11:11                       ` Mauro Carvalho Chehab [this message]
2016-10-05  7:40   ` dvb-usb stack-memory used for URB-buffers (was: Re: Problem with VMAP_STACK=y) Patrick Boettcher

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=20161007081136.1eb8fae9@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=jikos@kernel.org \
    --cc=jrg.otte@gmail.com \
    --cc=js@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mkrufky@linuxtv.org \
    --cc=patrick.boettcher@posteo.de \
    /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;
as well as URLs for NNTP newsgroup(s).