All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: randall@uph.com
Cc: Balbir Singh <balbir_soni@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Patch: Fix serial module use count (2.4.16 _and_ 2.5)
Date: Thu, 29 Nov 2001 18:12:27 +0000	[thread overview]
Message-ID: <20011129181227.I6214@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20011129160637.50471.qmail@web13606.mail.yahoo.com> <200111291803.fATI37q08404@sword.damocles.com>
In-Reply-To: <200111291803.fATI37q08404@sword.damocles.com>; from randall@sword.damocles.com on Thu, Nov 29, 2001 at 12:03:07PM -0600

On Thu, Nov 29, 2001 at 12:03:07PM -0600, Jeff Randall wrote:
> All of the other UNIX variants I've dealth with behave that way.
> However, you cannot just make that change without having some means
> of identifying that behavior change because all of the linux
> serial drivers have been written to assume that their close()
> will be called even after their open() has failed.

It's not only serial drivers, its everything that is a tty driver.
I believe that auditing and fixing that lot in 2.4 just isn't going
to happen - it's supposed to be a stable kernel after all.

> I'm not opposed to such a change in behavior, but at least be
> sure that it's somehow identifiable (kernel version, a define
> set in a header, etc) so that the 3rd party drivers have a means
> to identify the change.

eg, #if KERNEL_VERSION >= LINUX_VERSION(2,5,0)

> Redhat 7.1 included that behavior change in the kernel they shipped
> and it caused no end of problems for those of us that were doing
> serial drivers since there was no way to easily identify that the
> patch had been included.

The change which adds the MOD_DEC_USE_COUNT stuff is bogus, and it
shouldn't have been made.  (I'm assuming this is what you're talking
about).

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-11-29 18:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 16:06 Patch: Fix serial module use count (2.4.16 _and_ 2.5) Balbir Singh
2001-11-29 16:17 ` Russell King
2001-11-30  4:25   ` BALBIR SINGH
2001-11-30  9:36     ` Russell King
2001-11-30 22:19     ` Mike Fedyk
2001-11-30 23:06       ` Russell King
2001-12-01  0:20         ` Mike Fedyk
2001-11-29 18:03 ` Jeff Randall
2001-11-29 18:12   ` Russell King [this message]
2001-11-29 18:44     ` Jeff Randall
2001-11-29 19:05     ` James Simmons
2001-11-30 10:44   ` Maciej W. Rozycki
2001-11-30 10:56     ` Russell King
2001-11-30 12:11       ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2001-11-29 13:10 Russell King
2001-11-29 13:48 ` BALBIR SINGH
2001-11-29 15:37   ` Russell King

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=20011129181227.I6214@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=balbir_soni@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randall@uph.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.