| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [BUG] Slab corruption during XFS writeback under memory pressure |
| From: | Calvin Owens <calvinowens@xxxxxx> |
| Date: | Mon, 18 Jul 2016 19:05:44 -0700 |
| Cc: | <linux-block@xxxxxxxxxxxxxxx>, <kernel-team@xxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-scsi@xxxxxxxxxxxxxxx>, <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=from : subject : to : references : cc : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=facebook; bh=f9yXi7DmeazKv2Dqra7UCcTyihzOeS/yKixr4/9FncE=; b=qK/9Gqi/F5Epp2OZVYTh/yjXhTVIoTHWYdrXwsKfbCUG6s0h4900iJLhSgLhS+7DcSOW zsYCxOGyfmbyOavTuprTfSQHCh4bO85xpA71vDcQRGUjq/mBWNrD67arfSzfJ89cqT2f lykBAmX+Ui82B3WJAnKttLS8w5yxjM5AemU= |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=f9yXi7DmeazKv2Dqra7UCcTyihzOeS/yKixr4/9FncE=; b=UkahID1xHOVnmGV+QyUqvQjY5+YkgrXGNmIS7AJDsj1fzcp7I70MBM7GHrQrfjMCN187RQJyuvc9Zn9zrOy1VF3UonBo5d64eEnX50ZPmsS99NIfJZtONAd1dkFnxGX/irAIJl/BjnH0uV6a7/GH2r5WFwzFf2mhrH367OEKcdY= |
| In-reply-to: | <20160718060215.GB16044@dastard> |
| References: | <28f77d74-5ab4-d913-2921-df90da53f393@xxxxxx> <20160717000003.GW1922@dastard> <20160718060215.GB16044@dastard> |
| Spamdiagnosticmetadata: | NSPM |
| Spamdiagnosticoutput: | 1:99 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0 |
On 07/17/2016 11:02 PM, Dave Chinner wrote: On Sun, Jul 17, 2016 at 10:00:03AM +1000, Dave Chinner wrote:On Fri, Jul 15, 2016 at 05:18:02PM -0700, Calvin Owens wrote:Hello all, I've found a nasty source of slab corruption. Based on seeing similar symptoms on boxes at Facebook, I suspect it's been around since at least 3.10. It only reproduces under memory pressure so far as I can tell: the issue seems to be that XFS reclaims pages from buffers that are still in use by scsi/block. I'm not sure which side the bug lies on, but I've only observed it with XFS.[....]But this indicates that the page is under writeback at this point, so that tends to indicate that the above freeing was incorrect. Hmmm - it's clear we've got direct reclaim involved here, and the suspicion of a dirty page that has had it's bufferheads cleared. Are there any other warnings in the log from XFS prior to kasan throwing the error?Can you try the patch below? Thanks for getting this out so quickly :) So far so good: I booted Linus' tree as of this morning and reproduced the ASAN splat. After applying your patch I haven't triggered it. I'm a bit wary since it was hard to trigger reliably in the first place... so I lined up a few dozen boxes to run the test case overnight. I'll confirm in the morning (-0700) they look good. Thanks, Calvin -Dave. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 044/119] xfs: propagate bmap updates to rmapbt, Darrick J. Wong |
|---|---|
| Next by Date: | Re: iomap infrastructure and multipage writes V5, Christoph Hellwig |
| Previous by Thread: | Re: [BUG] Slab corruption during XFS writeback under memory pressure, Dave Chinner |
| Next by Thread: | Re: [BUG] Slab corruption during XFS writeback under memory pressure, Calvin Owens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |