All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffin Philip <jeffinphilip14@gmail.com>
To: gregkh@linuxfoundation.org
Cc: i@zenithal.me, jeffinphilip14@gmail.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	shuah@kernel.org, stable@vger.kernel.org,
	syzbot+af76b01c9a0f0ab60fb0@syzkaller.appspotmail.com,
	valentina.manea.m@gmail.com
Subject: [PATCH v2] usbip: usbip_host: fix null pointer dereference in
Date: Sat,  8 Aug 2026 21:37:31 +0530	[thread overview]
Message-ID: <20260808160731.8698-1-jeffinphilip14@gmail.com> (raw)
In-Reply-To: <2026080737-drank-trodden-16e4@gregkh>

On Fri, Aug 07, 2026 at 03:09:56PM +0200, Greg KH wrote:
>If you do not hold a lock when testing and doing something based on a
>field, it will race and is broken.
>
>Again, step back and try to determine what you are trying to fix here,
>and how that can be done in a race-free way.  If you don't know, that's
>fine too, I sure don't!  :)

I read the whole driver, and udev does not seem to be nulled anywhere
except in stub_probe(), where it is only assigned. So, we can safely
check for null udev alone. The driver itself seems to hold itself
together as currently I don't see a potential race. probe() also 
cannot run as we set our status to STUB_BUSID_OTHER under lock so 
probe would ignore that too. Am I missing something else here that
could create a potential race? Please advise.

Thanks,
Jeffin.

      parent reply	other threads:[~2026-08-08 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  4:37 [PATCH v2] usbip: usbip_host: fix null pointer dereference in Jeffin Philip
2026-08-07  6:00 ` Greg KH
2026-08-07 10:18   ` Jeffin Philip
2026-08-07 13:09     ` Greg KH
2026-08-07 15:36       ` Jeffin Philip
2026-08-08 16:07       ` Jeffin Philip [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=20260808160731.8698-1-jeffinphilip14@gmail.com \
    --to=jeffinphilip14@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=i@zenithal.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+af76b01c9a0f0ab60fb0@syzkaller.appspotmail.com \
    --cc=valentina.manea.m@gmail.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 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.