From: Andrew Morton <akpm@linux-foundation.org>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: James.Bottomley@HansenPartnership.com, jens.axboe@oracle.com,
linux-scsi@vger.kernel.org, coldwell@redhat.com, hare@novell.com
Subject: Re: [PATCH 1/1] cciss: resubmit kernel scan thread for MSA2012
Date: Wed, 11 Mar 2009 15:14:36 -0700 [thread overview]
Message-ID: <20090311151436.c9be9ab4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090311161733.GF28208@beardog.cca.cpqcorp.net>
On Wed, 11 Mar 2009 11:17:33 -0500
"Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net> wrote:
>
We haven't finished with you yet ;)
> Changed the logic in the while loop. The thread works, whenever I change my
> config the next IO to the storage returns the unit attention
> LUN_DATA_CHANGED. The thread fires off and either adds or removes the
> logical volume.
>
> Signed-off-by: Mike Miller <mike.miller@hp.com>
That's not a suitable changelog for the patch. Please maintain
changelogs alongside the patch, update them (if needed) with each
iteration and resend the full changelog each time.
> +static int scan_thread(ctlr_info_t *h)
> +{
> + int rc;
> + DECLARE_COMPLETION_ONSTACK(wait);
> + h->rescan_wait = &wait;
> +
> + while (!kthread_should_stop()) {
> + rc = wait_for_completion_interruptible(&wait);
> + if (!rc)
> + rebuild_lun_table(h, 0);
> + }
> + return 0;
> +}
This will run rebuild_lun_table() in the case where the thread is being
asked to terminate. Seems a bit peculiar, although hopefully harmless.
> + snprintf(cciss_scan, 14, "cciss_scan%02d", i);
> + hba[i]->cciss_scan_thread = kthread_run((void *)scan_thread, hba[i],
> + cciss_scan);
kthread_run() takes printf-style arguments, so this can be
hba[i]->cciss_scan_thread = kthread_run(scan_thread, hba[i],
"cciss_scan%02d", i);
and cciss_scan[] is removed.
And that void* cast of scan_thread is a bit grubby. It would be
better to be more honest to the type system and do
static int scan_thread(void *data)
{
ctlr_info_t *h = data;
...
}
next prev parent reply other threads:[~2009-03-11 22:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 15:17 [PATCH 1/1] cciss: resubmit kernel scan thread for MSA2012 Mike Miller (OS Dev)
2009-03-10 15:46 ` Mike Miller (OS Dev)
2009-03-10 15:50 ` James Bottomley
2009-03-10 16:34 ` Mike Miller (OS Dev)
2009-03-10 22:39 ` Andrew Morton
2009-03-11 14:31 ` Mike Miller (OS Dev)
2009-03-11 15:21 ` Mike Miller (OS Dev)
2009-03-11 16:17 ` Mike Miller (OS Dev)
2009-03-11 22:14 ` Andrew Morton [this message]
2009-03-12 16:26 ` Mike Miller (OS Dev)
2009-06-15 20:39 ` Mike Miller (OS Dev)
2009-06-15 21:25 ` Andrew Morton
2009-06-15 22:17 ` Mike Miller (OS Dev)
2009-06-15 22:41 ` Andrew Morton
2009-06-16 19:07 ` Mike Miller (OS Dev)
2009-06-16 19:17 ` Andrew Morton
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=20090311151436.c9be9ab4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=coldwell@redhat.com \
--cc=hare@novell.com \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox