linux-kernel - Re: Current status of rt2800usb and staging/rt2870

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 16 Oct 2009 19:13:43 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	Dan Williams <dcbw@...hat.com>,
	Ivo van Doorn <ivdoorn@...il.com>,
	Ozan Çağlayan <ozan@...dus.org.tr>,
	linux-wireless@...r.kernel.org,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870

On Thursday 15 October 2009 21:06:55 Luis R. Rodriguez wrote:
> On Thu, Oct 15, 2009 at 7:47 AM, Bartlomiej Zolnierkiewicz
> <bzolnier@...il.com> wrote:
> > On Wednesday 14 October 2009 18:55:23 Luis R. Rodriguez wrote:
> >
> >> I hear fishing in Poland is great this time of year.
> >
> > It got quite cold this week so I thought that I would try to fish
> > the commit that broke Atheros AR9285 in Linus' tree (works in 2.6.31)
> > and make recent kernels finally work on my laptop..
> >
> > Seems like there are two regressions actually:
> >
> > - later one making association/authentication impossible
> 
> And you reported this when and where?
> 
> > - earlier one making transfers stall
> 
> And you reported this when and where?
> 
> Curious how the issues you mention now spreading across sound and
> wireless do not get fixed or seriously addressed. Have you considered
> your tactics are perhaps not the best?

Please look closely at chosen examples and you'll see a lot of insight
telling you that users' experience is not granted by having clean code
or by having features which are not consider crucial instead of reliable
basic functionality.

I'm pretty sure that if you try F12 w/ AR9285 you will be able to reproduce
and fix at least some of above mentioned problems.  I just used the occasion
to raise them and make people aware of bugs before they hit users in final
2.6.32.

I'm not as much interested in fixing existing problems as in seeing why
they happened in the first place and how the process can be improved to
prevent them / making tracking of them easy for non-developers (so more
people can contribute to the project and developers have more time to
add new features).  I also don't have time to care about every single
Linux bug that I encounter (I hit quite a lot of them), bug-reporting
is a thankless and very time consuming work.

This is in no means trying to implicit that you're doing bad job.  Quite
the contrary -- I think that your work on Atheros support is much needed.

The point is that there is a lot of room for in release management process
of wireless/networking (it has been more-or-less unchanged for a long time
while other subsystems, i.e. x86, are constantly looking into improvements).

This is not something that you can change alone so please do not hesitate
to give feedback about this to your upstream maintainers so they are aware
of the need for improvements.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/