From: Ian Pilcher <arequipeno@gmail.com>
To: torvic9@mailbox.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH v10 0/2] Introduce block device LED trigger
Date: Wed, 7 Sep 2022 10:11:56 -0500 [thread overview]
Message-ID: <3097d4b8-a9d0-878c-3b95-5499ed943576@gmail.com> (raw)
In-Reply-To: <2047607620.67144.1662552964865@office.mailbox.org>
On 9/7/22 07:16, torvic9@mailbox.org wrote:
> Hi Ian,
>
> with a heavily patched Linux 6.0-rc4 with kfence, kmemleak and slub_debug I get the
> following splat at boot:
Sorry about that! I'm not sure how that slipped throgh, as I was sure
that I tested the new version before I sent it off.
Basically, I messed up while cleaning up the function parameter names,
so you need to apply this:
--- drivers/leds/trigger/ledtrig-blkdev.c.old 2022-09-07
10:00:26.194484681 -0500
+++ drivers/leds/trigger/ledtrig-blkdev.c 2022-09-04
11:36:16.107690614 -0500
@@ -540,7 +540,7 @@
return ERR_PTR(-ENOMEM);
bdev = blkdev_get_by_path(strim(buf), BLKDEV_TRIG_FMODE,
THIS_MODULE);
- kfree(path);
+ kfree(buf);
return bdev;
}
> I'm not 100% sure if this is an issue with ledtrig_blkdev or something else,
> but I thought I'll let you know about it.
> I have not been able to test this on a vanilla kernel yet.
Defnintely my fault.
> Other than that, I hope this patchset gets included in upstream.
> I have been using it for a long time now and found it very useful.
It's really hard to know if anyone is interested in/using this, so
that's great to hear.
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
next prev parent reply other threads:[~2022-09-07 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 12:16 torvic9
2022-09-07 15:11 ` Ian Pilcher [this message]
2022-09-08 8:37 ` torvic9
-- strict thread matches above, loose matches on Subject: below --
2022-09-01 19:40 Ian Pilcher
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=3097d4b8-a9d0-878c-3b95-5499ed943576@gmail.com \
--to=arequipeno@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=torvic9@mailbox.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®