Best way to contribute bunch of miscellaneous fixes?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,


Over last few weeks I was working on making Ceph 15.2.4 to build and run on ARM 32 bit system. It appears that Ceph no longer supports 32 bit systems. But I wanted to run it on Odroid HC-2 which makes a very good cheap OSD basically turning SATA disk into ethernet enabled disk. So I stuck my teeth into getting current Ceph up and running on 32 bit architecture. While doing so I have encountered number of bugs in Ceph codebase which I now want to put back for everyone to use.

For example I found a bug in EC code which attempts to malloc around 4GB - this bug is not noticeable on 64 bit systems as malloc happily allocates 4GB but it of course failed on 32 bit system and digging into the issue shown that this malloc was just a bug - it should not be happening at all in the first place.

Or wrong include (.cc instead of .h) which caused compilation hard error. Or python threading timeout was specified as int while it should be a float and basically timeout was not happening. And so on. Small inaccuracies peppered around code base. It is certainly should not be done as one huge patch and I am happy to put these patches one by one. But which way it should be done? As number of PR requests on github? Or patch files emailed to someone?

May someone from the list enlighten me on acceptable procedure I need to follow?


Regards,

Vladimir
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx



[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux