grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: ext4 inline data (Re: grub-2.02~beta1 happened)
Date: Thu, 19 Dec 2013 19:23:32 +0100	[thread overview]
Message-ID: <52B339A4.6080709@gmail.com> (raw)
In-Reply-To: <20131219200542.32cdec6d@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

On 19.12.2013 17:05, Andrey Borzenkov wrote:
> В Thu, 19 Dec 2013 10:53:54 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> 
>> On 19.12.2013 07:38, Andrey Borzenkov wrote:
>>> On Thu, Dec 19, 2013 at 5:51 AM, Vladimir 'φ-coder/phcoder' Serbinenko
>>> <phcoder@gmail.com> wrote:
>>>> Hello, all. I've just uploaded 2.02~beta1. This also means that we're
>>>> now in freeze. I'm willing to consider exceptions on case-by-case basis
>>>> but it would be exceptions.
>>>
>>> You did not answer my question whether I should commit ext4 inline
>>> data support. Do I understand it correctly you do not plan to include
>>> it in release?
>>>
>> There were several problems with it:
>> - Apparently the format isn't completely stable. A discussion dated of
>> December 2013 proposes to change format in order to squeeze in a little
>> bit more data.
> 
> I suspect we'll need to support both then, just like kernel. But that
> can live in a branch and be tested downstream first, when e2fsprogs
> with inline support is finally available.
> 
Yes, and it would be good to add it to ext234_test.
This ever chaging format is tricky one to handle. After release we'll
probably be able to merge it to master.
>> - Patch would crash on ARM due to misaligned access
>> - There are memory leaks.
>> For 2nd and 3rd I've uploaded fixes to andrey/ext4_inline_data but then
>> because lack of support in version packaged by Debian sid I couldn't
>> test it.
> 
> Thank you! Unfortunately I have only x86 to test.
> 
cross-compiling for ARM already catches most of them due to -Wcast-align
as long as you don't cast pointer to int or reverse or use void *.
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-12-19 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  1:51 grub-2.02~beta1 happened Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19  5:43 ` Bruce Dubbs
2013-12-19 12:39   ` rijndael.c warning (was Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-23 22:25     ` Mike Gilbert
2013-12-24 15:58       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19  6:38 ` grub-2.02~beta1 happened Andrey Borzenkov
2013-12-19  9:53   ` ext4 inline data (Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 16:05     ` Andrey Borzenkov
2013-12-19 18:23       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-19 19:59 ` Important EHCI bugfix " Aleš Nesrsta
2013-12-20 12:16   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-20 17:57     ` Aleš Nesrsta

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=52B339A4.6080709@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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).