mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Young" <hidave.darkstar@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: jens.axboe@oracle.com, marcel@holtmann.org,
	linux-kernel@vger.kernel.org, bluez-devel@lists.sourceforge.net,
	netdev@vger.kernel.org
Subject: Re: [PATCH retry] bluetooth : add conn add/del workqueues to avoid connection fail
Date: Fri, 1 Feb 2008 10:57:50 +0800	[thread overview]
Message-ID: <a8e1da0801311857rca1c9abmbff748d6708b995c@mail.gmail.com> (raw)
In-Reply-To: <20080131.183358.229943667.davem@davemloft.net>

On Feb 1, 2008 10:33 AM, David Miller <davem@davemloft.net> wrote:
> From: Dave Young <hidave.darkstar@gmail.com>
> Date: Fri, 1 Feb 2008 09:24:41 +0800
>
>
> > On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
> > > On Wed, Jan 30 2008, Dave Young wrote:
> > > >
> > > > The bluetooth hci_conn sysfs add/del executed in the default workqueue.
> > > > If the del_conn is executed after the new add_conn with same target,
> > > > add_conn will failed with warning of "same kobject name".
> > > >
> > > > Here add btaddconn & btdelconn workqueues,
> > > > flush the btdelconn workqueue in the add_conn function to avoid the issue.
> > > >
> > > > Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
> > > >
> > > > ---
> > > > diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
> > > > --- a/net/bluetooth/hci_sysfs.c   2008-01-30 10:14:27.000000000 +0800
> > > > +++ b/net/bluetooth/hci_sysfs.c   2008-01-30 10:14:14.000000000 +0800
> > > > @@ -12,6 +12,8 @@
> > > >  #undef  BT_DBG
> > > >  #define BT_DBG(D...)
> > > >  #endif
> > > > +static struct workqueue_struct *btaddconn;
> > > > +static struct workqueue_struct *btdelconn;
> > > >
> > > >  static inline char *typetostr(int type)
> > > >  {
> > > > @@ -279,6 +281,7 @@ static void add_conn(struct work_struct
> > > >   struct hci_conn *conn = container_of(work, struct hci_conn, work);
> > > >   int i;
> > > >
> > > > + flush_workqueue(btdelconn);
> > > >   if (device_add(&conn->dev) < 0) {
> > > >           BT_ERR("Failed to register connection device");
> > > >           return;
> > > > @@ -313,6 +316,7 @@ void hci_conn_add_sysfs(struct hci_conn
> > > >
> > > >   INIT_WORK(&conn->work, add_conn);
> > > >
> > > > + queue_work(btaddconn, &conn->work);
> > > >   schedule_work(&conn->work);
> > > >  }
> > >
> > > So you queue &conn->work on both btaddconn and keventd_wq?
> >
> > My fault. Thanks for pointing out.
> >
> > new patch as following (some fixes according to marcel's style as well)
>
> Your original patch was already in the tree, so I just checked
> in the relative changes.
>
> Please don't me do this next time :-)

David, sorry for it. Should be more careful.

Thanks :)

      reply	other threads:[~2008-02-01  2:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  2:23 Dave Young
2008-01-30  5:14 ` David Miller
2008-01-30 10:21   ` Marcel Holtmann
2008-01-31  1:29     ` Dave Young
2008-01-31 13:09 ` Jens Axboe
2008-02-01  1:24   ` Dave Young
2008-02-01  2:33     ` David Miller
2008-02-01  2:57       ` Dave Young [this message]

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=a8e1da0801311857rca1c9abmbff748d6708b995c@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.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®