From: Edward Shishkin <edward.shishkin@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: SOLVED! Re: Issues with reiser4 patch for Linux 4.12.0.
Date: Fri, 18 Aug 2017 11:13:02 +0200 [thread overview]
Message-ID: <4b456c74-f647-0252-01a5-01c532eb8d11@gmail.com> (raw)
In-Reply-To: <20170818053540.C4688C8D972@mictlantecuhtli.metztli-it.com>
Resource was used right after its release - a kind of sleeping bug..
Edward.
On 08/18/2017 07:35 AM, Jose R Rodriguez wrote:
> Your included patch worked, Edward. Thank you.
>
>> Hello.
>> Does the attached patch help?
>> Thanks,
>> Edward.
> On 08/17/2017 02:14 AM, Jose R Rodriguez wrote:
>>> Niltze, Ed-
>>>
>>> I have applied your latest patch to Debian Linux kernel and packaging 12.4.6-1, itself patched with upstream differential kernel patch 4.12.6-7.
>>>
>>> After ironing out some Debian kernel maintainer packaging code issues, i.e.,
>>>
>>> Modifying:
>>> debian/rules.d/tools/power/x86/turbostat/Makefile
>>>
>>> and replacing directive:
>>> CPPFLAGS += -DMSRHEADER='<asm/msr-index.h>' -DINTEL_FAMILY_HEADER='"$(top_srcdir)/arch/x86/include/asm/intel-family.h"'
>>>
>>> with
>>> CPPFLAGS += -DMSRHEADER='"$(top_srcdir)/arch/x86/include/asm/msr-index.h"' -DINTEL_FAMILY_HEADER='"$(top_srcdir)/arch/x86/include/asm/intel-family.h"'
>>>
>>> enabled the compiler to complete build procedure where it was failing.
>>>
> []
>
> --------------D029B91EB0C5287A303173DF
> Content-Type: text/x-patch;
> name="reiser4-done-fs-info-after-exit-ctx.patch"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> filename="reiser4-done-fs-info-after-exit-ctx.patch"
>
> diff --git a/init_super.c b/init_super.c
> index fb37605..f45e42d 100644
> --- a/init_super.c
> +++ b/init_super.c
> @@ -47,14 +47,10 @@ int reiser4_init_fs_info(struct super_block *super)
> void reiser4_done_fs_info(struct super_block *super)
> {
> assert("zam-990", super->s_fs_info != NULL);
> -
> - /* release per-super-block d_cursor resources */
> + /*
> + * release per-super-block d_cursor resources
> + */
> reiser4_done_super_d_info(super);
> -
> - /* make sure that there are not jnodes already */
> - assert("", list_empty(&get_super_private(super)->all_jnodes));
> - assert("", get_current_context()->trans->atom == NULL);
> - reiser4_check_block_counters(super);
> kfree(super->s_fs_info);
> super->s_fs_info = NULL;
> }
> diff --git a/page_cache.c b/page_cache.c
> index 099c00a..c566bf9 100644
> --- a/page_cache.c
> +++ b/page_cache.c
> @@ -282,19 +282,16 @@ void reiser4_done_formatted_fake(struct super_block *super)
> sinfo = get_super_private_nocheck(super);
>
> if (sinfo->fake != NULL) {
> - inode_detach_wb(sinfo->fake);
> iput(sinfo->fake);
> sinfo->fake = NULL;
> }
>
> if (sinfo->bitmap != NULL) {
> - inode_detach_wb(sinfo->bitmap);
> iput(sinfo->bitmap);
> sinfo->bitmap = NULL;
> }
>
> if (sinfo->cc != NULL) {
> - inode_detach_wb(sinfo->cc);
> iput(sinfo->cc);
> sinfo->cc = NULL;
> }
> diff --git a/super_ops.c b/super_ops.c
> --- a/super_ops.c
> index 697580c..2222e86 100644
> +++ b/super_ops.c
> @@ -257,8 +257,12 @@ static void reiser4_put_super(struct super_block *super)
> reiser4_done_ktxnmgrd(super);
> reiser4_done_txnmgr(&sbinfo->tmgr);
>
> - reiser4_done_fs_info(super);
> + assert("edward-1890", list_empty(&get_super_private(super)->all_jnodes));
> + assert("edward-1891", get_current_context()->trans->atom == NULL);
> + reiser4_check_block_counters(super);
> +
> reiser4_exit_context(ctx);
> + reiser4_done_fs_info(super);
> }
>
> /**
>
> --------------D029B91EB0C5287A303173DF--
> --
>
> Obviously it also solved the sudden crash upon powering down and/or rebooting (hence umounting) this Debian development environment on reiser4 root filesystem, too.
>
> Again, much appreciated Mr. Shishkin!
>
>
> Best Professional Regards.
>
prev parent reply other threads:[~2017-08-18 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 5:35 SOLVED! Re: Issues with reiser4 patch for Linux 4.12.0 Jose R Rodriguez
2017-08-18 9:13 ` Edward Shishkin [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=4b456c74-f647-0252-01a5-01c532eb8d11@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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).