From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Tyler Hall <tylerwhall@gmail.com>,
Andre Naujoks <nautsch2@gmail.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] slip: Fix deadlock in write_wakeup
Date: Mon, 23 Jun 2014 08:31:59 +0200 [thread overview]
Message-ID: <3115845.XamgKCD80B@ws-stein> (raw)
In-Reply-To: <539F2F78.40502@hartkopp.net>
On Monday 16 June 2014 19:55:04, Oliver Hartkopp wrote:
> Hello Tyler,
>
> On 16.06.2014 04:23, Tyler Hall wrote:
> > Use schedule_work() to avoid potentially taking the spinlock in
> > interrupt context.
> >
> (..)
>
> >
> > To deal with these issues, don't grab the lock in the wakeup function by
> > deferring the writeout to a workqueue. Also hold the lock during close
> > when de-assigning the tty pointer to safely disarm the worker and
> > timers.
> >
> > This bug is easily reproducible on the first transmit when slip is
> > used with the standard 8250 serial driver.
> >
>
> looks reasonable. Thanks for your patch!
> Indeed I can't remember ever using the slcan driver with a real serial
> controller hardware with irq line but only via serial-to-USB adapters :-)
> Due to the recent fixes from Andre and Alexander these two drivers got in
> motion again ...
>
> @Andre/Alexander: Can you please check if slcan still works in your setup. I
> don't have that hardware with me. I only was able to compile it successfully.
Sorry, I don't have access to the serial hardware currently.
Best regards
Alexander
next prev parent reply other threads:[~2014-06-23 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 2:23 [PATCH 1/2] slip: Fix deadlock in write_wakeup Tyler Hall
2014-06-16 2:23 ` [PATCH 2/2] slcan: Port write_wakeup deadlock fix from slip Tyler Hall
2014-06-17 4:30 ` David Miller
2014-06-17 8:06 ` Andre Naujoks
2014-06-16 17:55 ` [PATCH 1/2] slip: Fix deadlock in write_wakeup Oliver Hartkopp
2014-06-23 6:31 ` Alexander Stein [this message]
2014-06-17 4:29 ` David Miller
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=3115845.XamgKCD80B@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nautsch2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=tylerwhall@gmail.com \
/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