summaryrefslogtreecommitdiffstats
path: root/drivers/char/efirtc.c
diff options
context:
space:
mode:
authorJohn Kacur <jkacur@redhat.com>2009-12-15 16:46:06 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2009-12-16 07:19:59 -0800
commitf29627c2a3df5732af84bc217df26d1c311f5112 (patch)
tree170d0e203087f4cf592fbb9584a0345028860ae0 /drivers/char/efirtc.c
parent50e49bee3fc5c0cd0aff80ebd8061f356b7b9bd8 (diff)
downloadlinux-stable-f29627c2a3df5732af84bc217df26d1c311f5112.tar.gz
linux-stable-f29627c2a3df5732af84bc217df26d1c311f5112.tar.bz2
linux-stable-f29627c2a3df5732af84bc217df26d1c311f5112.zip
efirtc: explicitly set llseek to no_llseek
Now that we've removed the BKL here, let's explicitly set llseek to no_llseek since the default llseek is not used here. The default_llseek function still contains the BKL. When we are auditing code to see if we can remove the BKL, this is one of the hidden considerations we need to take into account. i.e., is there syncronization between code that has the BKL and llseek. At the same time we remove the BKL it would be a good idea to do indicate when no llseek function is required, so we don't have to revisit this code again, when we are trying to determine if we can remove the BKL from the default_llseek. Signed-off-by: John Kacur <jkacur@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/char/efirtc.c')
-rw-r--r--drivers/char/efirtc.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/char/efirtc.c b/drivers/char/efirtc.c
index 26a47dc88f61..53c524e7b829 100644
--- a/drivers/char/efirtc.c
+++ b/drivers/char/efirtc.c
@@ -285,6 +285,7 @@ static const struct file_operations efi_rtc_fops = {
.unlocked_ioctl = efi_rtc_ioctl,
.open = efi_rtc_open,
.release = efi_rtc_close,
+ .llseek = no_llseek,
};
static struct miscdevice efi_rtc_dev= {