mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lin Ma" <linma@zju.edu.cn>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: wkang77@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH v1 1/2] staging: gdm724x: fix type confusion in gdm_lte_event_rcv()
Date: Thu, 3 Jul 2025 15:03:46 +0800 (GMT+08:00)	[thread overview]
Message-ID: <7792df9a.9245.197cf193a6a.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <2025070355-uncommon-handlebar-c6f3@gregkh>

Hello Greg,

> > ```
> > 
> > - by `dev->type`. See ax25_device_event()
> > ```
> > static int ax25_device_event(struct notifier_block *this, unsigned long event,
> >                  void *ptr)
> > {
> >     struct net_device *dev = netdev_notifier_info_to_dev(ptr);
> > 
> >     ......
> > 
> >     /* Reject non AX.25 devices */
> >     if (dev->type != ARPHRD_AX25)
> >         return NOTIFY_DONE;
> > ```
> 
> 
> Those are core functions that all drivers are using, and the "type" of
> device is also ok to look at.  You are trying to compare a specific
> callback in this change, which feels wrong to me.

Got it. I will try to prepare another version.

> 
> Wait, what tree are you making this change against?  I don't even see
> the file you are trying to patch in the latest tree, are you sure it's
> not just deleted already?
> 
> ...
> 
> Again, make sure this file is still present in the tree before going
> further :)
> 
> thanks,
> 
> greg k-h

Yes, you are right, just like how I pointed out in the patch:

"""
This bug was "fixed" in upstream kernel by the commit 1c2d364e7f7f
("staging: gdm724x: Remove unused driver"). However, other stable
versions still contain it. Fix the confusion bug by adding checks.
"""

That is, together with another identified bug, has already been deleted the
latest upstream kernel. (see https://lore.kernel.org/lkml/20250703052837.15458-1-linma@zju.edu.cn/T/#u)

I sent this patch just because the stable version, like 5.15.186, still
contains it. T.T

Therefore, shall I proceed with the patches? Or maybe the stable tree
could also delete that vulnerable code?


Thanks for the reply!


Sincerely
Lin

  reply	other threads:[~2025-07-03  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  5:27 Lin Ma
2025-07-03  5:44 ` Greg KH
2025-07-03  6:29   ` Lin Ma
2025-07-03  6:45     ` Greg KH
2025-07-03  7:03       ` Lin Ma [this message]
2025-07-03  7:48         ` Greg KH
2025-07-03  8:21           ` Lin Ma

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=7792df9a.9245.197cf193a6a.Coremail.linma@zju.edu.cn \
    --to=linma@zju.edu.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=stable@kernel.org \
    --cc=wkang77@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 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®