linux-kernel - Re: [PATCH v3 0/2] Fix subject line

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] [day] [month] [year] [list]

Message-ID: <1403051413.4155.12.camel@buesod1.americas.hpqcorp.net>
Date:	Tue, 17 Jun 2014 17:30:13 -0700
From:	Davidlohr Bueso <davidlohr@...com>
To:	Wahib <wahibfaizi@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Valentina Manea <valentina.manea.m@...il.com>,
	linux-usb@...r.kernel.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] Fix subject line

On Mon, 2014-06-16 at 00:28 +0400, Wahib wrote:
> Hi Davidlohr!
> 
> Don't worry. I am not discouraged. :)
> 
> I understand your concern that the patch feels superficial. It's what the task
> asked us to do. I suspect the author(s) of the Eudyptula Challenge designed
> this task to get us involved with the Linux kernel community.

If you feel you actually learn something by doing the Eudyptula
Challenge, then good for you, and by all means continue doing so. As I
mentioned, I know almost zero about it, but can say for sure that
cleanups alone won't get you very far in the community and you will
probably get bored sooner or later -- which is unfortunate as kernel
hacking fascinating.

> 
> I have been looking for a bug in 'usbip' to bundle with my patch. The only bug
> that I could find (as of 16-Jun-2014) on bugzilla.kernel.org related
> to 'usbip' is Bug 77191.
> 
> Bug 77191 - ftdi-sio (usbserial) over usbip hung after disconnect while in use
> (https://bugzilla.kernel.org/show_bug.cgi?id=77191)
> 
> Sadly the bug doesn't seem to be newbie friendly as it requires special setup
> to reproduce and requires the developer to know about the intricacies of the
> 'usbip' subsystem. I understand that people commiting their specialized
> knowledge is how the kernel development actually works. But USB is not my
> speciality (yet).
> 
> Could you point me to more beginner friendly bugs which aren't superficial code
> cleanups?

There are plenty of bugs out there, and not so hard to find -- just push
some module/filesystem/subsystem/testcase hard enough to make it do
things it shouldn't. Run linux-next on trinity and fix/report the bugs,
etc.

imho testing and reading other people's patches is perhaps the best way
to do useful things, get acquainted with the code and get experience
with lkml and the process behind kernel development.

> Can I bundle fixes to subsystems other than 'usbip' with the code cleanup patch
> for 'usbip'?

Probably not, unless it's a tree-wide change.

Hope this helps,
Davidlohr

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