All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <jbottomley@parallels.com>,
	Jens Axboe <axboe@fb.com>, Tejun Heo <tj@kernel.org>,
	Jan Kara <jack@suse.cz>, Hannes Reinecke <hare@suse.de>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Fix a bdi reregistration race, v2
Date: Mon, 30 Nov 2015 17:18:50 -0800	[thread overview]
Message-ID: <565CF57A.4090507@sandisk.com> (raw)
In-Reply-To: <yq1610jf0jk.fsf@sermon.lab.mkp.net>

On 11/30/2015 04:57 PM, Martin K. Petersen wrote:
>>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
>
> Bart> This race is hard to trigger. I can trigger it by repeatedly
> Bart> removing and re-adding SRP SCSI devices. Enabling debug options
> Bart> like SLUB debugging and kmemleak helps. I think that is because
> Bart> these debug options slow down the SCSI device removal code and
> Bart> thereby increase the chance that this race is triggered.
>
> Any updates on this? Your updated patch has no reviews.
>
> Should I just revert the original patch for 4.4?

Hello Martin,

Since the original patch caused a regression, please proceed with 
reverting the original patch.

Regarding this patch: is there anyone on the CC-list of this e-mail who 
can review it ?

Thanks,

Bart.

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <jbottomley@parallels.com>,
	Jens Axboe <axboe@fb.com>, Tejun Heo <tj@kernel.org>,
	Jan Kara <jack@suse.cz>, Hannes Reinecke <hare@suse.de>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Fix a bdi reregistration race, v2
Date: Mon, 30 Nov 2015 17:18:50 -0800	[thread overview]
Message-ID: <565CF57A.4090507@sandisk.com> (raw)
In-Reply-To: <yq1610jf0jk.fsf@sermon.lab.mkp.net>

On 11/30/2015 04:57 PM, Martin K. Petersen wrote:
>>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
>
> Bart> This race is hard to trigger. I can trigger it by repeatedly
> Bart> removing and re-adding SRP SCSI devices. Enabling debug options
> Bart> like SLUB debugging and kmemleak helps. I think that is because
> Bart> these debug options slow down the SCSI device removal code and
> Bart> thereby increase the chance that this race is triggered.
>
> Any updates on this? Your updated patch has no reviews.
>
> Should I just revert the original patch for 4.4?

Hello Martin,

Since the original patch caused a regression, please proceed with 
reverting the original patch.

Regarding this patch: is there anyone on the CC-list of this e-mail who 
can review it ?

Thanks,

Bart.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-12-01  1:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 22:13 [PATCH] Fix a bdi reregistration race, v2 Bart Van Assche
2015-11-20 22:13 ` Bart Van Assche
2015-11-20 22:43 ` Aaro Koskinen
2015-11-20 22:55   ` Bart Van Assche
2015-11-24 23:13 ` Christoph Hellwig
2015-11-24 23:13   ` Christoph Hellwig
2015-11-24 23:23   ` Bart Van Assche
2015-11-25  8:47     ` Christoph Hellwig
2015-11-25  8:47       ` Christoph Hellwig
2015-11-25 14:59       ` Bart Van Assche
2015-12-01  0:57         ` Martin K. Petersen
2015-12-01  1:18           ` Bart Van Assche [this message]
2015-12-01  1:18             ` Bart Van Assche
2015-12-01  7:23             ` Christoph Hellwig
2015-12-01  7:23               ` Christoph Hellwig
2016-03-28 21:26               ` Bart Van Assche

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=565CF57A.4090507@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=axboe@fb.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jbottomley@parallels.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.