From: Ingo Molnar <mingo@elte.hu>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
David Miller <davem@davemloft.net>,
johannes@sipsolutions.net, linville@tuxdriver.com,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344
Date: Tue, 3 Nov 2009 18:04:29 +0100 [thread overview]
Message-ID: <20091103170429.GA3074@elte.hu> (raw)
In-Reply-To: <1257266984.3420.111.camel@localhost.localdomain>
Hi Marcel,
* Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Ingo,
>
> > > > > no questions that it needs fixed, I agree with you. However just blindly
> > > > > reverting something, because it fixes it for one or two people, might
> > > > > have side effects that causes more problems than the revert would
> > > > > actually fix.
> > > >
> > > > Stop whining. Really.
> > > >
> > > > Everybody understands that it should be fixed. That's not the question.
> > > >
> > > > But it should be fixed _quickly_. In this case, I have a bisection report
> > > > FROM TWO DAYS AGO. And I'm still kicking myself for not just reverting
> > > > that piece-of-shit commit then, because I spent the time to look at the
> > > > oops and the commit, and could tell that it was crap.
> > > >
> > > > Instead, I _did_ wait for the subsystem maintainer to get around to it. As
> > > > a result of waiting, I've now wasted time for a lot of other people.
> > >
> > > I do have a patch in my inbox from Johannes from 4 days ago that fixes
> > > this issue.
> > >
> > > http://marc.info/?l=linux-wireless&m=125697124819563&w=2
> > >
> > > So what is the take away from this now? Do you wanna have Johannes
> > > step over John and Dave and send such a patch directly to you?
> >
> > The problem as i see it is the kind of answer Johannes gave when the bug
> > was bisected to by Jeff Chua two days ago:
> >
> > Subject: wpa2 hangs v2.6.32-rc5-402-gb6727b1. Revert
> > 7d930bc33653d5592dc386a76a38f39c2e962344 fixed it.
> >
> > [ <1257151742.3555.165.camel@johannes.local> ]
> > ...
> > |
> > | On Sun, 2009-11-01 at 23:18 +0800, Jeff Chua wrote:
> > | > wpa2 (wpa_supplicant) hangs v2.6.32-rc5-402-gb6727b1.
> > |
> > | Explain?
> > |
> > | > Reverting 7d930bc33653d5592dc386a76a38f39c2e962344 fixes it.
> > |
> > | Certainly not a good idea, will break when your AP denies association.
> > |
> > | johannes
> >
> > Unhelpful, defensive, in denial.
> >
> > Plus that you tried to berate Dmitry in this particular thread about the
> > revert was pretty bad form too IMO.
> >
> > _Anyone_ who went through the unnecessary, avoidable cost of having to
> > do a bisection of a 3 days old commit merged at around -rc5 time is in
> > his full rights to ask for a revert, straight from Linus if he thinks
> > so. No ifs and when about it.
> >
> > So IMO you are showing the wrong kind of attitude for a post-rc5
> > regression, by a _wide_ margin. The right kind of attitude would be:
> >
> > "Oops, my bad - thanks. I've queued up a revert."
> >
> > or:
> >
> > "Oops, my bad - thanks. Does the attached patch fix it?
> > If not we'll revert it."
> >
> > Furthermore, your 'hey, nothing happened, we fixed it after all'
> > argument is just a forewarning that you learned nothing and such
> > avoidable incidents could repeat in the future.
>
> who said 'hey, nothing happened, we fixed it after all'. The fix for
> this issue is 4 days old and was already on the way to Linus. And I
> remember the first response was that this got fixed already and that the
> patch is going to Linus.
Well, what formed my opinion was the first response to Jeff Chua's
bisection result - see it above, i quoted it in its entirety.
Thanks,
Ingo
next prev parent reply other threads:[~2009-11-03 17:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 5:31 Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344 Dmitry Torokhov
2009-11-03 6:49 ` David Miller
2009-11-03 6:52 ` Dmitry Torokhov
2009-11-03 7:16 ` Marcel Holtmann
2009-11-03 7:44 ` Johannes Berg
2009-11-03 8:22 ` Dmitry Torokhov
2009-11-03 8:31 ` Johannes Berg
2009-11-03 8:47 ` Dmitry Torokhov
2009-11-03 8:57 ` Johannes Berg
2009-11-03 15:29 ` Marcel Holtmann
2009-11-03 15:38 ` Linus Torvalds
2009-11-05 19:19 ` Pavel Machek
2009-11-03 15:31 ` Linus Torvalds
2009-11-04 6:34 ` Andrew Morton
2009-11-04 8:41 ` David Miller
2009-11-04 15:23 ` Andrew Morton
2009-11-04 16:32 ` David Miller
2009-11-03 15:26 ` Linus Torvalds
2009-11-03 15:36 ` Marcel Holtmann
2009-11-03 15:43 ` Linus Torvalds
2009-11-03 16:07 ` Linus Torvalds
2009-11-03 16:08 ` Marcel Holtmann
2009-11-03 16:23 ` Linus Torvalds
2009-11-03 16:37 ` Linus Torvalds
2009-11-03 16:44 ` Marcel Holtmann
2009-11-03 16:59 ` Linus Torvalds
2009-11-03 16:29 ` Ingo Molnar
2009-11-03 16:49 ` Marcel Holtmann
2009-11-03 17:04 ` Ingo Molnar [this message]
2009-11-03 17:24 ` Luis R. Rodriguez
2009-11-03 17:37 ` Linus Torvalds
2009-11-03 17:49 ` Dmitry Torokhov
2009-11-03 17:55 ` Luis R. Rodriguez
2009-11-03 15:54 ` Zdenek Kabelac
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=20091103170429.GA3074@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox