linux-kernel - Re: [git pull] habanalabs pull request for kernel 5.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFCwf12iMY18BSLj7Cu1Q0SQnCg+1d4hyCLoBe8oJrBv5=ByVQ@mail.gmail.com>
Date:   Sun, 22 May 2022 00:07:03 +0300
From:   Oded Gabbay <ogabbay@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] habanalabs pull request for kernel 5.19

On Sat, May 21, 2022 at 9:21 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Sat, May 21, 2022 at 05:53:52PM +0300, Oded Gabbay wrote:
> > On Sat, May 21, 2022 at 4:22 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> > >
> > > On Sat, May 21, 2022 at 02:53:25PM +0300, Oded Gabbay wrote:
> > > > Hi Greg,
> > > >
> > > > This is habanalabs pull request for the merge window of kernel 5.19.
> > > > We added a few minor features, such as support eventfd registration
> > > > for device events, and the ability to scrub the device memory
> > > > through debugfs.
> > > >
> > > > We did some refactoring such as adding a centralized memory
> > > > manager inside the driver for allocating mmapable memory and tracking
> > > > it, so we can remove different code paths that basically duplicated
> > > > that functionality.
> > > >
> > > > And, as usual, there are multiple bug fixes.
> > > >
> > > > Full details are in the tag.
> > > >
> > > > Thanks,
> > > > Oded
> > > >
> > > > The following changes since commit cafada1fe932ce761d6c0bc1d56967e27abe4cff:
> > > >
> > > >   Revert "speakup: Generate speakupmap.h automatically" (2022-05-20 21:07:05 +0200)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git tags/misc-habanalabs-next-2022-05-21
> > > >
> > > > for you to fetch changes up to 93f742b13260b070a695f44d6b6ff696cb5cbcd8:
> > > >
> > > >   habanalabs: use separate structure info for each error collect data (2022-05-21 14:42:17 +0300)
> > >
> > > Has this been in linux-next already?  It's _really_ late to be adding
> > > new commits to my trees as 5.17 is about to come out in a few hours :(
> > >
> > > greg k-h
> >
> > Yeah, sorry about that, I got to a computer only yesterday as my wife
> > and I had a new baby boy last week :)
>
> Congratulations!
>
> And totally understandable about the delay.
>
> > To your question, no, my branch isn't taken to linux-next. Our driver
> > commits are added to linux-next only through your -next.
>
> Ok, as these are only touching your driver, I'll take them.
>
> Oops, odd, I get this warning with my scripts:
> Commit: ad05bb784ca2 ("habanalabs: hl_ts_behavior can be static")
>         Fixes tag: Fixes: 079c2434d6e8 ("habanalabs: convert ts to use unified memory manager")
>         Has these problem(s):
>                 - Target SHA1 does not exist
>
> Where did you get that SHA1 from?
>
> Sorry, I can't take this as is, invalid sha1 shouldn't be in the tree.
>
> I can export these as patches and fix up the sha1 by hand, want me to do
> that?  I'll have some time on Monday.
>
> thanks,
>
> greg k-h

Yes, that will be a great help. I'm pretty occupied right now as you
probably imagine ;)

Thanks,
Oded