On Sat, Jan 29, 2022 at 09:19:18AM -0600, Kangjie Lu wrote:
> > So to be explicit, so you do not misunderstand me somehow:
> >
> > No more patches from umn.edu should be accepted into the Linux
> > kernel until further public notice.
>
> This is clear to me.
>
> > They should be c
On Sat, Jan 29, 2022 at 08:18:55AM -0600, Kangjie Lu wrote:
> On Fri, Jan 28, 2022 at 1:58 PM Karol Herbst wrote:
> >
> > On Fri, Jan 28, 2022 at 8:54 PM Alex Deucher wrote:
> > >
> > > On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> > > >
> > > > Sigh-thank you for catching this - I had tot
On Fri, Jan 28, 2022 at 02:57:36PM -0500, Lyude Paul wrote:
> On Fri, 2022-01-28 at 14:53 -0500, Alex Deucher wrote:
> > On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> > >
> > > Sigh-thank you for catching this - I had totally forgot about the umn.edu
> > > ban.
> > > I pushed this already b
On Fri, Jan 28, 2022 at 02:20:24PM -0500, Lyude Paul wrote:
> Sigh-thank you for catching this - I had totally forgot about the umn.edu ban.
> I pushed this already but I will go ahead and send a revert for this patch.
No worries, thanks for doing this.
greg k-h
On Fri, Jan 28, 2022 at 08:57:56PM +0100, Karol Herbst wrote:
> On Fri, Jan 28, 2022 at 8:54 PM Alex Deucher wrote:
> >
> > On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> > >
> > > Sigh-thank you for catching this - I had totally forgot about the umn.edu
> > > ban.
> > > I pushed this alrea
On Fri, Jan 28, 2022 at 2:58 PM Karol Herbst wrote:
>
> On Fri, Jan 28, 2022 at 8:54 PM Alex Deucher wrote:
> >
> > On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> > >
> > > Sigh-thank you for catching this - I had totally forgot about the umn.edu
> > > ban.
> > > I pushed this already but
On Fri, Jan 28, 2022 at 8:54 PM Alex Deucher wrote:
>
> On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> >
> > Sigh-thank you for catching this - I had totally forgot about the umn.edu
> > ban.
> > I pushed this already but I will go ahead and send a revert for this patch.
> > Will cc you on
On Fri, 2022-01-28 at 14:53 -0500, Alex Deucher wrote:
> On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
> >
> > Sigh-thank you for catching this - I had totally forgot about the umn.edu
> > ban.
> > I pushed this already but I will go ahead and send a revert for this
> > patch.
> > Will cc you
On Fri, Jan 28, 2022 at 2:20 PM Lyude Paul wrote:
>
> Sigh-thank you for catching this - I had totally forgot about the umn.edu ban.
> I pushed this already but I will go ahead and send a revert for this patch.
> Will cc you on it as well.
This seems short-sighted. If the patch is valid I see no
Sigh-thank you for catching this - I had totally forgot about the umn.edu ban.
I pushed this already but I will go ahead and send a revert for this patch.
Will cc you on it as well.
On Fri, 2022-01-28 at 11:18 +0100, Greg KH wrote:
> On Tue, Jan 25, 2022 at 12:58:55AM +0800, Zhou Qingyang wrote:
>
On Tue, Jan 25, 2022 at 12:58:55AM +0800, Zhou Qingyang wrote:
> In nvkm_acr_hsfw_load_bl(), the return value of kmalloc() is directly
> passed to memcpy(), which could lead to undefined behavior on failure
> of kmalloc().
>
> Fix this bug by using kmemdup() instead of kmalloc()+memcpy().
>
> Thi
Reviewed-by: Lyude Paul
On Tue, 2022-01-25 at 00:58 +0800, Zhou Qingyang wrote:
> In nvkm_acr_hsfw_load_bl(), the return value of kmalloc() is directly
> passed to memcpy(), which could lead to undefined behavior on failure
> of kmalloc().
>
> Fix this bug by using kmemdup() instead of kmalloc()
12 matches
Mail list logo
