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]
Date:	Thu, 4 Jun 2015 09:38:07 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Helge Deller <deller@....de>
Cc:	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] compat: fix possible out-of-bound accesses in
 compat_get_bitmap() and compat_put_bitmap()

On Thu, Jun 4, 2015 at 6:45 AM, Helge Deller <deller@....de> wrote:
>
> Do you want me to send it again cleaned up, or will you just take yours?

I'd prefer to get a re-send, I've already nuked the patch from me tree.

These days, 99% of the patches I write are throw-away stuff just for
this kind of "how about this" email exchange.

I do it that way partly because I'm lazy (ok, _mostly_ because I'm
lazy, except then the explanation emails like this are actually more
work than just doing it myself - but I tell myself that it makes it
easier for me be lazy in the long run ;^). But partly it's because it
makes it more natural to credit the person who actually reported the
issue (the patch itself is *much* less important than the fact that
somebody noticed the problem in the first place), and also partly
because sometimes the patches may need some extra tender care and
loving ("Oh, the patch I sent out didn't actually compile, and it
burnt down your house? Yeah, it was just a general 'wouldn't this way
be nicer' thing, not a serious patch").

                     Linus
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ