linux-kernel - Re: splice methods in character device driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 13 Jun 2009 00:05:09 +0200
From:	Leon Woestenberg <leon.woestenberg@...il.com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Steve Rottinger <steve@...tek.com>, linux-kernel@...r.kernel.org
Subject: Re: splice methods in character device driver

Hello Jens,

On Mon, Jun 8, 2009 at 9:05 AM, Jens Axboe<jens.axboe@...cle.com> wrote:
> On Sat, Jun 06 2009, Leon Woestenberg wrote:
>> How can I pass information from the splice_read(), which spawns a hardware
>> DMA to the pages in my case, to the confirm() hook which is called at some
>> (random) time in the future?
>
> There's a ->private for each pipe_buffer, so you can pass along info on
> a per-page granularity.
>
So, this means in my driver's splice_read(), I must set
pipe->bufs[i]->private for each 0 <= i < PIPE_BUFFERS?


struct pipe_buffer {
   ...
   unsigned long private;
};
struct pipe_inode_info {
   ...
   struct pipe_buffer bufs[PIPE_BUFFERS];
};
static int splice_read(..., struct pipe_inode_info *pipe, ...)

Regards,
-- 
Leon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/