aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2007-07-23 18:43:46 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-24 12:24:58 -0700
commit0d786d4a2773f06a791e8c3730d049077fb81df6 (patch)
treede553420b6b1a70b80034385ff94eb706bac12ab /drivers/bluetooth
parent4f640efb3170dbcf99a37a3cc99060647b95428c (diff)
downloadkernel_samsung_smdk4412-0d786d4a2773f06a791e8c3730d049077fb81df6.zip
kernel_samsung_smdk4412-0d786d4a2773f06a791e8c3730d049077fb81df6.tar.gz
kernel_samsung_smdk4412-0d786d4a2773f06a791e8c3730d049077fb81df6.tar.bz2
fallocate syscall interface deficiency
The fallocate syscall returns ENOSYS in case the filesystem does not support the operation and expects the userlevel code to fill in. This is good in concept. The problem is that the libc code for old kernels should be able to distinguish the case where the syscall is not at all available vs not functioning for a specific mount point. As is this is not possible and we always have to invoke the syscall even if the kernel doesn't support it. I suggest the following patch. Using EOPNOTSUPP is IMO the right thing to do. Cc: Amit Arora <aarora@in.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions