Tejun Heo wrote:
Hello,
Borislav Petkov wrote:
Honestly, I don't know. The code predates even the initial git
commit of the kernel so I guess nobody knows?
Heh.. maybe Mark does.
..
I may have known once -- I'm sure Gadi explained it to me,
but my memory doesn't have it any more.
Yet another problem is that idetape_flush_tape_buffers() uses pc which
is on stack which drive->pc ends up pointing directly to, so it won't
work. Nobody expects that the pointer it passed into an API should be
accessible by the API implementation after it was done with it.
That's just a silly thing to do.
The whole on stack passing should be passe :)
..
Nowadays, for sure.
But back then, the kernel was able to map all physical memory
at once, so lots of code did things that way. Over time, much of
it has been "fixed" to handle newer machines with tons of RAM.
I guess you've just found more of it to modernize. :)
Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
