0
I Use This!
Activity Not Available

Commits : Listings

Analyzed 4 months ago. based on code collected 4 months ago.
Jul 20, 2025 — Jul 20, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
kern.log for working virgo_malloc, virgo_set and virgo_get via telnet command path. More... about 13 years ago
Updated autogenerated driver kernel object files and build generated source files More... about 13 years ago
For virgo_cloud_get(), a prefix "virgodata:" is added which is removed through an strncmp() and if clause in virgo_cloudexec_mempool.ko driver. With this virgo_malloc, virgo_set and virgo_get work and today's kern.log has been added in test_logs/ More... about 13 years ago
*)To differentiate address from data a special prefix virgodata: is prepended to data retrieved This will be removed by virgo_cloudexec_send_to() module op and only data will be sent to client. Similar prefix can also be done for address but for the timebeing one prefix is enough to distinguish address and data. More... about 13 years ago
Updated VIRGO Design Document More... about 13 years ago
Updated VIRGO Design Document More... about 13 years ago
extern declaration for exported function toKernelAddress() in module virgo_cloud_mempool_kernelspace.ko More... about 13 years ago
kern.log for telnet path test of virgo_malloc and virgo_set after fixing the address scan error with new function virgo_parse_integer() carried over from lib/kstrtox.c and locally modified to add an if clause for quote and unquote. More... about 13 years ago
Updated autogenerated source files and build generated driver kernel object files More... about 13 years ago
Updated autogenerated source files and driver kernel object files More... about 13 years ago
Some cleanup More... about 13 years ago
Added more include paths More... about 13 years ago
1.Added more #includes kstrtox.h and ctype.h. 2.After a failed effort to make simple_strtoll() and kstrtoll() work without address scan errors, carried over _parse_integer() from lib/kstrtox.c which underlies all strtoxxx() functions and modified for VIRGO by adding an additional if clause for quote and unquote as below. Probably this missing clause could be causing the kstrtoll() and simple_strtoll() which use _parse_integer() in lib/kstrtox.c internally to randomly return junk addresses. But the simple_strtoll() works well in virgo_malloc client without the above special clause for quotes. With this new function virgo_cloud_set command correctly sets the address (kern.log for this has been added to repository with date 6November2013 appended. 3.Added a function printBytes() to print contents of the char* strings. 4.toKernelAddress() has been made inline. 5.More printk()s added. More... about 13 years ago
Build generated source and object files for virgo_cloudexec_mempool and virgo_cloud_mempool_kernelspace drivers. More... about 13 years ago
Hardcoded string literals in toKernelAdress() which get parsed correctly though function argument doesnot get parsed. All GFP_ATOMIC have been changed to GFP_KERNEL for kmalloc()s Argument to toKernelAddress() has been changed to const char*. More... about 13 years ago
All GFP_ATOMIC kmalloc(s) have been made into GFP_KERNEL allocations. More... about 13 years ago
Kern.log(s) with hardcoded address strings in toKernelAddress() of virgo_cloud_mempool_kernelspace.c that get parsed correctly with simple_strtoul() and kstrtoul() but something weird happens when the function argument is parsed and some junk address is parsed. So there is no problem with simple_strtoul() and kstrtoul(). More... about 13 years ago
Updated VIRGO Design Document More... about 13 years ago
kern.log with working virgo_malloc and virgo_set, but kstrtoul, with kstrdup embedded returns wrong address. Other permutations of kstrdup done separately etc., causes kernel panic. This unpredictable behaviour could be either in kstrtoul() or this is similar to earlier problems of inconsistent kernel blocking sockets caused by external cybercrime issues including a deliberately injected microcode update or kernel bug that happened few months ago. Same kstrtoul() code correctly parses in module_init of virgo_cloud_mempool_kernelspace.c which makes this quite obviously suspicious as to why the problem happens only in toKernelAddress(). More... about 13 years ago
Laptop screenshot of a working telnet to virgo_mempool_driver for virgo_malloc and virgo_set. More... about 13 years ago
two kern.log excerpts for working virgo_malloc and virgo_set that sets a data in remote cloud node. But there seems to be something different in kstrtoul() parsing in second kern.log. More... about 13 years ago
Some changes made to printk() and kstrtoul() invocation and simplified toKernelAddress(). A test kstrtoul() is added to module_init for debugging. More... about 13 years ago
kern.log for virgo_cloud_set() test in telnet path. More... about 13 years ago
kern.log for virgo_cloud_set() telnet path More... about 13 years ago
kern.log for virgo_cloud_set() test through telnet path which works. More... about 13 years ago
Updated build generated files and .ko files More... about 13 years ago
Updated simple_strtoll() to simple_strtoul() due to kernel panic and both didn't work. As kernel source mentions these to be obsolete, replaced it with kstrtoul() for scanning the address from string. But after kstrtoul(), the virgo_cloud_set address, though parsed, shows wrong value of 0x0000000b always. Kernel logs under test_logs/ More... about 13 years ago
Updated Makefile for building intptrtest.c More... about 13 years ago
Updated test_virgo_malloc testcase with unsigned long and long instead of long long return type. More... about 13 years ago
Updated intptr testcase for miscellaneous cast usecases. More... about 13 years ago