Skip to contentSkip to conversation

Bug with O_DIRECT in 2.6.36-rc3?

DISCUSSION Ben Greear 1 participant 2 messages Sep 3, 2010 – Sep 7, 2010

Subsystems (2)
lore
Share & tools
lore

Ben Greear

author
#0 lore raw

I was getting ENOMEM errors on write when using O_DIRECT in 2.6.36-rc3 plus the patch I just posted for srcaddr= (my test harness needs that feature to work).

It seems to work fine w/out O_DIRECT enabled.

The same patch against 2.6.34.6 works fine with and without O_DIRECT.

After the ENOMEM, I cannot un-mount, even with -f (says it's busy).

But, fuser doesn't show any users.

Anyone tried O_DIRECT recently?

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com
author
#1 lore raw
Quoted 7 lines · Ben Greear

I was getting ENOMEM errors on write when using O_DIRECT in 2.6.36-rc3 plus the
patch I just posted for srcaddr= (my test harness needs that feature to work).

It seems to work fine w/out O_DIRECT enabled.

Quoted 7 lines

The same patch against 2.6.34.6 works fine with and without O_DIRECT.

After the ENOMEM, I cannot un-mount, even with -f (says it's busy).

But, fuser doesn't show any users.

Anyone tried O_DIRECT recently?

I did some testing on un-patched kernels:

It seems this was broken after 2.6.35:

# good: [26845f585fad66dc23d87dad89d403cd64b48780] [SCSI] remove fake "address-of" expression

and before 2.6.36-rc2.

2.6.36-rc1 won't boot for me, and neither would the kernels generated by my attempt to git-bisect this further.

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com