mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: russ.dill@gmail.com
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, Alan Stern <stern@rowland.harvard.edu>,
	Greg KH <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: [GIT PATCH] USB patches for 2.6.33-git
Date: Mon, 14 Dec 2009 20:17:52 -0700 (MST)	[thread overview]
Message-ID: <g383sjib9r8nlmw354UYAxe124vaj_firegpg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0912141902040.14385@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]



On Mon, Dec 14, 2009 at 8:09 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 14 Dec 2009, Linus Torvalds wrote:
>>
>> I'll double-check by reverting it from current -tip, but if you don't hear
>> anything different from me, you can assume that that double-check
>> succeeded and confirms that that commit really is the cause of my printer
>> no longer working.
>
> Confirmed.
>
> With that commit reverted, everything works fine again. So it's definitely
> a2582bd478c13c574d4c16ef1209d333f2a25935, although I have no idea _why_ it
> causes problems.
>
> One thing I note is that it literally changed semantics, as per the
> comment in there. It used to be:
>
>        This walks the driver device list and returns a pointer to the interface
>        with the matching minor.
>
> and after that it is
>
>        This walks the bus device list and returns a pointer to the interface
>        with the matching minor.
>
> Notice the "driver device list" -> "bus device list" change.
>
> Also notice that the minor number of my 'lp0' device is zero, so I could
> easily imagine that some device without a driver at all or whatever will
> have a zero there, and then it would return the wrong device entirely.
>
> So I really think that commit is very suspect. Not matching against the
> driver that we passed in looks like some total screwup.
>
> But I don't know the code or the use. I do know that reverting it fixes
> it.

Yes, you are right. Sorry for breaking your printer. There is both USB_MAJOR and USB_DEVICE_MAJOR. I haven't investigated it in great detail yet, but that seems likely to be the issue. I'll clean up the patch. And yes, it should definitely not be going into stable yet. Revert for now and I'll resubmit.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 271 bytes --]

  reply	other threads:[~2009-12-15  3:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 21:26 Greg KH
2009-12-12  6:59 ` [build failure] " Ingo Molnar
2009-12-12  7:00   ` David Miller
2009-12-12  7:15     ` [PATCH] kaweth: Replace runtime power management primitives Ingo Molnar
2009-12-15  0:39 ` [GIT PATCH] USB patches for 2.6.33-git Linus Torvalds
2009-12-15  0:52   ` Greg KH
2009-12-15  1:00     ` Linus Torvalds
2009-12-15  1:47       ` Linus Torvalds
2009-12-15  2:29         ` Linus Torvalds
2009-12-15  3:09           ` Linus Torvalds
2009-12-15  3:17             ` russ.dill [this message]
2009-12-15  4:00               ` Russ Dill
2009-12-15  4:28                 ` Linus Torvalds
2009-12-15  4:44                   ` Linus Torvalds
2009-12-15 14:31                     ` Greg KH
2009-12-15  4:36                 ` Linus Torvalds
2009-12-15  4:45                   ` Russ Dill
2009-12-15  6:02                     ` Linus Torvalds
2009-12-15  6:11                       ` Russ Dill
2009-12-15  6:20                         ` Linus Torvalds
2010-03-02 23:09 Greg KH

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=g383sjib9r8nlmw354UYAxe124vaj_firegpg@mail.gmail.com \
    --to=russ.dill@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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

all inboxes | Powered by JetHome®