linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Soeren Moch <smoch@web.de>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: mchehab@redhat.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] media: dmxdev: remove dvb_ringbuffer_flush() on writer side
Date: Sun, 12 May 2013 10:16:43 +0200	[thread overview]
Message-ID: <518F4FEB.70908@web.de> (raw)
In-Reply-To: <20130510193955.GI1075@valkosipuli.retiisi.org.uk>

On 10.05.2013 21:39, Sakari Ailus wrote:
> Hi Soeren,
>
> Thanks for the patch!
>
> On Sun, Apr 14, 2013 at 11:03:42AM +0200, Soeren Moch wrote:
>> In dvb_ringbuffer lock-less synchronizationof reader and writer threads is done
>> with separateread and write pointers. Since dvb_ringbuffer_flush() modifies the
>> read pointer, this function must not be called from the writer thread.
>>
>> This patch removes the dvb_ringbuffer_flush() calls in the dmxdev ringbuffer
>> write functions, this fixes Oopses "Unable to handle kernel paging request"
>> I could observe for the call chain dvb_demux_read ->dvb_dmxdev_buffer_read ->
>> dvb_ringbuffer_read_user -> __copy_to_user (the reader side of the ringbuffer).
>>
>> The flush calls at the write side are not necessary anyway since ringbuffer_flush
>> is also called in dvb_dmxdev_buffer_read() when an error condition is set in the
>> ringbuffer.
>>
>> This patch should also be applied to stable kernels.
>>
>> Signed-off-by: Soeren Moch <smoch@web.de>
>> CC: <stable@vger.kernel.org>
> While the change the patch does itself appears sound to me, I need to ask
> you to resend the patch using git send-email (it won't apply as-is). I can
> do that this time, too; let me know what works for you.
Please convert this patch to git format, thank you!
>
> Reviewed-by: Sakari Ailus <sakari.ailus@iki.fi>
And thanks for your rewiew, too.

   Soeren
>
>> --- a/drivers/media/dvb-core/dmxdev.c	2013-04-05 21:21:15.000000000 +0200
>> +++ b/drivers/media/dvb-core/dmxdev.c	2013-04-14 09:01:58.000000000 +0200
>> @@ -377,10 +377,8 @@ static int dvb_dmxdev_section_callback(c
>>   		ret = dvb_dmxdev_buffer_write(&dmxdevfilter->buffer, buffer2,
>>   					      buffer2_len);
>>   	}
>> -	if (ret < 0) {
>> -		dvb_ringbuffer_flush(&dmxdevfilter->buffer);
>> +	if (ret < 0)
>>   		dmxdevfilter->buffer.error = ret;
>> -	}
>>   	if (dmxdevfilter->params.sec.flags & DMX_ONESHOT)
>>   		dmxdevfilter->state = DMXDEV_STATE_DONE;
>>   	spin_unlock(&dmxdevfilter->dev->lock);
>> @@ -416,10 +414,8 @@ static int dvb_dmxdev_ts_callback(const
>>   	ret = dvb_dmxdev_buffer_write(buffer, buffer1, buffer1_len);
>>   	if (ret == buffer1_len)
>>   		ret = dvb_dmxdev_buffer_write(buffer, buffer2, buffer2_len);
>> -	if (ret < 0) {
>> -		dvb_ringbuffer_flush(buffer);
>> +	if (ret < 0)
>>   		buffer->error = ret;
>> -	}
>>   	spin_unlock(&dmxdevfilter->dev->lock);
>>   	wake_up(&buffer->queue);
>>   	return 0;
>>


      reply	other threads:[~2013-05-12  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  1:25 dmxdev: Unable to handle kernel paging request Soeren Moch
2013-04-14  9:03 ` [PATCH] media: dmxdev: remove dvb_ringbuffer_flush() on writer side Soeren Moch
2013-05-10 19:39   ` Sakari Ailus
2013-05-12  8:16     ` Soeren Moch [this message]

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=518F4FEB.70908@web.de \
    --to=smoch@web.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=sakari.ailus@iki.fi \
    /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).