From: Matthew Wilcox <willy@infradead.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
iommu@lists.linux-foundation.org, linux-mm@kvack.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v4 9/9] dmapool: debug: prevent endless loop in case of corruption
Date: Mon, 12 Nov 2018 22:36:01 -0800 [thread overview]
Message-ID: <20181113063601.GT21824@bombadil.infradead.org> (raw)
In-Reply-To: <9e65ec2e-5e22-4f65-7b92-ca2af0c555f3@cybernetics.com>
On Mon, Nov 12, 2018 at 10:46:35AM -0500, Tony Battersby wrote:
> Prevent a possible endless loop with DMAPOOL_DEBUG enabled if a buggy
> driver corrupts DMA pool memory.
>
> Signed-off-by: Tony Battersby <tonyb@cybernetics.com>
I like it! Also, here you're using blks_per_alloc in a way which isn't
normally in the performance path, but might be with the right config
options. With that, I withdraw my objection to the previous patch and
Acked-by: Matthew Wilcox <willy@infradead.org>
Andrew, can you funnel these in through your tree? If you'd rather not,
I don't mind stuffing them into a git tree and asking Linus to pull
for 4.21.
next prev parent reply other threads:[~2018-11-13 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 15:46 Tony Battersby
2018-11-13 6:36 ` Matthew Wilcox [this message]
2018-12-04 16:22 ` Tony Battersby
2018-12-04 20:14 ` Andrew Morton
2018-12-04 20:18 ` Matthew Wilcox
2018-12-04 20:28 ` Andrew Morton
2018-12-04 20:35 ` Matthew Wilcox
2018-12-04 20:30 ` Andy Shevchenko
2018-12-04 21:26 ` Tony Battersby
2018-12-04 22:05 ` Andy Shevchenko
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=20181113063601.GT21824@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=tonyb@cybernetics.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