[OpenAFS-devel] Suggestions for contributing further to the cmd subsystem

[Michael Meffie]

On Mon, 16 Mar 2026 22:58:49 +0530
Archana S <archanagowdaa005@gmail.com> wrote:

> Hello everyone,
> 
> My name is Archana and I recently started contributing to OpenAFS. Over the
> past few weeks I have been working on a few small patches in the cmd
> subsystem and submitting them through Gerrit while learning more about the
> codebase and development workflow.
> 
> While reading through the cmd code, I became particularly interested in how
> the command parsing and error handling logic works. I would really like to
> continue contributing in this area and understand it more deeply.
> 
> If there are any parts of the cmd subsystem that could benefit from
> improvements such as validation, testing, usability improvements, or
> general cleanup, I would really appreciate any suggestions on issues or
> areas that would be useful to work on.
> 
> I am also planning to continue contributing as I prepare for GSoC, so any
> guidance on meaningful areas to explore would be very helpful.
> 
> Thank you for your time.

Hello Archana,

Apologies for the tardy reply.  The cmd library is quite idiosyncratic, and we
need to be very careful when making any changes to it, since we do not wish to
break any existing users.  That said, two things come to mind.

1. We do already have a TAP unit test for the libcmd. Tests can always be improved and
   more test cases are always appreciated.

2. One annoyance I have with libcmd is it allocates a small amount of memory which is
   not freed before the process exits. This is not problem in practice, since it the
   OS will reclaim the memory on process exit, and it is a small, fixed amount of memory.
   However, this generates a "false" alarm when running tools with valgrind to find memory
   leaks.  I haven't thought about the best way to deal with that yet, but that's an issue
   I thought I could share.

Thanks,
Mike


> Best regards
> Archana S


-- 
Michael Meffie <mmeffie@sinenomine.net>