mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <stoffel@lucent.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: John Stoffel <stoffel@lucent.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH CYCLADES 1/2] fix cli()/sti() for ISA Cyclom-Y boards
Date: Wed, 18 Jun 2003 21:05:00 -0400	[thread overview]
Message-ID: <16113.3132.953080.164174@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030618224323.GE6754@parcelfarce.linux.theplanet.co.uk>


viro> On Wed, Jun 18, 2003 at 05:48:17PM -0400, John Stoffel wrote:
>> -    save_flags(flags); cli();
>> +    spin_lock_irqsave(&isa_card_lock, flags);
>> 
>> if ((e1 = tty_unregister_driver(cy_serial_driver)))
>> printk("cyc: failed to unregister Cyclades serial driver(%d)\n",
>> e1);
>> 
>> -    restore_flags(flags);
>> +    spin_unlock_irqrestore(&isa_card_lock,flags);

viro> It doesn't fix the problem and only makes the compile trouble go
viro> away.  Not to mention anything else, you are relying on a lot of
viro> code being non-blocking.

viro> Could you explain what is protected by disabling interrupts and
viro> taking a spinlock here?

Honestly, I'm not sure.  My original patch was against 2.5.69, which
didn't have this section of code at all, I think there have been some
patches to the code between 2.5.69 and 2.5.72 which have mucked around
with stuff.

It looked suspicious to me as well, and I'd be happy to remove this
from my patch, since I don't know what locking is needed around this
section of code off hand.  Let me look at some other drivers and see
how they unregister themselves.  Maybe theres a tty_drive_spinlock
somewhere that should be used instead.

Thanks for your comments, good to see you back on l-k.

John

      reply	other threads:[~2003-06-19  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 21:48 John Stoffel
2003-06-18 22:43 ` viro
2003-06-19  1:05   ` John Stoffel [this message]

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=16113.3132.953080.164174@gargle.gargle.HOWL \
    --to=stoffel@lucent.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

all inboxes | Powered by JetHome®