linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: alan-jenkins@tuffmail.co.uk
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath5k-devel@lists.ath5k.org
Subject: Re: net/wireless/reg.c:1196: warning: ‘channel_after’ may be used uninitialised in this function
Date: Wed, 15 Apr 2009 09:02:32 -0400	[thread overview]
Message-ID: <20090415130232.GA21411@tuxdriver.com> (raw)
In-Reply-To: <9b2b86520904150358u81dd977g3378ef81d7748355@mail.gmail.com>

On Wed, Apr 15, 2009 at 11:58:39AM +0100, Alan Jenkins wrote:
> [Corrected Luis address]
>=20
> On 4/15/09, Alan Jenkins <sourcejedi.lkml@googlemail.com> wrote:
> > On 4/10/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> >> Thanks pavel, please try this patch:
> >>
> >> From 94505af850bd0961a86e2786238ac0bbe0c44615 Mon Sep 17 00:00:00 =
2001
> >> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> >> Date: Fri, 10 Apr 2009 11:07:43 -0700
> >> Subject: [PATCH] cfg80211: fix bug while trying to process obeacon=
 hints
> >> on
> >> init
> >>
> >> During initialization we would not have received any beacons
> >> so skip processing reg beacon hints, also adds a check to
> >> reg_is_world_roaming() for last_request before accessing its
> >> fields.
> >
> > Hi again
> >
> > I'm building wireless-testing to test the rfkill-rewrite patches on
> > top of.  I need to apply the patch referenced above as well.
> >
> > When I applied the above patch, I noticed this unrelated warning
> >
> > net/wireless/reg.c: In function =E2=80=98wiphy_update_regulatory=E2=
=80=99:
> > net/wireless/reg.c:1196: warning: =E2=80=98channel_after=E2=80=99 m=
ay be used
> > uninitialised in this function
> > net/wireless/reg.c:1196: note: =E2=80=98channel_after=E2=80=99 was =
declared here
> > net/wireless/reg.c:1196: warning: =E2=80=98channel_before=E2=80=99 =
may be used
> > uninitialised in this function
> > net/wireless/reg.c:1196: note: =E2=80=98channel_before=E2=80=99 was=
 declared here
> >
> > Looking at the code, I think it does need fixing.  There's even a
> > comment which says "this finds them (or not)" - and if they're not
> > found, channel_before / channel_after will be unset.

I reverted the (HT40-related) patch series that last touched that line.
Hopefully that resolves that warning.

> Um, also the new "ath" module taints the kernel
>=20
> ath: module 'unspecified' taints kernel.
>=20
> and I get a new BUG in freq_reg_info_regd.  I'll send the full trace
> as soon as someone reassures it is welcome and wireless-testing is
> really intended for testing at the current time :-).

Someone probably wants to see it. :-)

John
--=20
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-15 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 10:45 net/wireless/reg.c:1196: warning: ‘channel_after’ may be used uninitialised in this function Alan Jenkins
2009-04-15 10:58 ` Alan Jenkins
2009-04-15 13:02   ` John W. Linville [this message]
2009-04-15 14:17     ` BUG in freq_reg_info_regd Alan Jenkins
2009-04-15 15:09       ` [ath5k-devel] " Bob Copeland
2009-04-15 15:13         ` Alan Jenkins
2009-04-15 16:08           ` Bob Copeland
2009-04-17 10:22             ` Alan Jenkins

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=20090415130232.GA21411@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).