public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Introduce tty_unregister_ldisc()
Date: Tue, 31 May 2005 17:28:11 -0500	[thread overview]
Message-ID: <1117578491.4627.14.camel@at2.pipehead.org> (raw)
In-Reply-To: <200505312356.00853.adobriyan@gmail.com>

This patch is wrong. Please do not apply.

An unmodified ldisc driver (externally maintained) will continue to call
tty_register_ldisc with NULL, but the new behavior will be to set the
ldisc pointer to NULL but have LDISC_FLAG_DEFINED set.

If you feel it is absolutely necessary to add this new function
for cosmetic reasons, then leave the old behavior in place
and make tty_unregister_ldisc a wrapper to tty_register_ldisc
that uses a NULL pointer.

This preserves sanity and compatibility.

The existing function has a bug:
If new_ldisc != NULL and LDISC_FLAG_DEFINED is set,
the ldisc is switched to new_ldisc without checking
for non-zero refcount of current ldisc.

--
Paul Fulghum
paulkf@microgate.com


On Tue, 2005-05-31 at 23:56 +0400, Alexey Dobriyan wrote:
> It's a bit strange to see tty_register_ldisc() call in modules' exit functions.
> ...
> --- linux-tty_register_ldisc_000/Documentation/tty.txt	2005-05-31 20:12:47.000000000 +0400
> +++ linux-tty_register_ldisc_001/Documentation/tty.txt	2005-05-31 23:19:32.000000000 +0400
> @@ -22,7 +22,7 @@ copy of the structure. You must not re-r
>  discipline even with the same data or your computer again will be eaten by
>  demons.
>  
> -In order to remove a line discipline call tty_register_ldisc passing NULL.
> +In order to remove a line discipline call tty_unregister_ldisc().
>  In ancient times this always worked. In modern times the function will
>  return -EBUSY if the ldisc is currently in use. Since the ldisc referencing
>  code manages the module counts this should not usually be a concern.
> diff -uprN linux-tty_register_ldisc_000/drivers/char/tty_io.c linux-tty_register_ldisc_001/drivers/char/tty_io.c
> --- linux-tty_register_ldisc_000/drivers/char/tty_io.c	2005-05-31 20:13:34.000000000 +0400
> +++ linux-tty_register_ldisc_001/drivers/char/tty_io.c	2005-05-31 23:17:40.000000000 +0400
> @@ -262,17 +262,10 @@ int tty_register_ldisc(int disc, struct 
>  		return -EINVAL;
>  	
>  	spin_lock_irqsave(&tty_ldisc_lock, flags);
> -	if (new_ldisc) {
> -		tty_ldiscs[disc] = *new_ldisc;
> -		tty_ldiscs[disc].num = disc;
> -		tty_ldiscs[disc].flags |= LDISC_FLAG_DEFINED;
> -		tty_ldiscs[disc].refcount = 0;
> -	} else {
> -		if(tty_ldiscs[disc].refcount)
> -			ret = -EBUSY;
> -		else
> -			tty_ldiscs[disc].flags &= ~LDISC_FLAG_DEFINED;
> -	}
> +	tty_ldiscs[disc] = *new_ldisc;
> +	tty_ldiscs[disc].num = disc;
> +	tty_ldiscs[disc].flags |= LDISC_FLAG_DEFINED;
> +	tty_ldiscs[disc].refcount = 0;
>  	spin_unlock_irqrestore(&tty_ldisc_lock, flags);
>  	
>  	return ret;
> @@ -280,6 +273,26 @@ int tty_register_ldisc(int disc, struct 
>  
>  EXPORT_SYMBOL(tty_register_ldisc);
>  
> +int tty_unregister_ldisc(int disc)
> +{
> +	unsigned long flags;
> +	int ret = 0;
> +
> +	if (disc < N_TTY || disc >= NR_LDISCS)
> +		return -EINVAL;
> +
> +	spin_lock_irqsave(&tty_ldisc_lock, flags);
> +	if (tty_ldiscs[disc].refcount)
> +		ret = -EBUSY;
> +	else
> +		tty_ldiscs[disc].flags &= ~LDISC_FLAG_DEFINED;
> +	spin_unlock_irqrestore(&tty_ldisc_lock, flags);
> +
> +	return ret;
> +}
> +
> +EXPORT_SYMBOL(tty_unregister_ldisc);
> +
>  struct tty_ldisc *tty_ldisc_get(int disc)
>  {
>  	unsigned long flags;
> diff -uprN linux-tty_register_ldisc_000/include/linux/tty.h linux-tty_register_ldisc_001/include/linux/tty.h
> --- linux-tty_register_ldisc_000/include/linux/tty.h	2005-05-31 20:15:51.000000000 +0400
> +++ linux-tty_register_ldisc_001/include/linux/tty.h	2005-05-31 23:18:23.000000000 +0400
> @@ -345,6 +345,7 @@ extern int tty_check_change(struct tty_s
>  extern void stop_tty(struct tty_struct * tty);
>  extern void start_tty(struct tty_struct * tty);
>  extern int tty_register_ldisc(int disc, struct tty_ldisc *new_ldisc);
> +extern int tty_unregister_ldisc(int disc);
>  extern int tty_register_driver(struct tty_driver *driver);
>  extern int tty_unregister_driver(struct tty_driver *driver);
>  extern void tty_register_device(struct tty_driver *driver, unsigned index, struct device *dev);
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
--
Paul Fulghum
paulkf@microgate.com


  reply	other threads:[~2005-05-31 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 19:56 [PATCH 1/2] Introduce tty_unregister_ldisc() Alexey Dobriyan
2005-05-31 22:28 ` Paul Fulghum [this message]
2005-06-01  3:38   ` Paul Fulghum
2005-06-01 13:51     ` Paul Fulghum
2005-06-01  4:39   ` Greg KH
2005-06-01  5:42   ` Christoph Hellwig
2005-06-01 15:22     ` Alexey Dobriyan
  -- strict thread matches above, loose matches on Subject: below --
2005-06-15 21:40 Alexey Dobriyan

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=1117578491.4627.14.camel@at2.pipehead.org \
    --to=paulkf@microgate.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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