Re: disk revalidation updates and OOM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jan Kara <jack@xxxxxxx>
Subject: Re: disk revalidation updates and OOM
From: Christoph Hellwig <hch@xxxxxx>
Date: Sat, 7 Mar 2020 15:29:50 +0100
Cc: He Zhe <zhe.he@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, viro@xxxxxxxxxxxxxxxxxx, bvanassche@xxxxxxx, keith.busch@xxxxxxxxx, tglx@xxxxxxxxxxxxx, mwilck@xxxxxxxx, yuyufen@xxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20200304162625.GA11616@lst.de>
References: <93b395e6-5c3f-0157-9572-af0f9094dbd7@windriver.com> <20200304133738.GF21048@quack2.suse.cz> <20200304162625.GA11616@lst.de>
User-agent: Mutt/1.5.17 (2007-11-01)

So I looked into this, and if it was just the uevent this
should have been fixed in:

"block: don't send uevent for empty disk when not invalidating"

from Eric Biggers in December.  Does the problem still occur with that
patch applied?

Follow-Ups:
- Re: disk revalidation updates and OOM
  - From: He Zhe

References:
- disk revalidation updates and OOM
  - From: He Zhe
- Re: disk revalidation updates and OOM
  - From: Jan Kara
- Re: disk revalidation updates and OOM
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH v2 3/7] bdi: protect device lifetime with RCU
Next by Date: Re: general protection fault in __queue_work (2)
Previous by thread: Re: disk revalidation updates and OOM
Next by thread: Re: disk revalidation updates and OOM
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux