Bug#682007: NULL pointer dereference in __fscache_read_or_alloc_pages
Brian Kroth wrote:
> Sorry, the labs went into their dormant period and all of my test cases ran
> away for the rest of the summer (the find cmd didn't seem to trigger the
> __fscache problem), so I hadn't moved any further on this.
>
> Now that they're back, I'm definitely seeing it again (about 20 different
> machines in two days last week), so I've started the process of hunting down
> a trigger cause again. I'll let you know if I find something.
Thanks for the update.
The human test cases can work fine for vetting a fix. I'd also be
interested to hear whether the series I sent was completely borked, so
I'd recommend trying on a test machine for a day or two before putting
such a patched kernel into production, though.
Jonathan
Reply to: