linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongsu Park <dongsu.park@profitbricks.com>
To: Daniel Phillips <daniel@phunq.net>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-fsdevel@vger.kernel.org, tux3@tux3.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Tux3 for review
Date: Thu, 22 May 2014 11:52:27 +0200	[thread overview]
Message-ID: <20140522095227.GA9176@gmail.com> (raw)
In-Reply-To: <537AA802.408@phunq.net>

Hi,

On 19.05.2014 17:55, Daniel Phillips wrote:
> On 05/18/2014 04:55 PM, Dave Chinner wrote:
> >On Fri, May 16, 2014 at 05:50:59PM -0700, Daniel Phillips wrote:
> >>We would like to offer Tux3 for review for mainline merge. We have
> >>prepared a new repository suitable for pulling:
> >>
> >>https://git.kernel.org/cgit/linux/kernel/git/daniel/linux-tux3.git/

First of all, thank you for trying to merge it to mainline.
Maybe I cannot say the code is clean enough, but basically
the filesystem seems to work at least.

> >Then there's all the writeback hacks. You've simply copy-n-pasted
> >most of fs-writeback.c, including duplicating structures like struct
> >wb_writeback_work and then hacked in crap (kallsyms lookups!) to be
> >able to access core structures from kernel module context
> >(tux3_setup_writeback(), I'm looking at you).
> This is intentional. The files named "*_hack" were kept as close as
> possible to the original core code to clarify exactly where core
> needs to change in order to remove our workarounds. If you think we
> should pretty up that code then we will happily do it. Or maybe we
> can hammer out acceptable core patches right now, and include those
> with our merge proposal. That would make us even happier. We hate
> those hacks as much as you do.

Looking up kallsyms is not only hacky, but also making the filesystem
unable to be mounted at all, when CONFIG_KALLSYMS_ALL is not defined.
I'll send out patches to fix that separately to tux3 mailing list.

Regards,
Dongsu

  parent reply	other threads:[~2014-05-22  9:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17  0:50 [RFC] Tux3 for review Daniel Phillips
2014-05-17  5:09 ` Martin Steigerwald
2014-05-17  5:29   ` Daniel Phillips
2014-05-20  6:56     ` Daniel Phillips
2014-05-18 23:55 ` Dave Chinner
2014-05-20  0:55   ` Daniel Phillips
2014-05-20  3:18     ` Dave Chinner
2014-05-20  5:41       ` Daniel Phillips
2014-05-20 17:25         ` Daniel Phillips
2014-06-13 10:32       ` Pavel Machek
2014-06-13 17:49         ` Daniel Phillips
2014-06-13 20:20           ` Pavel Machek
2014-06-15 21:41             ` Daniel Phillips
2014-06-16 15:25               ` James Bottomley
2014-06-19  8:21                 ` Pavel Machek
2014-06-19  9:26                   ` Lukáš Czerner
2014-06-19 21:58                     ` Daniel Phillips
2014-06-21 19:29                       ` James Bottomley
2014-06-22  1:06                         ` Dave Chinner
2014-06-24 11:16                           ` Daniel Phillips
2014-06-22  3:32                         ` Daniel Phillips
2014-06-22 14:43                           ` James Bottomley
     [not found]                             ` <522aee97-34e7-4adc-adf2-c9b73aa0ef36@phunq.net>
2014-06-24  4:41                               ` James Bottomley
2014-06-24  9:10                                 ` Daniel Phillips
2014-06-24 10:59                                   ` Theodore Ts'o
2014-06-24 11:27                                     ` Daniel Phillips
2014-06-24 11:52                                       ` James Bottomley
2014-06-24 12:10                                         ` Daniel Phillips
2014-06-22 18:34                           ` Theodore Ts'o
2014-06-24  0:31                             ` Daniel Phillips
2014-06-24  0:19                         ` Daniel Phillips
2014-05-22  9:52     ` Dongsu Park [this message]
2014-05-23  8:21       ` Daniel Phillips
2014-06-19 16:24 ` Josef Bacik
2014-06-19 22:14   ` Daniel Phillips

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=20140522095227.GA9176@gmail.com \
    --to=dongsu.park@profitbricks.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@phunq.net \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tux3@tux3.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).