All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	vvscore@gmail.com
Subject: Re: [PATCH] 8250: Fix oops from setserial
Date: Fri, 29 May 2009 20:54:29 -0700	[thread overview]
Message-ID: <20090529205429.c9c73b19.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090528130132.19582.65165.stgit@t61.ukuu.org.uk>

On Thu, 28 May 2009 14:01:35 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> From: Alan Cox <alan@linux.intel.com>
> 
> [Impact: ok I just put this here to wind up Linus]
> 
> If you setserial a port which has never been initialised we change the type
> but don't update the I/O method pointers. The same problem is true if you
> change the io type of a port - but nobody ever does that so nobody noticed!
> 
> Remember the old type and when attaching if the type has changed reload the
> port accessor pointers. We can't do it blindly as some 8250 drivers load custom
> accessors and we must not stomp those.
> 
> Closes-bug: #13367

Please quote the full bug URL.

a) for consistency

b) because there are multiple bug tracking systems out there:

y:/usr/src/git26> git-log|grep bugzilla.redhat|wc -l
123

>  static void set_io_from_upio(struct uart_port *p)
>  {
> +	struct uart_8250_port *up = (struct uart_8250_port *)p;

container_of() is nicer, IMO.  It's clearer, and doesn't require that
the uart_port be the fist member.


  reply	other threads:[~2009-05-30  3:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 13:01 [PATCH] 8250: Fix oops from setserial Alan Cox
2009-05-30  3:54 ` Andrew Morton [this message]
2009-05-30  8:25   ` Alan Cox
2009-05-30  8:43     ` Andrew Morton
2009-05-30 10:46       ` Alan Cox
2009-05-30 18:50         ` Andrew Morton

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=20090529205429.c9c73b19.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vvscore@gmail.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.