[#LU-432] Add support for Fedora14 kernel 2.6.35.13-92.fc14 (1.8.x patchless client)

[LU-432] Add support for Fedora14 kernel 2.6.35.13-92.fc14 (1.8.x patchless client) Created: 18/Jun/11 Updated: 22/Feb/12 Resolved: 25/Oct/11
Status:	Resolved
Project:	Lustre
Component/s:	None
Affects Version/s:	Lustre 1.8.6
Fix Version/s:	None

Type:

Improvement

Priority:

Minor

Reporter:

Christos Triantafyllidis

Assignee:

Yang Sheng

Resolution:

Fixed

Votes:

Labels:

None

Rank (Obsolete):

4976

Comments

Comment by Peter Jones [ 18/Jun/11 ]

Hi Christos

Thanks for your interest in Lustre and your willingness to contribute to its developement. I saw your discussion about this work with Whamcloud's Andreas Dilger and would further add to his comments that you should review the instructions at http://wiki.whamcloud.com/display/PUB/Submitting+Changes about the logisitcs of contributing code to Lustre. Furthermore, it would be easiest to get your work quickly landed if it was baselined on the master branch rather than 1.8.x. The master branch is the basis for the upcoming Lustre 2.1 release and all future Lustre releases.

Regards

Peter

Comment by Christos Triantafyllidis [ 19/Jun/11 ]

Hi Peter,
i totally understand your concern on using the master branch instead of the 1.8.x but the problem here is that our deployment is still on 1.8.4 thus i don't have the needed testing infrastructure for the master branch.

I'm not sure if building a patchless client based on master branch would work fluently with our old (1.8.4) servers. This is something that i'm willing to test on a later phase.

Anyway we are planning to update our infrastructure, hopefully in this summer, thus i'll anyway have to migrate these patches to the master branch unless someone else already have done them (as they are not fedora specific but kernel 2.6.35 specific).

Regards,
Christos

PS: I'm cleaning up my patch and splitting it to small commits to ease the landing procedure. I'll push them for review hopefully tonight.

Comment by Peter Jones [ 19/Jun/11 ]

Christos

I do understand your situation. I'm afraid that running 2.x clients with 1.8.x servers is not supported, so I am afraid that your suggestion is not an option. Running old servers with new clients is usually supported between subsequent versions but as this is a major version change this is not the case. If you contribute the work against 1.8.x then an engineer can always port this work to master for landing. This should give you the feedback that you need, even if we choose not to land the patches for 1.8.x. Smaller patches definitely make things easier.

Regards

Peter

Comment by Christos Triantafyllidis [ 20/Jun/11 ]

Hi,
it looks that all my patches but the last compiled fine at jekins [1]. I'm not sure what is the problem with the last as the change is totally trivial (adding -lpthread at compilation of a test) but for sure this is not critical for the 2.6.35 kernel support (at least i'm happy without it).

I'm not sure how i should proceed now. Do i have to do something more or is it up to you now?

Regards,
Christos

[1] http://review.whamcloud.com/#change,978

Comment by Peter Jones [ 20/Jun/11 ]

Yang Sheng

Can you please review these patch contributions and see about porting them to land for master

Thanks

Peter

Comment by Andreas Dilger [ 22/Jun/11 ]

Christos, thanks for submitting the patches.

Sorry to be picky about the changes, but the kernel compat checks need to be kept "clean" since the changes to the kernel API change so frequently this code would otherwise just get increasingly more difficult to maintain.

Please also submit similar patches for the "master" (2.x) branch.

Comment by Yang Sheng [ 22/Jun/11 ]

master patch： http://review.whamcloud.com/#change,994