From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Bart Van Assche <bvanassche@acm.org>,
linux-mm <linux-mm@kvack.org>,
linux-block <linux-block@vger.kernel.org>
Cc: Jianchao Wang <jianchao.w.wang@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
fsdevel <linux-fsdevel@vger.kernel.org>,
SCSI <linux-scsi@vger.kernel.org>,
Joao Pinto <jpinto@synopsys.com>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Evan Green <evgreen@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
Tomas Winkler <tomas.winkler@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bart.vanassche@wdc.com>,
Martin Petersen <martin.petersen@oracle.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Ming Lei <ming.lei@redhat.com>, Omar Sandoval <osandov@fb.com>,
Roman Gushchin <guro@fb.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: dd hangs when reading large partitions
Date: Sat, 9 Feb 2019 12:57:46 +0100 [thread overview]
Message-ID: <5aff492a-9aca-0517-264f-c0eb95f1a87f@free.fr> (raw)
In-Reply-To: <1549640986.34241.78.camel@acm.org>
On 08/02/2019 16:49, Bart Van Assche wrote:
> On Fri, 2019-02-08 at 16:33 +0100, Marc Gonzalez wrote:
>
>> Does anyone see what's going sideways in the no-flag case?
>
> Does this problem only occur with block devices backed by the UFS driver
> or does this problem also occur with other block drivers?
So far, I've only been able to test with UFS storage.
The board has no PATA/SATA. SDHC is not supported yet.
With Jeffrey's help, I was able to get a semi-functional
USB3 stack running. I'll test USB3 mass storage on Monday.
FWIW, I removed most (all?) locks from the UFSHC driver,
by dropping scaling and gating support. I could also
drop runtime suspend, if someone thinks that could help,
but I'm thinking the problem might be in the mm or block
layers?
(It doesn't look like a locking problem, but more a memory
exhaustion problem.)
Regards.
next prev parent reply other threads:[~2019-02-09 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f792574c-e083-b218-13b4-c89be6566015@free.fr>
[not found] ` <398a6e83-d482-6e72-5806-6d5bbe8bfdd9@oracle.com>
[not found] ` <ef734b94-e72b-771f-350b-08d8054a58f3@kernel.dk>
[not found] ` <20190119095601.GA7440@infradead.org>
[not found] ` <07b2df5d-e1fe-9523-7c11-f3058a966f8a@free.fr>
[not found] ` <985b340c-623f-6df2-66bd-d9f4003189ea@free.fr>
[not found] ` <b3910158-83d6-21fe-1606-33e88912404a@oracle.com>
[not found] ` <d082bdee-62e5-d470-b63b-196c0fe3b9fb@free.fr>
[not found] ` <5132e41b-cb1a-5b81-4a72-37d0f9ea4bb9@oracle.com>
[not found] ` <7bd8b010-bf0c-ad64-f927-2d2187a18d0b@free.fr>
[not found] ` <0cfe1ed2-41e1-66a4-8d98-ebc0d9645d21@free.fr>
2019-02-07 10:44 ` Marc Gonzalez
2019-02-07 16:56 ` Marc Gonzalez
2019-02-08 15:33 ` Marc Gonzalez
2019-02-08 15:49 ` Bart Van Assche
2019-02-09 11:57 ` Marc Gonzalez [this message]
2019-02-11 16:36 ` Marc Gonzalez
2019-02-11 17:27 ` Marc Gonzalez
2019-02-12 15:26 ` [SOLVED] " Marc Gonzalez
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=5aff492a-9aca-0517-264f-c0eb95f1a87f@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=bvanassche@acm.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=guro@fb.com \
--cc=hch@infradead.org \
--cc=jhugo@codeaurora.org \
--cc=jianchao.w.wang@oracle.com \
--cc=jpinto@synopsys.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mhocko@suse.com \
--cc=ming.lei@redhat.com \
--cc=mka@chromium.org \
--cc=osandov@fb.com \
--cc=swboyd@chromium.org \
--cc=tomas.winkler@intel.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