linux-kernel - Re: [char-misc-next V2] mei: drop the warning when cl is not initialized during unlinking

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:	Mon, 14 Jan 2013 16:34:58 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tomas Winkler <tomas.winkler@...el.com>, arnd@...db.de,
	alan@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next V2] mei: drop the warning when cl is not
 initialized during unlinking

On Mon, Jan 14, 2013 at 4:12 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Mon, Jan 14, 2013 at 03:55:44PM +0100, Sedat Dilek wrote:
>> On Mon, Jan 14, 2013 at 3:32 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>> > On Mon, Jan 14, 2013 at 03:14:50PM +0100, Sedat Dilek wrote:
>> >> On Thu, Jan 10, 2013 at 4:32 PM, Tomas Winkler <tomas.winkler@...el.com> wrote:
>> >>
>> >> Can you please apply this patch to char-misc-next?
>> >> I am hitting it again while doing other regression testing!
>> >
>> > Please be patient, it will get there soon.
>> >
>>
>> The same answer I got for the report/testing of [1], it is still not
>> in mainline.
>> Yes, I have seen your pull-request for char-misc-linus of today, but
>> why does this takes weeks to apply?
>
> "Weeks"?  You do realize this was sent to me over a holliday break, one
> in which I was on vacation?  I only returned a week ago, to over 1500
> patches to sift through and process.
>
> And, I did that within 4 days, and sent the needed fix off to Linus
> within 7 days of returning.
>
> If you think you can do better than that, wonderful, I would love for
> you to start out reviewing code and helping with handling stuff like
> that.  Please do so before complaining about anything.
>

The MAINTAINERS file lists a co-maintainer. Not sure what his job is.
In every company when people are on holidays, the work continues.

Speaking in general... regression fixes (freezing my machine on reboot
is one!) should be treat differently - faster!

I am testing GIT tree's before they enter mainline or Linux-Next.
And I am doing this in my free-time - I am not paid for it.
In a scrum talk the speaker called that (time) "units" (of work
especially in OSS projects)... "lost of free-time".
Maybe, I should look for a different hobby and wait til -rc4 is
released to be on the safe side of life.

In another email I was reflecting on a "arbritration board".
Good Mr. Torvalds said in an interview "I don't read code anymore"...
but what was with these fs/blkdev changes late in 3.7 cycle :-)?
There seems to be no rules except yours.
Right, you have the reponsibilty.

The last week I played with Linux Test Project and I still do NOT know
how to (really) test my kernels!
In each kernel-release (even rc) we read "please test" - but how?
Noone tells you this.
( A different story... )

Just some thoughts... for free.

- Sedat -

> greg k-h
--
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/