Re: O_DIRECT Inside Kernel Module?
- From: "jaylucasaustin.rr.com" <jaylucas@xxxxxxxxxxxxx>
- Date: Tue, 31 Jan 2006 16:22:57 GMT
The filp_open succeeds, it's the first read that fails with an EFAULT. I've
verified alignment, block, and I/O sizes as well.
"Kasper Dupont"
<61913572015144542017@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:43DF7A8B.C0BE997F@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> "jaylucasaustin.rr.com" wrote:
>>
>> I should have mentioned that I've already discovered filp_open, which is
>> the
>> open that I am using, but is failing with the O_DIRECT flag set.
>
> Is it filp_open that fails? Or is it the read and write methods?
>
> --
> Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
> #define _(_)"d.%.4s%."_"2s" /* This is my new email address */
> char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,6,_+2,_+7,_+6);
.
- References:
- O_DIRECT Inside Kernel Module?
- From: jaylucasaustin.rr.com
- Re: O_DIRECT Inside Kernel Module?
- From: Peter T. Breuer
- Re: O_DIRECT Inside Kernel Module?
- From: jaylucasaustin.rr.com
- O_DIRECT Inside Kernel Module?
- Prev by Date: select system call behavior
- Next by Date: Re: select system call behavior
- Previous by thread: Re: O_DIRECT Inside Kernel Module?
- Next by thread: Debugging the Memory leakage
- Index(es):