I've read some kernel code recently, and I want to see how it actually works. I
found a lot of articles about how to debug kernel with qemu, but all i found
are about setting a breakpoint at start_kernel, so i wonder if there's way i
can debug before start_kernel, those setup code and decompress
Hi,
Valdis Klētnieks wrote:
> The tricky part is, of course, that for this to work correctly, you need
> to have 64-bit timestamps in the on-disk format.
Initially yes. In
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627
i sketched what it thought was needed to do.
But by the much more
On Fri, 03 Sep 2021 13:00:55 +0200, "Thomas Schmitt" said:
> I could offer bugs of isofs with explanations and patch proposals:
>
> - isofs: prevent file time rollover after year 2038
> Change the return type of function iso_date() from int to time64_t.
The tricky part is, of course, that for t
>Your best source for low-hanging fruit these days is probably drivers/staging,
> as pretty much everything under there is *known* to be less-than-optimal.
Thanks for the reply. The reason I looked for some bugs is that I’m not really
interested in driver development and digging into details
Hi,
Adverg Ebashinskii wrote:
> The reason I looked for some bugs is that I’m not
> really interested in driver development and digging into details of a
> specific hardware. So I tried to get into some core subsystems like fs, net,
> cgroups, etc...
I could offer bugs of isofs with explanations
