linux-kernel - Re: Linux 3.0.24

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, 15 Mar 2012 13:28:28 -0400
From:	Chris Frey <cdfrey@...rsquare.net>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Jonathan Nieder <jrnieder@...il.com>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: Linux 3.0.24

On Thu, Mar 15, 2012 at 09:58:12AM -0700, Greg KH wrote:
> On Thu, Mar 15, 2012 at 12:51:08PM -0400, Chris Frey wrote:
> > Perhaps it would help if I phrased my question differently: What kind of
> > bug makes you decide to write "must" instead of something else?
> 
> This has been discussed endlessly in the past, please see the lkml
> archives for details if you are interested.  It all comes down to the
> issue, how do you classify a bug fix as a specific "kind"[1]?
> 
> Is there some reason you don't trust me in my usage of the word "must"
> here?  If so, then please feel free to go through all of the individual
> patches, which I post, and make the judgement call for yourself.
> 
> [1] Hint, for the most part, you can't.

It's not a matter of trust, but of understanding.  If, according to your
footnote, you do not classify bugs at all (except maybe compile issues,
as Jonathan mentioned), then "must" merely implies that "a bug was fixed."

But had you classified bugs, then it would be useful to know what
criteria you had used.  And if so, it would make sense that such criteria
would be documented somewhere.

I had assumed the latter case, but it seems that the former is more accurate.

Thanks, both to you and Jonathan for clarifying my misunderstanding.

- Chris

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