From: Tejun Heo <tj@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernfs: use stack-buf for small writes.
Date: Tue, 23 Sep 2014 00:18:17 -0400 [thread overview]
Message-ID: <20140923041817.GA11740@mtj.dyndns.org> (raw)
In-Reply-To: <20140923140633.35efbe7a@notabene.brown>
On Tue, Sep 23, 2014 at 02:06:33PM +1000, NeilBrown wrote:
...
> Note that reads from a sysfs file are already safe due to the use for
> seqfile. The first read will allocate a buffer (m->buf) which will
> be used for all subsequent reads.
Hmmm? How is seqfile safe? Where would the seq op write to?
Thanks.
--
tejun
next prev parent reply other threads:[~2014-09-23 4:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 4:06 [PATCH] kernfs: use stack-buf for small writes NeilBrown
2014-09-23 4:12 ` Tejun Heo
2014-09-23 4:18 ` Tejun Heo [this message]
2014-09-23 4:46 ` NeilBrown
2014-09-23 4:55 ` Tejun Heo
2014-09-23 5:40 ` NeilBrown
2014-09-23 5:51 ` Tejun Heo
2014-09-23 6:11 ` NeilBrown
2014-09-23 6:15 ` Tejun Heo
2014-09-24 19:17 ` Al Viro
2014-09-24 23:58 ` 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=20140923041817.GA11740@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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