All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eugeny S. Mints" <emints@ru.mvista.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, David Brownell <david-b@pacbell.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: race in usbnet.c in full RT
Date: Wed, 08 Jun 2005 16:45:05 +0400	[thread overview]
Message-ID: <42A6E851.2010504@ru.mvista.com> (raw)
In-Reply-To: <1118231726.8255.7.camel@localhost.localdomain>

Steven Rostedt wrote:
> On Wed, 2005-06-08 at 12:34 +0200, Ingo Molnar wrote:
> 
>>* Eugeny S. Mints <emints@ru.mvista.com> wrote:
>>
>>
>>>seems there is a race in drivers/net/usbnet.c in full RT mode. To be 
>>>honest I haven't hardly checked this on the latest kernel and latest 
>>>RT patch but just took a look at usbnet.c and latest RT patch and 
>>>haven't observed any related changes.
>>
>>thanks, i've applied your patch to my tree. Note that your patch is 
>>specific to the -RT kernel (both in terms of semantics and in term of 
>>API dependence), so it does not make any sense to apply it upstream.  
>>David, please ignore it.
>>
> 
> 
> Is this action only take place on the same CPU, or is this also an SMP
> problem?  I would think if this is a race with full RT, that this may
> also be a race with SMP, unless the race is guaranteed to always happen
> on the same CPU. Then this is only a RT problem.
thanks, good point. looks like it could be SMP problem but probably 
David is able to say it for sure as usb host code expert.
David?
	Eugeny
> 
> -- Steve
> 
> 
> 
> 



      reply	other threads:[~2005-06-08 12:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 10:21 race in usbnet.c in full RT Eugeny S. Mints
2005-06-08 10:16 ` Christoph Hellwig
2005-06-08 10:34 ` Ingo Molnar
2005-06-08 11:49   ` Eugeny S. Mints
2005-06-08 11:55   ` Steven Rostedt
2005-06-08 12:45     ` Eugeny S. Mints [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=42A6E851.2010504@ru.mvista.com \
    --to=emints@ru.mvista.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.