public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-kernel@vger.kernel.org,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	Ed Okerson <eokerson@quicknet.net>,
	Greg Herlein <gherlein@quicknet.net>,
	"David W. Erhart" <derhart@quicknet.net>,
	John Sellers <jsellers@quicknet.net>,
	Mike Preston <mpreston@quicknet.net>,
	David Huggins-Daines <dhd@cepstral.com>,
	Fabio Ferrari <fabio.ferrari@digitro.com.br>,
	Artis Kugevics <artis@mt.lv>,
	Daniele Bellucci <bellucda@tiscali.it>
Subject: Re: [PATCH 1/2] drivers/telephony/ixj.c::add_caps(): don't rely on undefined behaviour
Date: Mon, 19 Mar 2012 16:29:44 -0700	[thread overview]
Message-ID: <1332199784.7847.12.camel@joe2Laptop> (raw)
In-Reply-To: <alpine.LNX.2.00.1203200017100.9012@swampdragon.chaosbits.net>

On Tue, 2012-03-20 at 00:19 +0100, Jesper Juhl wrote:
> On Mon, 19 Mar 2012, Joe Perches wrote:
> > On Mon, 2012-03-19 at 23:46 +0100, Jesper Juhl wrote:
> > > On Mon, 19 Mar 2012, Joe Perches wrote:
> > > > On Mon, 2012-03-19 at 23:37 +0100, Jesper Juhl wrote:
> > > > > In drivers/telephony/ixj.c::add_caps() we have several statements like this:
> > > > >   	j->caplist[j->caps].handle = j->caps++;
> > > > > That's undefined behaviour right there.
> > > > telephony has been moved to staging.
> > > Since when? Where?
> > > In my up-to-date Linus tree with HEAD at 
> > > c16fa4f2ad19908a47c63d8fa436a1178438c7e7, that file is is still in 
> > > drivers/telephony/, not in staging/...
> > > /confused
> > In the -next tree.
> Ok, seems I've missed that.
> > Yes, it's a bug fix, but drivers/telephony is pretty dead.
> Dead or not, as long as it's in the tree I think that fixing bugs is 
> relevant.
> Besides, who knows if/when it'll get ressurrected ;)

Sorry, I didn't mean to suggest it shouldn't
be fixed.

I meant that it probably didn't need to be
fixed during the merge window or maybe even
not backported to stable unless you're sure
the order of operations is now done correctly
and with no real change in current operation
by inspecting the object.  I presume it worked
before but it's likely not too many people
actually still use this hardware with the
current kernel.



  reply	other threads:[~2012-03-19 23:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 22:37 [PATCH 1/2] drivers/telephony/ixj.c::add_caps(): don't rely on undefined behaviour Jesper Juhl
2012-03-19 22:44 ` Joe Perches
2012-03-19 22:46   ` Jesper Juhl
2012-03-19 23:10     ` Joe Perches
2012-03-19 23:19       ` Jesper Juhl
2012-03-19 23:29         ` Joe Perches [this message]
2012-03-19 23:40           ` Jesper Juhl
2012-03-20 13:51             ` Greg KH
2012-03-22 23:15               ` Jesper Juhl
2012-03-22 23:18                 ` Jesper Juhl
2012-03-22 23:21               ` And patch 2 as well - " Jesper Juhl

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=1332199784.7847.12.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=artis@mt.lv \
    --cc=bellucda@tiscali.it \
    --cc=derhart@quicknet.net \
    --cc=dhd@cepstral.com \
    --cc=eokerson@quicknet.net \
    --cc=fabio.ferrari@digitro.com.br \
    --cc=gherlein@quicknet.net \
    --cc=jj@chaosbits.net \
    --cc=jsellers@quicknet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=mpreston@quicknet.net \
    /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