From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linville@redhat.com
Subject: Re: Oops/Warning report of the week of July 4th 2008
Date: Fri, 4 Jul 2008 18:23:41 -0400 [thread overview]
Message-ID: <20080704222341.GB9792@redhat.com> (raw)
In-Reply-To: <486EA0D6.2040504@linux.intel.com>
On Fri, Jul 04, 2008 at 03:14:46PM -0700, Arjan van de Ven wrote:
> The stats look very similar to last week; Fedora released a 2.6.25.9 based
> kernel upgrade, which led to a new sighting (at rank 12): the rt25xx wireless
> driver is calling flush_workqueue() with a NULL parameter in some cases.
> There has been a lot of thrash about the last report with regard to inclusion of wireless.git
> into the Fedora kernel rpms. As an observer I can say that it's both a blessing and a bog.
> It's a blessing in that this allows bugs to show up early before wireless.git hits mainline
> (as an example: this is the third or fourth fedora rpm upgrade in a row that showed new and exciting
> oopses/warnings due to rt25xx... as a result of very active development). It's a bog in that
> it may expose users to not-quite-ready code. So far it seems the Fedora kernel maintainers are happy
> enough with the overall balance that they continue the practice.
I actually think we need to scale things back a notch wrt pushing
wireless.git bits to users of released distros. The recent disaster
in wireless caused a shitstorm in bugzilla that we never even saw
in rawhide. A clear sign that we're pushing things too fast to users.
It's great that we're getting this stuff tested, but at the same time,
it doesn't give a great impression, and makes users reluctant to always
apply the latest updates if the last time around they have to deal with
this kind of fallout.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-07-04 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 22:14 Oops/Warning report of the week of July 4th 2008 Arjan van de Ven
2008-07-04 22:23 ` Dave Jones [this message]
2008-07-07 15:55 ` John W. Linville
2008-07-07 15:55 ` John W. Linville
2008-07-04 22:38 ` Ivo van Doorn
2008-07-04 22:56 ` Arjan van de Ven
2008-07-05 6:39 ` Ingo Molnar
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=20080704222341.GB9792@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@redhat.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.