public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic TEMPORELLI <frederic.temporelli@ext.bull.net>
To: linux-kernel <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Cc: Frederic TEMPORELLI <frederic.temporelli@ext.bull.net>
Subject: Re: kernel workqueue -max name length
Date: Wed, 10 Aug 2005 07:45:18 +0200	[thread overview]
Message-ID: <42F9946E.2040609@ext.bull.net> (raw)
In-Reply-To: <42F8AE91.9030708@ext.bull.net>

Hi,


any explanation about the 10 chars limit for kernel workqueue name ?


another question: why is the name length test managed by BUG_ON ?
returning a NULL workqueue is done in the next test (failed kmalloc for wq)...

Anyway, this can explain some issues when loading some SCSI drivers modules.


hope that somebody knows...


Frederic TEMPORELLI wrote:
> Hello,
> 
> 
> When creating a workqueue, workqueue name is limited to 10 chars
> (kernel/workqueue.c , function is __create_workqueue, test is done in a 
> BUG_ON).
> 
> Why has this length be limited to 10 chars ?
> Can I safely increase this max length (13 chars should be enough...) ?
> 
> 
> 
> Some comments about these questions:
> 
> In SCSI layer, HBA kernel ID is incremented after each modprobe/rmmod.
> 
> Then, when a scsi driver is managing a working queue and HBA kernel ID 
> is greater than 99 (let's assume that you have modprobe/rmmod the scsi 
> driver to get this ID to 99, or you may have play with 'scsi_debug' 
> module), an oops is generated when loading again the driver (and the 
> driver is frozen).
> 
> This is because working queue name format is "scsi_wq_%d" 
> (drivers/scsi/hosts.c , function scsi_add_host, %d is the HBA ID), and 
> so working queue name length is greater than 10 chars when HBA kernel ID 
> is > 99...
> 
> 
> Best regards
> 
> 


-- 
Frederic TEMPORELLI


      reply	other threads:[~2005-08-10  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 13:24 max workqueue name length Frederic TEMPORELLI
2005-08-10  5:45 ` Frederic TEMPORELLI [this message]

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=42F9946E.2040609@ext.bull.net \
    --to=frederic.temporelli@ext.bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox