From: Tejun Heo <tj@kernel.org>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: disable port while unloading ATA controller driver
Date: Tue, 29 Nov 2016 14:00:25 -0500 [thread overview]
Message-ID: <20161129190025.GC22330@htj.duckdns.org> (raw)
In-Reply-To: <09c7866c-ecd4-f48a-5112-6cf3c6786cd9@mleia.com>
Hello, Vladimir.
On Tue, Nov 29, 2016 at 08:54:11PM +0200, Vladimir Zapolskiy wrote:
> tracing on the board shows a race between driver initialization and
> deinitialization, when async_port_probe() is scheduled after driver
> removal, this causes the reported problem.
>
> Since it is a race, it should be possible to fuzz the kernel by
> introducing a delay (e.g. in ata_port_probe()) to get enough time
> to reproduce the problem reliably and to verify a fix.
>
> imx_ahci_probe()
> ahci_platform_init_host()
> ata_host_alloc_pinfo()
> ata_host_alloc()
> ata_port_alloc() ---> sets ATA_PFLAG_INITIALIZING flag
> ata_link_init()
> ....
> ahci_host_activate()
> ata_host_activate()
> ata_host_start()
> ata_eh_freeze_port()
> ata_port_desc()
> ata_host_register() ---> schedules async_port_probe()
> ....
>
> *** at this point the driver probe is completed, thus it can be removed ***
Not really. Is this from the unloading test config? Control doesn't
get passed to userland until async probings are flushed, so this
shouldn't normally be possible.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-11-29 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 23:18 [PATCH] ata: disable port while unloading ATA controller driver Vladimir Zapolskiy
2016-11-27 23:30 ` Vladimir Zapolskiy
2016-11-28 18:34 ` Tejun Heo
2016-11-28 23:51 ` Vladimir Zapolskiy
2016-11-29 18:54 ` Vladimir Zapolskiy
2016-11-29 19:00 ` Tejun Heo [this message]
2016-11-29 20:04 ` Vladimir Zapolskiy
2016-11-29 20:44 ` Tejun Heo
2016-11-29 22:15 ` Vladimir Zapolskiy
2016-11-29 22:29 ` Tejun Heo
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=20161129190025.GC22330@htj.duckdns.org \
--to=tj@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=linux-ide@vger.kernel.org \
--cc=vz@mleia.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;
as well as URLs for NNTP newsgroup(s).