Re: [PATCH]bluetooth rfcomm_dev refcount bug fix

Hi Dave,

> I'm afraid to be considered as spam ;)
> 
> (Due to timezone offset, I have to mail again and cann't wait for your
> reply, sorry for the annoying)

I am in a different timezone every other week. So nevermind ;)

> I think the rfcomm_dev_put could be seperated from the rfcomm_dev_put,
> it will be more straitforward then.
> 
> please consider below patch, tested on my side. thanks.

That one looks totally wrong to me. Without even testing it, it will
have side effects that you haven't run into yet. Unless the TTY core
changed so much, this comments are there for a really good reason and
the code is tested a lot.

Also if you have to do two rfcomm_dev_put() in a row, then we are doing
something really wrong and this tries to hide a real bug somewhere.

Regards

Marcel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH]bluetooth rfcomm_dev refcount bug fix
    • From: "Dave Young" <[email protected]>

• References:
  • Re: [PATCH]bluetooth rfcomm_dev refcount bug fix
    • From: Dave Young <[email protected]>

• Prev by Date: Re: [PATCH -net 2/2] Put proc_net_create() on death row
• Next by Date: Re: [PATCH] Smackv10: Smack rules grammar + their stateful parser
• Previous by thread: Re: [PATCH]bluetooth rfcomm_dev refcount bug fix
• Next by thread: Re: [PATCH]bluetooth rfcomm_dev refcount bug fix
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]