From: majianpeng <majianpeng@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: [PATCH V1] md:Fix name of raid thread when raid takeovered.
Date: Tue, 5 Jun 2012 14:06:06 +0800 [thread overview]
Message-ID: <201206051406033596882@gmail.com> (raw)
In-Reply-To: 20120605154851.0664f8fb@notabene.brown
On Mon, 4 Jun 2012 22:49:02 -0700, neil wrote:
>On Tue, 5 Jun 2012 13:37:15 +0800 majianpeng <majianpeng@gmail.com> wrote:
>
>> When raid takeovered, it used old personality to set task->comm[].
>> So we add judgement and set corrected task->comm[].
>>
>> Signed-off-by: majianpeng <majianpeng@gmail.com>
>> ---
>> drivers/md/md.c | 14 ++++++++++++++
>> 1 files changed, 14 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>> index 1c2f904..6b3ce6e 100644
>> --- a/drivers/md/md.c
>> +++ b/drivers/md/md.c
>> @@ -6738,11 +6738,25 @@ struct md_thread *md_register_thread(void (*run) (struct mddev *), struct mddev
>> const char *name)
>> {
>> struct md_thread *thread;
>> + struct md_personality *pers = NULL;
>>
>> thread = kzalloc(sizeof(struct md_thread), GFP_KERNEL);
>> if (!thread)
>> return NULL;
>>
>> + /*
>> + *When raid takeovered,the mddev->pers was old,so the
>> + *thread_name is wrong.
>> + */
>> + if (name == NULL && mddev->level != mddev->new_level) {
>> + spin_lock(&pers_lock);
>> + list_for_each_entry(pers, &pers_list, list)
>> + if (pers->level == mddev->new_level) {
>> + name = pers->name;
>> + break;
>> + }
>> + spin_unlock(&pers_lock);
>> + }
>> init_waitqueue_head(&thread->wqueue);
>>
>> thread->run = run;
>
>No, I really don't like that. It is to focussed on fixing the particular
>symptom rather that making the code generally cleaner.
>
>Was there a reason you didn't just change the last arg of md_register_thread
>to be the level name instead of NULL??
>
No.I first wanted to corrected in which call md_register_thread.But I found it will take some codes.
So i think corrected this function may better.
>NeilBrown
>
>
--------------
majianpeng
next prev parent reply other threads:[~2012-06-05 6:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 5:37 [PATCH V1] md:Fix name of raid thread when raid takeovered majianpeng
2012-06-05 5:48 ` NeilBrown
2012-06-05 6:06 ` majianpeng [this message]
2012-06-05 6:33 ` NeilBrown
2012-06-27 3:56 ` NeilBrown
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=201206051406033596882@gmail.com \
--to=majianpeng@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).