From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH RESEND] mfd: wm831x-auxadc: Prevent use after free in wm831x_auxadc_read_irq()
Date: Thu, 04 Feb 2021 10:58:37 +0000 [thread overview]
Message-ID: <20210204105837.GI20820@kadam> (raw)
In-Reply-To: <20210204103724.GC2789116@dell>
On Thu, Feb 04, 2021 at 10:37:24AM +0000, Lee Jones wrote:
> On Fri, 29 Jan 2021, Dan Carpenter wrote:
>
> > The "req" struct is always added to the "wm831x->auxadc_pending" list,
> > but it's only removed from the list on the success path. If a failure
> > occurs then the "req" struct is freed but it's still on the list,
> > leading to a use after free.
> >
> > Fixes: 78bb3688ea18 ("mfd: Support multiple active WM831x AUXADC conversions")
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > ---
> > drivers/mfd/wm831x-auxadc.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Patchwork still can't find this.
>
> I've applied it manually, thanks.
Ah... You know what it is? I normally use Mutt instead of
git-send-email. Some of the patchworks have been hacked a bit to only
accept patches from git-send-email as a spam filtering method. What I
do is my patch scripts add a header:
X-Mailer: git-send-email haha only kidding
But because this was a resend, I didn't use my normal patch scripts and
just resent it from Mutt so it didn't have the header. Something for me
to remember for next time I guess.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH RESEND] mfd: wm831x-auxadc: Prevent use after free in wm831x_auxadc_read_irq()
Date: Thu, 4 Feb 2021 13:58:37 +0300 [thread overview]
Message-ID: <20210204105837.GI20820@kadam> (raw)
In-Reply-To: <20210204103724.GC2789116@dell>
On Thu, Feb 04, 2021 at 10:37:24AM +0000, Lee Jones wrote:
> On Fri, 29 Jan 2021, Dan Carpenter wrote:
>
> > The "req" struct is always added to the "wm831x->auxadc_pending" list,
> > but it's only removed from the list on the success path. If a failure
> > occurs then the "req" struct is freed but it's still on the list,
> > leading to a use after free.
> >
> > Fixes: 78bb3688ea18 ("mfd: Support multiple active WM831x AUXADC conversions")
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > ---
> > drivers/mfd/wm831x-auxadc.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Patchwork still can't find this.
>
> I've applied it manually, thanks.
Ah... You know what it is? I normally use Mutt instead of
git-send-email. Some of the patchworks have been hacked a bit to only
accept patches from git-send-email as a spam filtering method. What I
do is my patch scripts add a header:
X-Mailer: git-send-email haha only kidding
But because this was a resend, I didn't use my normal patch scripts and
just resent it from Mutt so it didn't have the header. Something for me
to remember for next time I guess.
regards,
dan carpenter
next prev parent reply other threads:[~2021-02-04 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129143724.GX20820@kadam>
2021-02-04 10:37 ` [PATCH RESEND] mfd: wm831x-auxadc: Prevent use after free in wm831x_auxadc_read_irq() Lee Jones
2021-02-04 10:37 ` Lee Jones
2021-02-04 10:58 ` Dan Carpenter [this message]
2021-02-04 10:58 ` Dan Carpenter
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=20210204105837.GI20820@kadam \
--to=dan.carpenter@oracle.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=sameo@linux.intel.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.