Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CANX2M5Zw_zW6ez0_wvaXL1pbLnR2jWY=T7MgkT=4a-zNkiwVig@mail.gmail.com>
 <YtuceCr5OCJcDatJ@kroah.com> <874jz82kx0.wl-tiwai@suse.de>
 <CANX2M5Ywm+GpYY3+GsOWCLH24Nhy0M0LjBE-pHC8wFcd7SO=wQ@mail.gmail.com> <87tu73p1o2.wl-tiwai@suse.de>
In-Reply-To: <87tu73p1o2.wl-tiwai@suse.de>
From:   Dipanjan Das <mail.dipanjan.das@gmail.com>
Date:   Thu, 28 Jul 2022 16:24:12 -0700
Message-ID: <CANX2M5abRrSADvd3x_rm+TrA2ziu71VL6X3=v_Cft4LtaB=6Eg@mail.gmail.com>
Subject: Re: KASAN: vmalloc-out-of-bounds Write in snd_pcm_hw_params
To:     Takashi Iwai <tiwai@suse.de>
Cc:     Greg KH <gregkh@linuxfoundation.org>, perex@perex.cz,
        tiwai@suse.com, consult.awy@gmail.com, alsa-devel@alsa-project.org,
        linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
        fleischermarius@googlemail.com, its.priyanka.bose@gmail.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jul 26, 2022 at 10:25 PM Takashi Iwai <tiwai@suse.de> wrote:
>
> Thanks for the analysis.  A good news is that, at least for the
> vmalloc() case, it's a kind of false-positive; vmalloc() always takes
> the full pages, so practically seen, the size is page-aligned.  It's
> fooling the memory checker, though.
>
> But the similar problem could be seen with genalloc calls, and this
> was fixed by the upstream commit
> 5c1733e33c888a3cb7f576564d8ad543d5ad4a9e
>     ALSA: memalloc: Align buffer allocations in page size
>
> I suppose you can simply backport this commit to 5.10.y.  Could you
> confirm that this fixes your problem?

We confirm that the patch you proposed fixes the problem (blocks the
reproducer). How do we proceed with getting the issue fixed? Do we
send a patch according to the steps detailed here:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html?

-- 
Thanks and Regards,

Dipanjan