From: David Sterba <dsterba@suse.cz>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Commit 'synchronize incompat feature bits with sysfs files' still missing in for-next?
Date: Mon, 3 Oct 2016 18:27:49 +0200 [thread overview]
Message-ID: <20161003162749.GC6576@suse.cz> (raw)
In-Reply-To: <57D7E442.2010400@applied-asynchrony.com>
On Tue, Sep 13, 2016 at 01:34:26PM +0200, Holger Hoffstätte wrote:
>
> I've noticed that the 4.5-rc commit 14e46e04:
> 'btrfs: synchronize incompat feature bits with sysfs files' [1]
> was reverted later in [2], but despite fixes to protect sysfs
> with locks & exorcise GFP_NOFS in favor of GFP_KERNEL it was
> never reinstated - neither for 4.5-final, nor later..and it's
> been quite a while since then. Is this still valid?
>
> I ask because I've just noticed I've had this in my tree since
> forever, but have never encountered a problem during balance -
> probably because of all the other fixes.
I spent sime time trying to fix it but got lost in sysfs. Supposedly,
the attribute group functions should provide all what's needed, ie.
define a set of attributes, visibility callback. Calling an update will,
in theory and my expectations, refresh the values and files. It does
not. IIRC it was never meant to work like that, so it would have to be
worked around or new sysfs helpers adde or I don't know what else.
Working with sysfs code is sometimes painful, but I'm about to return to
adding the free-space-tree bits someday.
prev parent reply other threads:[~2016-10-03 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 11:34 Commit 'synchronize incompat feature bits with sysfs files' still missing in for-next? Holger Hoffstätte
2016-10-03 16:27 ` David Sterba [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=20161003162749.GC6576@suse.cz \
--to=dsterba@suse.cz \
--cc=holger@applied-asynchrony.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).