[lttng-dev] [PATCH lttng-modules 3/5] Fix: pipe: stop using ->can_merge (v5.1)
Michael Jeanson
mjeanson at efficios.com
Mon Mar 18 16:20:34 EDT 2019
See upstream commit:
commit 01e7187b41191376cee8bea8de9f907b001e87b4
Author: Jann Horn <jannh at google.com>
Date: Wed Jan 23 15:19:18 2019 +0100
pipe: stop using ->can_merge
Al Viro pointed out that since there is only one pipe buffer type to which
new data can be appended, it isn't necessary to have a ->can_merge field in
struct pipe_buf_operations, we can just check for a magic type.
Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
---
lib/ringbuffer/ring_buffer_splice.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/ringbuffer/ring_buffer_splice.c b/lib/ringbuffer/ring_buffer_splice.c
index 468641b..52179a7 100644
--- a/lib/ringbuffer/ring_buffer_splice.c
+++ b/lib/ringbuffer/ring_buffer_splice.c
@@ -43,7 +43,9 @@ static void lib_ring_buffer_pipe_buf_release(struct pipe_inode_info *pipe,
}
static const struct pipe_buf_operations ring_buffer_pipe_buf_ops = {
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(5,1,0))
.can_merge = 0,
+#endif
#if (LINUX_VERSION_CODE < KERNEL_VERSION(3,15,0))
.map = generic_pipe_buf_map,
.unmap = generic_pipe_buf_unmap,
--
2.17.1
More information about the lttng-dev
mailing list