[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190916103351.GA14308@infradead.org>
Date: Mon, 16 Sep 2019 03:33:51 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: "Ahmed S. Darwish" <darwish.07@...il.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jan Kara <jack@...e.cz>, zhangjs <zachary@...shancloud.com>,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Linux 5.3-rc8
On Tue, Sep 10, 2019 at 07:56:35AM -0400, Theodore Y. Ts'o wrote:
> Hmm, I'm not seeing this on a Dell XPS 13 (model 9380) using a Debian
> Bullseye (Testing) running a rc4+ kernel.
>
> This could be because Debian is simply doing more I/O; or it could be
> because I don't have some package installed which is trying to reading
> from /dev/random or calling getrandom(2). Previously, Fedora ran into
> blocking issues because of some FIPS compliance patches to some
> userspace daemons. So it's going to be very user space dependent and
> package dependent.
Btw, I've been seeing this issue on debian testing with an XFS root
file system ever since the blocking random changes went in. There
are a few reports (not from me) in the BTS since. I ended up just
giving up on gdm and using lightdm instead as it was clearly related
to that.
Powered by blists - more mailing lists