From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCHv2 7/7] zram: deprecate zram attrs sysfs nodes
Date: Fri, 13 Mar 2015 10:10:35 +0900 [thread overview]
Message-ID: <20150313011035.GA1901@swordfish> (raw)
In-Reply-To: <20150312235547.GA15607@blaptop>
Hi Minchan,
On (03/13/15 08:55), Minchan Kim wrote:
> How about adding pid, comm? Admin can know which process touches.
>
ok.
> > struct zram *zram = dev_to_zram(d); \
> > + \
> > + deprecated_attr_warn(__stringify(name)); \
>
> It just reports once for first-touched stat and miss other stats by ZRAM_ATTR_RO.
> Of course, you warned "See zram documentation" so he might know about other stats
> plan, too. If it's your intention, let's make warn more clear.
>
yes, we have a "go and read docs" warning. documentation explains it in details.
so I think one warning is enough.
> "Atrribute $s will be removed. Also, there are other stats we will remove
> in future. See Documentation/blockdev/zram.txt"
>
I didn't want it to be tooooooooooooooo long (and still don't want).
"Documentation/blockdev/zram.txt" is not a path which a regular user
can just copy-paste and use to access the documentation. so I'd prefer
to keep it as "See zram documentation".
How about this? (well, a multi-line string.)
---
drivers/block/zram/zram_drv.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index 2aced91..7f19196 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -49,7 +49,10 @@ static unsigned int num_devices = 1;
static inline void deprecated_attr_warn(const char *name)
{
- pr_warn_once("Attribute %s will be removed. See zram documentation.\n",
+ pr_warn_once("%d (%s): Attribute %s (and others) will be removed. "
+ "See zram documentation.\n",
+ task_pid_nr(current),
+ current->comm,
name);
}
next prev parent reply other threads:[~2015-03-13 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:47 [PATCHv2 0/7] new zram statistics reporting scheme Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 1/7] zram: remove `num_migrated' device attr Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 2/7] zram: move compact_store() to sysfs functions area Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 3/7] zram: use generic start/end io accounting Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 4/7] zram: describe device attrs in documentation Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 5/7] zram: export new 'io_stat' sysfs attrs Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 6/7] zram: export new 'mm_stat' " Sergey Senozhatsky
2015-03-12 14:47 ` [PATCHv2 7/7] zram: deprecate zram attrs sysfs nodes Sergey Senozhatsky
2015-03-12 23:55 ` Minchan Kim
2015-03-13 1:10 ` Sergey Senozhatsky [this message]
2015-03-13 7:39 ` Minchan Kim
2015-03-13 8:16 ` Sergey Senozhatsky
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=20150313011035.GA1901@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox