From: butt3rflyh4ck <butterflyhuangxx@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, tiwai@suse.com,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org,
alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: A divide error bug in snd_pcm_write
Date: Thu, 29 Sep 2022 22:52:10 +0800 [thread overview]
Message-ID: <CAFcO6XNsqKCzNBiBF4eYyh+RCSGBp_5HSzxF0gw0kgfQ2FDAiQ@mail.gmail.com> (raw)
In-Reply-To: <87leq6gglm.wl-tiwai@suse.de>
This one fixes the problem.
https://lore.kernel.org/all/20220926135558.26580-2-tiwai@suse.de/
Regards,
butt3rflyh4ck.
On Tue, Sep 27, 2022 at 2:01 AM Takashi Iwai <tiwai@suse.de> wrote:
>
> On Mon, 26 Sep 2022 19:16:48 +0200,
> butt3rflyh4ck wrote:
> >
> > The latest kernel upstream.
> > Yes, but using mmap, you can map the runtime->status page, and then
> > copy the data through memcpy to overwrite the status->state data, or
> > even more, which is incredible.
>
> Ah, then that's exactly the case my latest patch set covers.
> Either the first patch or the second patch alone should work.
> https://lore.kernel.org/r/20220926135558.26580-2-tiwai@suse.de
> https://lore.kernel.org/r/20220926135558.26580-3-tiwai@suse.de
>
> Could you verify either of them fixes the problem?
>
>
> thanks,
>
> Takashi
--
Active Defense Lab of Venustech
WARNING: multiple messages have this Message-ID (diff)
From: butt3rflyh4ck <butterflyhuangxx@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
broonie@kernel.org
Subject: Re: A divide error bug in snd_pcm_write
Date: Thu, 29 Sep 2022 22:52:10 +0800 [thread overview]
Message-ID: <CAFcO6XNsqKCzNBiBF4eYyh+RCSGBp_5HSzxF0gw0kgfQ2FDAiQ@mail.gmail.com> (raw)
In-Reply-To: <87leq6gglm.wl-tiwai@suse.de>
This one fixes the problem.
https://lore.kernel.org/all/20220926135558.26580-2-tiwai@suse.de/
Regards,
butt3rflyh4ck.
On Tue, Sep 27, 2022 at 2:01 AM Takashi Iwai <tiwai@suse.de> wrote:
>
> On Mon, 26 Sep 2022 19:16:48 +0200,
> butt3rflyh4ck wrote:
> >
> > The latest kernel upstream.
> > Yes, but using mmap, you can map the runtime->status page, and then
> > copy the data through memcpy to overwrite the status->state data, or
> > even more, which is incredible.
>
> Ah, then that's exactly the case my latest patch set covers.
> Either the first patch or the second patch alone should work.
> https://lore.kernel.org/r/20220926135558.26580-2-tiwai@suse.de
> https://lore.kernel.org/r/20220926135558.26580-3-tiwai@suse.de
>
> Could you verify either of them fixes the problem?
>
>
> thanks,
>
> Takashi
--
Active Defense Lab of Venustech
next prev parent reply other threads:[~2022-09-29 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 9:26 A divide error bug in snd_pcm_write butt3rflyh4ck
2022-09-26 10:21 ` Takashi Iwai
2022-09-26 10:21 ` Takashi Iwai
2022-09-26 17:16 ` butt3rflyh4ck
2022-09-26 17:16 ` butt3rflyh4ck
2022-09-26 18:01 ` Takashi Iwai
2022-09-26 18:01 ` Takashi Iwai
2022-09-29 14:52 ` butt3rflyh4ck [this message]
2022-09-29 14:52 ` butt3rflyh4ck
2022-09-29 16:14 ` Takashi Iwai
2022-09-29 16:14 ` Takashi Iwai
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=CAFcO6XNsqKCzNBiBF4eYyh+RCSGBp_5HSzxF0gw0kgfQ2FDAiQ@mail.gmail.com \
--to=butterflyhuangxx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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.