linux-kernel - Re: [PATCH] staging: slicoss: fix use-after-free in slic_entry

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: <CANoiuG+5qYQkgmzPXoCTMY9C5Z3P0_K-rXHjN3k50CJhv+E5Qw@mail.gmail.com>
Date:	Fri, 23 May 2014 13:07:55 -0700
From:	David Matlack <matlackdavid@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	devel@...verdev.osuosl.org, charrer@...critech.com,
	linux-kernel@...r.kernel.org, Lior Dotan <liodot@...il.com>
Subject: Re: [PATCH] staging: slicoss: fix use-after-free in slic_entry_probe

On Fri, May 23, 2014 at 4:14 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> I think I've already applied all of these, if not, please let me know.
>
> Also, you forgot to number these patches to let me know what order to
> apply them in :(
>
> thanks,
>
> greg k-h

Thanks Greg. Sorry for the confusion. I resent these patches without numbers
because in retrospect, they were all independent changes and could be applied
in any order. In retro-retrospect, that probably just piled onto the confusion
:)

Looking at the emails I got from you about staging-next, _almost_ all the
patches were applied. I reply to the ones directly that were dropped.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/