From: "欧阳炜钊(Weizhao Ouyang)" <ouyangweizhao@zeku.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "王大宇(John Wang)" <wangdayu@zeku.com>,
"Sergey Shtylyov" <s.shtylyov@omp.ru>,
"马宏伟(Matthew Ma)" <mahongwei@zeku.com>,
"Pierre Ossman" <drzeus@drzeus.cx>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] mmc: sdio: fix kernel panic when remove non-standard SDIO card
Date: Fri, 14 Oct 2022 02:39:02 +0000 [thread overview]
Message-ID: <4d2f9cf9f9c248a1bb18ce7e86f349d5@zeku.com> (raw)
In-Reply-To: <CAPDyKFpfm2i2u3BKCxFEA=qZ8GiOOryhHYKNt_yyMA51sxSLJw@mail.gmail.com>
Wednesday, October 12, 2022 6:09 PM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>
> On Wed, 12 Oct 2022 at 03:50, 欧阳炜钊(Weizhao Ouyang)
> <ouyangweizhao@zeku.com> wrote:
> >
> > 2022年10月11日 22:41, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> > >
> > > On Tue, 27 Sept 2022 at 04:04, Weizhao Ouyang
> <ouyangweizhao@zeku.com>
> > > wrote:
> > > >
> > > > From: Matthew Ma <mahongwei@zeku.com>
> > > >
> > > > SDIO tuple is only allocated for standard SDIO card, especially it
> > > > causes memory corruption issues when the non-standard SDIO card has
> > > > removed since the card device's reference counter does not increase for
> > > > it at sdio_init_func(), but all SDIO card device reference counter has
> > > > decreased at sdio_release_func().
> > > >
> > > > Fixes: 1a632f8cdc33 ("sdio: split up common and function CIS parsing")
> > > > Signed-off-by: Matthew Ma <mahongwei@zeku.com>
> > > > Reviewed-by: Weizhao Ouyang <ouyangweizhao@zeku.com>
> > > > Reviewed-by: John Wang <wangdayu@zeku.com>
> > >
> > > Apologize for the delay!
> > >
> > > Wow, that's a very old bug you fixed! However, it looks like the fixed
> > > commit should be changed to 6f51be3d37df ("sdio: allow non-standard
> > > SDIO cards").
> >
> > Thanks, I messed the tag.
> >
> > >
> > > I tried to apply the patch, but the patch format seems to be corrupt.
> > > Did you use git format-patch and did run ./scripts/checkpatch.pl on
> > > it?
> > >
> >
> > Yeah I used checkpatch.pl with strict mode to check this patch, and it
> > has no obvious style problems. What's the format error you got?
>
> ERROR: patch seems to be corrupt (line wrapped?)
> #130: FILE: drivers/mmc/core/sdio_bus.c:291:
> struct sdio_func *func = dev_to_sdio_func(dev);
>
> total: 1 errors, 0 warnings, 9 lines checked
>
Sorry our email hosting service made some issue on formatting, I will
send an updated patch ASAP.
Thanks,
Weizhao
next prev parent reply other threads:[~2022-10-14 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 1:50 [PATCH] mmc: sdio: fix kernel panic when remove non-standard SDIO card 欧阳炜钊(Weizhao Ouyang)
2022-10-12 10:09 ` Ulf Hansson
2022-10-14 2:39 ` 欧阳炜钊(Weizhao Ouyang) [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-14 2:22 欧阳炜钊(Weizhao Ouyang)
2022-09-27 2:01 Weizhao Ouyang
2022-10-11 14:40 ` Ulf Hansson
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=4d2f9cf9f9c248a1bb18ce7e86f349d5@zeku.com \
--to=ouyangweizhao@zeku.com \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mahongwei@zeku.com \
--cc=s.shtylyov@omp.ru \
--cc=ulf.hansson@linaro.org \
--cc=wangdayu@zeku.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