From: Stefan Agner <stefan@agner.ch>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jslaby@suse.cz, jingchang.lu@freescale.com, shawn.guo@linaro.org,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] serial: fsl_lpuart: delete timer on shutdown
Date: Sat, 10 Jan 2015 09:09:59 +0100 [thread overview]
Message-ID: <a65e439b2fb720d94ae2a7effea96eb0@agner.ch> (raw)
In-Reply-To: <20150110004858.GB4171@kroah.com>
On 2015-01-10 01:48, Greg KH wrote:
> On Sat, Jan 10, 2015 at 01:08:58AM +0100, Stefan Agner wrote:
>> If the serial port gets closed while a RX transfer is in progress,
>> the timer might fire after the serial port shutdown finished. This
>> leads in a NULL pointer dereference:
>>
>> [ 7.508324] Unable to handle kernel NULL pointer dereference at virtual address 00000000
>> [ 7.516590] pgd = 86348000
>> [ 7.519445] [00000000] *pgd=86179831, *pte=00000000, *ppte=00000000
>> [ 7.526145] Internal error: Oops: 17 [#1] ARM
>> [ 7.530611] Modules linked in:
>> [ 7.533876] CPU: 0 PID: 123 Comm: systemd Not tainted 3.19.0-rc3-00004-g5b11ea7 #1778
>> [ 7.541827] Hardware name: Freescale Vybrid VF610 (Device Tree)
>> [ 7.547862] task: 861c3400 ti: 86ac8000 task.ti: 86ac8000
>> [ 7.553392] PC is at lpuart_timer_func+0x24/0xf8
>> [ 7.558127] LR is at lpuart_timer_func+0x20/0xf8
>> [ 7.562857] pc : [<802df99c>] lr : [<802df998>] psr: 600b0113
>> [ 7.562857] sp : 86ac9b90 ip : 86ac9b90 fp : 86ac9bbc
>> [ 7.574467] r10: 80817180 r9 : 80817b98 r8 : 80817998
>> [ 7.579803] r7 : 807acee0 r6 : 86989000 r5 : 00000100 r4 : 86997210
>> [ 7.586444] r3 : 86ac8000 r2 : 86ac9bc0 r1 : 86997210 r0 : 00000000
>> [ 7.593085] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
>> [ 7.600341] Control: 10c5387d Table: 86348059 DAC: 00000015
>> [ 7.606203] Process systemd (pid: 123, stack limit = 0x86ac8230)
>>
>> Setup the timer on UART startup which allows to delete the timer
>> unconditionally on shutdown. This also saves the initialization
>> on each transfer.
>>
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>> ---
>> drivers/tty/serial/fsl_lpuart.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> Do stable kernels care about this as well, or is this just a regression
> from 3.18?
This is an issue since DMA support for lpuart was included in the
kernel, which was in 3.14.
--
Stefan
next prev parent reply other threads:[~2015-01-10 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 0:08 [PATCH v2 0/2] serial: fsl_lpuart: fix DMA issues for 3.19 Stefan Agner
2015-01-10 0:08 ` [PATCH v2 1/2] serial: fsl_lpuart: delete timer on shutdown Stefan Agner
2015-01-10 0:48 ` Greg KH
2015-01-10 8:09 ` Stefan Agner [this message]
2015-01-10 0:08 ` [PATCH v2 2/2] serial: fsl_lpuart: avoid new transfer while DMA is running Stefan Agner
2015-01-10 0:49 ` Greg KH
2015-01-10 8:12 ` Stefan Agner
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=a65e439b2fb720d94ae2a7effea96eb0@agner.ch \
--to=stefan@agner.ch \
--cc=gregkh@linuxfoundation.org \
--cc=jingchang.lu@freescale.com \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shawn.guo@linaro.org \
/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).