[lkml]   [2018]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG] ext4/block null pointer crashes in linux-next
On Mon, Oct 15, 2018 at 07:28:48PM -0400, wrote:
> Traceback of the rm crash (I have *no* idea why it has systemd-tmpfile as Comm:
> as none of the tmpfile config reference /usr/src at all, and the config says it
> shouldn't have been running at the time of the crash, and I can't replicate as
> the directory is now empty...)

Given the commit that it bisected down to, I very much doubt it has
anything to do with a specific directory or pathname. Either you or
your distribution has enabled blk cgroup for I/O throttling, and
there's some race that you're tripping across. What ext4 file or
directory happens to be accessed when you trip across the problem is
probably just pure luck.

If you can disable the block I/O throttling configuration (which may
very well be distro-specific), the problem will probably go away. I
don't use blkcg at all, personally, and on a personal laptop
(especially if you have an SSD), I really don't see the point.

Still, I'm sure the people who *do* use blkcg for real (mostly in data
centers, in my experience) will probably thank you for being a great
guinea pig. :-)

- Ted

 \ /
  Last update: 2018-10-16 03:52    [W:0.053 / U:15.072 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site