mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: david-b@pacbell.net, lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jonathan Corbet <corbet@lwn.net>,
	akpm@linux-foundation.org
Subject: Re: [rtc-linux] [PATCH] rtc: remove BKL for ioctl()
Date: Wed, 25 Jun 2008 10:57:17 +0200	[thread overview]
Message-ID: <20080625105717.2d9f30b2@i1501.lan.towertech.it> (raw)
In-Reply-To: <200806221955.42597.david-b@pacbell.net>

On Sun, 22 Jun 2008 19:55:42 -0700
David Brownell <david-b@pacbell.net> wrote:

> Remove implicit use of BKL in ioctl() from the RTC framework.
> 
> Instead, the rtc->ops_lock is used.  That's the same lock that already
> protects the RTC operations when they're issued through the exported
> rtc_*() calls in drivers/rtc/interface.c ... making this a bugfix, not
> just a cleanup, since both ioctl calls and set_alarm() need to update
> IRQ enable flags and that implies a common lock (which RTC drivers as
> a rule do not provide on their own).
> 
> A new comment at the declaration of "struct rtc_class_ops" summarizes
> current locking rules.  It's not clear to me that the exceptions listed
> there should exist ... if not, those are pre-existing problems which can
> be fixed in a patch that doesn't relate to BKL removal.
> 
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>


 Acked-by: Alessandro Zummo <a.zummo@towertech.it>

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


  reply	other threads:[~2008-06-25  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23  2:55 David Brownell
2008-06-25  8:57 ` Alessandro Zummo [this message]
2008-06-25 22:39 ` Jonathan Corbet
2008-06-25 22:30   ` Alan Cox
2008-06-25 23:04     ` David Brownell
2008-06-25 23:41     ` Jonathan Corbet
2008-06-25 22:58   ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080625105717.2d9f30b2@i1501.lan.towertech.it \
    --to=alessandro.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome