mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Race condition in kobject_get_path()
Date: Wed, 30 Mar 2022 11:22:59 +0200	[thread overview]
Message-ID: <YkQhc5ZjWe35T8fU@kroah.com> (raw)
In-Reply-To: <abc55eae-1e78-4389-e60c-db984ad8ed50@quicinc.com>

On Wed, Mar 30, 2022 at 02:47:20PM +0530, Mukesh Ojha wrote:
> Hi All,
> 
> We are facing one issue where one driver is trying to register its device
> from driver probe
> and from another path  dev_set_name() done from driver probe of the added
> device whose
> length can be more than earlier which could result in redzone overwritten
> issue.

What drivers are doing this so we can see the code?  This should be
happening in order and not at the same time.

> 
> Can we get your suggestion here ? is this case of a race here ?
> 
> 
> p1 p2
> 
> *kobject_get_path* <https://opengrok.qualcomm.com/source/s?refs=kobject_get_path&project=KERNEL.PLATFORM.1.0>
> 
> 
>                             =>  get_kobj_path_length  (length is calculated
> from this path)
>                                dev_set_name(same dev name)
>                                  => fill_kobj_path  (path is copied here)

I do not understand this trace, sorry.  What code are you referring to?

confused,

greg k-h

       reply	other threads:[~2022-03-30  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <abc55eae-1e78-4389-e60c-db984ad8ed50@quicinc.com>
2022-03-30  9:22 ` Greg KH [this message]
2022-03-30  9:24   ` 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=YkQhc5ZjWe35T8fU@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_mojha@quicinc.com \
    --cc=rafael@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®