From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] staging: rtl8192u: Fix two crashing bugs
Date: Thu, 12 Oct 2023 08:35:43 +0200 [thread overview]
Message-ID: <2023101244-unaudited-sadly-d9d6@gregkh> (raw)
In-Reply-To: <cover.1697089416.git.philipp.g.hortmann@gmail.com>
On Thu, Oct 12, 2023 at 08:02:58AM +0200, Philipp Hortmann wrote:
> Question: Fix or remove rtl8192u?
We should remove it if it's obviously broken and no one has reported it
in a very long time.
> I found a USB WLAN Stick with a rtl8192u. I got it last Saturday and
> found out that the firmware is missing in my ubuntu 20.04. I found it on
> the web and fixed it. When I started the driver my computer crashed. The
> missing part was: priv->priv_wq = alloc_workqueue("priv_wq", 0, 0);
> Fixing this the next error was a network = kzalloc(sizeof(*network),
> GFP_KERNEL); in wrong context which leads to a crash of my computer.
> Fixing this the next error is more depending on what I do with the stick.
>
> When lucky the connection is build up and I can surf and download at maximum speed (12,5MB/s) several gigabytes.
Do you want to keep it here so that you can maintain it and keep it
working?
thanks,
greg k-h
prev parent reply other threads:[~2023-10-12 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 6:02 [RFC PATCH 0/2] staging: rtl8192u: Fix two crashing bugs Philipp Hortmann
2023-10-12 6:03 ` [RFC PATCH 1/2] staging: rtl8192u: Fix missing alloc_workqueue() Philipp Hortmann
2023-10-12 6:03 ` [RFC PATCH 2/2] staging: rtl8192u: Fix sleeping kzalloc() called from invalid context Philipp Hortmann
2023-10-12 6:35 ` Greg Kroah-Hartman [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=2023101244-unaudited-sadly-d9d6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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