diff options
| author | Jesper Dangaard Brouer | 2019-06-18 15:05:53 +0200 |
|---|---|---|
| committer | David S. Miller | 2019-06-19 17:23:13 +0200 |
| commit | d956a048cd3fc1ba154101a1a50fb37950081ff6 (patch) | |
| tree | 79e45a34946dc77756fc1a508c78f84193ba1b86 /include/trace | |
| parent | xdp: tracking page_pool resources and safe removal (diff) | |
| download | kernel-qcow2-linux-d956a048cd3fc1ba154101a1a50fb37950081ff6.tar.gz kernel-qcow2-linux-d956a048cd3fc1ba154101a1a50fb37950081ff6.tar.xz kernel-qcow2-linux-d956a048cd3fc1ba154101a1a50fb37950081ff6.zip | |
xdp: force mem allocator removal and periodic warning
If bugs exists or are introduced later e.g. by drivers misusing the API,
then we want to warn about the issue, such that developer notice. This patch
will generate a bit of noise in form of periodic pr_warn every 30 seconds.
It is not nice to have this stall warning running forever. Thus, this patch
will (after 120 attempts) force disconnect the mem id (from the rhashtable)
and free the page_pool object. This will cause fallback to the put_page() as
before, which only potentially leak DMA-mappings, if objects are really
stuck for this long. In that unlikely case, a WARN_ONCE should show us the
call stack.
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions