public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaliy Ivanov <vitalivanov@gmail.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: w@1wt.eu, gregkh@suse.de, linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch] Port of adutux driver from 2.6 kernel to 2.4.
Date: Fri, 19 Oct 2007 20:40:35 +0300	[thread overview]
Message-ID: <1192815634.7965.53.camel@dell1.softservecom.com> (raw)
In-Reply-To: <20071019095313.76990765.zaitcev@redhat.com>


> > Didn't here anything on this? What is our final decision here?
> 
> It's gotten worse, not better. Apparently, you aren't getting the
> concept of protecting the open count with a static lock and my
> explanations are just not vivid enough or something. So I decided
> to fix it myself. Maybe then the patch in C will explain it better
> than English. But I didn't have time to do it.

Probably I'm not trying to do what you want. I analyzed locks for other
usb drivers in 2.4 tree and used same ideas.
Static lock minor_table_mutex is used for minor table structure.
And dev->sem for dev manipulations and that's why for open_count.
If you will simply browse /drivers/usb dir for 2.4 you will see that
such approach is widely used there.
What's not right?
Certainly, you have more experience so I can't say that I'm right.

> Also, there's an outright bug in the latest version. Your purge
> of the wrong lock was incomplete and so there was an unbalanced up().
> But this is moot.

Yes, got it. It's up for minor_table_mutex in adu_release. Corrected.

> So, the version before the latest is borderline acceptable. If Willy
> wants to take it, it's fine. I'll fix it up later together with 2.6.

Let's do everything correctly for 2.4.

V.


  reply	other threads:[~2007-10-19 17:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 17:37 [2.4 patch] Port of adutux driver from 2.6 kernel to 2.4 Vitaliy Ivanov
2007-10-14 18:25 ` Willy Tarreau
2007-10-14 20:45   ` Vitaliy Ivanov
2007-10-14 22:39     ` Willy Tarreau
2007-10-16 13:54       ` Vitaliy Ivanov
2007-10-16 15:41         ` Willy Tarreau
2007-10-16 17:56           ` Pete Zaitcev
2007-10-16 18:22             ` Vitaliy Ivanov
2007-10-16 18:24             ` Willy Tarreau
2007-10-16 18:24           ` Vitaliy Ivanov
2007-10-17 18:12             ` Vitaliy Ivanov
2007-10-19 15:26               ` Vitaliy Ivanov
2007-10-19 16:53                 ` Pete Zaitcev
2007-10-19 17:40                   ` Vitaliy Ivanov [this message]
2007-10-23  3:45                     ` Pete Zaitcev
2007-11-04 14:05                       ` Willy Tarreau
2007-11-05  9:32                         ` Vitaliy Ivanov
2007-11-05  9:36                           ` Willy Tarreau
2007-10-16 17:52         ` Pete Zaitcev
2007-10-15 17:30     ` Pete Zaitcev
2007-10-15 20:04       ` Vitaliy Ivanov
2007-10-16 13:48       ` Vitaliy Ivanov
2007-10-16 14:59         ` 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=1192815634.7965.53.camel@dell1.softservecom.com \
    --to=vitalivanov@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=w@1wt.eu \
    --cc=zaitcev@redhat.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