All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "dwagner@suse.de" <dwagner@suse.de>,
	"osandov@fb.com" <osandov@fb.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	pankydev8@gmail.com, javier.gonz@samsung.com,
	joshi.k@samsung.com, vincent.fu@samsung.com,
	a.manzanares@samsung.com, e.kyvenko@samsung.com,
	k.jensen@samsung.com
Subject: Re: [PATCH] blktests: replace module removal with patient module removal
Date: Thu, 20 Jan 2022 12:25:40 -0800	[thread overview]
Message-ID: <YenFRNuU2sUNxvpx@bombadil.infradead.org> (raw)
In-Reply-To: <YbCqsDQxzk0Q0hSl@bombadil.infradead.org>

On Wed, Dec 08, 2021 at 04:53:04AM -0800, Luis Chamberlain wrote:
> On Thu, Nov 18, 2021 at 01:38:49AM +0000, Chaitanya Kulkarni wrote:
> > On 11/16/21 09:29, Luis Chamberlain wrote:
> > > A long time ago, in a galaxy far, far away...
> > > 
> > > I ran into some odd scsi_debug false positives with fstests. This
> > > prompted me to look into them given these false positives prevents
> > > me from moving forward with establishing a test baseline with high
> > > number of cycles. That is, this stupid issue was prevening creating
> > > high confidence in testing.
> > > 
> > > I reported it [0] and exchanged some ideas with Doug. However, in
> > > the end, despite efforts to help things with scsi_debug there were
> > > still issues lingering which seemed to defy our expectations upstream.
> > > One of the last hanging fruit issues is and always has been that
> > > userspace expectations for proper module removal has been broken,
> > > so in the end I have demonstrated this is a generic issue [1].
> > > 
> > > Long ago a WAIT option for module removal was added... that was then
> > > removed as it was deemed not needed as folks couldn't figure out when
> > > these races happened. The races are actually pretty easy to trigger, it
> > > was just never properly documented. A simpe blkdev_open() will easily
> > > bump a module refcnt, and these days many thing scan do that sort of
> > > thing.
> > > 
> > > The proper solution is to implement then a patient module removal
> > > on kmod and patches have been sent for that and those patches are
> > > under review. In the meantime we need a work around to open code a
> > > similar solution for users of old versions of kmod. I sent an open
> > > coded solution for fstests about since August 19th and has been used
> > > there for a few months now. Now that that stuff is merged and tested
> > > in fstests with more exposure, its time to match parity on blktests.
> > > 
> > > I've tested blktests with this for things which I can run virtually
> > > for a while now. More wider testig is welcomed.
> > > 
> > > [0] https://bugzilla.kernel.org/show_bug.cgi?id=212337
> > > [1] https://bugzilla.kernel.org/show_bug.cgi?id=214015
> > > Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> > >
> > 
> > Thanks for having this work done and explaining the importance of it.
> > 
> > Give me couple of days, I'll provide you a feedback after I finish my
> > testing of your patch.
> 
> How did testing go?

*Friendly poke*

  Luis

  reply	other threads:[~2022-01-20 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 17:29 [PATCH] blktests: replace module removal with patient module removal Luis Chamberlain
2021-11-18  1:38 ` Chaitanya Kulkarni
2021-12-08 12:53   ` Luis Chamberlain
2022-01-20 20:25     ` Luis Chamberlain [this message]
2022-01-26  5:39 ` Chaitanya Kulkarni
2022-02-05  2:33   ` Luis Chamberlain
2022-02-06  3:57     ` Bart Van Assche
2022-02-05 17:50 ` Theodore Ts'o
2022-02-08  1:10 ` Bart Van Assche
2022-02-08 21:21   ` Luis Chamberlain
2022-02-08 22:26     ` Bart Van Assche
2022-04-13 22:46       ` Luis Chamberlain

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=YenFRNuU2sUNxvpx@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=a.manzanares@samsung.com \
    --cc=chaitanyak@nvidia.com \
    --cc=dwagner@suse.de \
    --cc=e.kyvenko@samsung.com \
    --cc=javier.gonz@samsung.com \
    --cc=joshi.k@samsung.com \
    --cc=k.jensen@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=pankydev8@gmail.com \
    --cc=vincent.fu@samsung.com \
    /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.