public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Fubo Chen <fubo.chen@gmail.com>, Christoph Hellwig <hch@lst.de>,
	"J.H." <warthog9@kernel.org>, Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH] target: Call proc_mkdir + remove_proc_entry with NULL parameter
Date: Mon, 24 Jan 2011 12:54:22 -0800	[thread overview]
Message-ID: <1295902462.24778.40.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1295791971.3007.0.camel@mulgrave.site>

On Sun, 2011-01-23 at 08:12 -0600, James Bottomley wrote:
> On Sat, 2011-01-22 at 15:20 -0800, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> > 
> > This patch makes proc_mkdir() and remove_proc_entry() use a NULL
> > parameter to fix the following sparse warning:
> > 
> > CHECK   drivers/target/target_core_configfs.c
> > drivers/target/target_core_configfs.c:3131:54: warning: Using plain integer as NULL pointer
> > drivers/target/target_core_configfs.c:3145:50: warning: Using plain integer as NULL pointer
> > drivers/target/target_core_configfs.c:3212:42: warning: Using plain integer as NULL pointer
> 
> Um, so I thought this interface was being replaced ... there's not a lot
> of point in sparse fixing it.
> 

Hi James,

So my plan here is to move these statistics in /proc/scsi_target/ into
configfs specific contexts for TCM v4.1.  This also includes moving
iscsi_target_mod -> /proc/iscsi_target/ to use 
/sys/kernel/config/target/iscsi/ context attributes using our existing
CONFIGFS_EATTR() based macros in target_core_fabric_configfs.h
to provide the fabric dependent attributes.

So for target core this should be easy enough to split up short term in
'for-39', but the generic fabric statistics piece will require some new
logic that allows CONFIGFS_EATTR() macros to be seq_list() aware in
order to cat more than PAGE_SIZE for a individual configfs statistic
attribute some (one..?) special case. (jlbec CC'ed)

The reason we need this is to handle the N possible dynamic demo mode
struct se_node_acl (Initiator NodeACL) per TargetName+TargetPortalGroup
endpoint that we need for BKO ops.  (J.H CC'ed)

--nab



      reply	other threads:[~2011-01-24 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 23:20 [PATCH] target: Call proc_mkdir + remove_proc_entry with NULL parameter Nicholas A. Bellinger
2011-01-22 23:20 ` [PATCH] target: Convert backend ->create_virtdevice() call to return ERR_PTR Nicholas A. Bellinger
2011-01-23 14:12 ` [PATCH] target: Call proc_mkdir + remove_proc_entry with NULL parameter James Bottomley
2011-01-24 20:54   ` Nicholas A. Bellinger [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=1295902462.24778.40.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=fubo.chen@gmail.com \
    --cc=hch@lst.de \
    --cc=jlbec@evilplan.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=warthog9@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