grub-2.02~beta1 happened

grub-2.02~beta1 happened

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

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. The major points to do before release:
- ARM64 loader.
- Yeeloong 3A support needs some love.
- XEN would probably need config adjustments.
- XNU loader needs fixes.
- NEWS needs contents.
- Documentation.
- Loads and loads of testing and some bugfixes.

The tarball is available at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1.tar.xz
and signature at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1.tar.xz.sig

Signed with following fingerprint:
 E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 420

If you don't have xz support alternatively you may consider files
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1.tar.xz
and signature at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1.tar.xz.sig

As an experiment, I also uploaded zip binaries for windows (i386-pc,
x86_64-efi and i386-efi only, all in single zip) at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1-for-windows.zip
and signature at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta1-for-windows.zip.sig

If this proves useful similar upload can be part of release.


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

Re: grub-2.02~beta1 happened

[Bruce Dubbs]

Vladimir 'φ-coder/phcoder' Serbinenko 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. The major points to do before release:
> - ARM64 loader.
> - Yeeloong 3A support needs some love.
> - XEN would probably need config adjustments.
> - XNU loader needs fixes.
> - NEWS needs contents.
> - Documentation.
> - Loads and loads of testing and some bugfixes.

There are a few warnings for rijndael.c with gcc 4.8.2.  A couple of 
them are pretty trivial.  Others probably should be turned off with 
-Wno-strict-aliasing.  Do you want a patch?

If so, is the following acceptable?

#pragma GCC diagnostic ignored "-Wstrict-aliasing"

   -- Bruce

rijndael.c warning (was Re: grub-2.02~beta1 happened)

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

On 19.12.2013 06:43, Bruce Dubbs wrote:
> Vladimir 'φ-coder/phcoder' Serbinenko 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. The major points to do before release:
>> - ARM64 loader.
>> - Yeeloong 3A support needs some love.
>> - XEN would probably need config adjustments.
>> - XNU loader needs fixes.
>> - NEWS needs contents.
>> - Documentation.
>> - Loads and loads of testing and some bugfixes.
> 
> There are a few warnings for rijndael.c with gcc 4.8.2.  A couple of
> them are pretty trivial.  Others probably should be turned off with
> -Wno-strict-aliasing.  Do you want a patch?
> 
This file is managed by libgcrypt. Could you take issue with them? I'm
fine with backporting patches from libgcrypt but it's better not to have
own patches for libgcrypt (Debian fiasco, remember?)
> If so, is the following acceptable?
> 
> #pragma GCC diagnostic ignored "-Wstrict-aliasing"
> 
This would break gcc < 4.4 and we officially support from gcc 4.1,
unofficially 3.1 requires only a small patch to skip long double in
gnulib and few warning options.
>   -- Bruce
> 
> 
> _______________________________________________
> 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 --]

Re: rijndael.c warning (was Re: grub-2.02~beta1 happened)

[Mike Gilbert]

On Thu, Dec 19, 2013 at 7:39 AM, Vladimir 'φ-coder/phcoder' Serbinenko
<phcoder@gmail.com> wrote:
> On 19.12.2013 06:43, Bruce Dubbs wrote:
>> Vladimir 'φ-coder/phcoder' Serbinenko 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. The major points to do before release:
>>> - ARM64 loader.
>>> - Yeeloong 3A support needs some love.
>>> - XEN would probably need config adjustments.
>>> - XNU loader needs fixes.
>>> - NEWS needs contents.
>>> - Documentation.
>>> - Loads and loads of testing and some bugfixes.
>>
>> There are a few warnings for rijndael.c with gcc 4.8.2.  A couple of
>> them are pretty trivial.  Others probably should be turned off with
>> -Wno-strict-aliasing.  Do you want a patch?
>>
> This file is managed by libgcrypt. Could you take issue with them? I'm
> fine with backporting patches from libgcrypt but it's better not to have
> own patches for libgcrypt (Debian fiasco, remember?)

This has already been fixed upstream, and the change applies to grub's
copy of libgcrypt without any issues.

http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=dfb4673da8ee52d95e0a62c9f49ca8599943f22e

Re: rijndael.c warning (was Re: grub-2.02~beta1 happened)

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

On 23.12.2013 23:25, Mike Gilbert wrote:
> On Thu, Dec 19, 2013 at 7:39 AM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> On 19.12.2013 06:43, Bruce Dubbs wrote:
>>> Vladimir 'φ-coder/phcoder' Serbinenko 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. The major points to do before release:
>>>> - ARM64 loader.
>>>> - Yeeloong 3A support needs some love.
>>>> - XEN would probably need config adjustments.
>>>> - XNU loader needs fixes.
>>>> - NEWS needs contents.
>>>> - Documentation.
>>>> - Loads and loads of testing and some bugfixes.
>>>
>>> There are a few warnings for rijndael.c with gcc 4.8.2.  A couple of
>>> them are pretty trivial.  Others probably should be turned off with
>>> -Wno-strict-aliasing.  Do you want a patch?
>>>
>> This file is managed by libgcrypt. Could you take issue with them? I'm
>> fine with backporting patches from libgcrypt but it's better not to have
>> own patches for libgcrypt (Debian fiasco, remember?)
> 
> This has already been fixed upstream, and the change applies to grub's
> copy of libgcrypt without any issues.
> 
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=dfb4673da8ee52d95e0a62c9f49ca8599943f22e
> 
Done, thanks.
> _______________________________________________
> 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 --]

Re: grub-2.02~beta1 happened

[Andrey Borzenkov]

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?

ext4 inline data (Re: grub-2.02~beta1 happened)

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

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.
- 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.
> _______________________________________________
> 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 --]

Re: ext4 inline data (Re: grub-2.02~beta1 happened)

[Andrey Borzenkov]

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

В 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.

> - 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: ext4 inline data (Re: grub-2.02~beta1 happened)

[Vladimir 'φ-coder/phcoder' Serbinenko]

[-- 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 --]

Important EHCI bugfix (Re: grub-2.02~beta1 happened)

[Aleš Nesrsta]

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

Hi Vladimir,

it would be fine if the bugfix, posted by me in ML thread "EHCI/USBMS
corrections" (12/16/2013), will be included in the final release. It
solves serious bug.

I tested it on four different PCs - it is working fine, I saw no
negative results, and it helps on PCs where the problem, described in
"flash drive timing out, can't boot vmlinuz/initrd (coreboot payload)",
appeared.

Would be nice if the initial reporter "The Gluglug" will do test of this
patch. Do you know him? Could you arrange such test with him? I don't
see any further reaction from his side in ML thread "flash drive timing
out, can't boot vmlinuz/initrd (coreboot payload)".

BR,
Ales

Dne 19.12.2013 02:51, Vladimir 'φ-coder/phcoder' Serbinenko napsal(a):
> 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. The major points to do before release:
> - ARM64 loader.
> - Yeeloong 3A support needs some love.
> - XEN would probably need config adjustments.
> - XNU loader needs fixes.
> - NEWS needs contents.
> - Documentation.
> - Loads and loads of testing and some bugfixes.
> ... 
> _______________________________________________
> 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: 295 bytes --]

Re: Important EHCI bugfix (Re: grub-2.02~beta1 happened)

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

On 19.12.2013 20:59, Aleš Nesrsta wrote:
> Hi Vladimir,
> 
> it would be fine if the bugfix, posted by me in ML thread "EHCI/USBMS
> corrections" (12/16/2013), will be included in the final release. It
> solves serious bug.
> 
Check the git, it's already there, in cleaned up form.
> I tested it on four different PCs - it is working fine, I saw no
> negative results, and it helps on PCs where the problem, described in
> "flash drive timing out, can't boot vmlinuz/initrd (coreboot payload)",
> appeared.
> 
> Would be nice if the initial reporter "The Gluglug" will do test of this
> patch. Do you know him? Could you arrange such test with him? I don't
> see any further reaction from his side in ML thread "flash drive timing
> out, can't boot vmlinuz/initrd (coreboot payload)".
> 
> BR,
> Ales
> 
> Dne 19.12.2013 02:51, Vladimir 'φ-coder/phcoder' Serbinenko napsal(a):
>> 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. The major points to do before release:
>> - ARM64 loader.
>> - Yeeloong 3A support needs some love.
>> - XEN would probably need config adjustments.
>> - XNU loader needs fixes.
>> - NEWS needs contents.
>> - Documentation.
>> - Loads and loads of testing and some bugfixes.
>> ... 
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
> 
> 
> 
> _______________________________________________
> 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 --]

Re: Important EHCI bugfix (Re: grub-2.02~beta1 happened)

[Aleš Nesrsta]

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

Dne 20.12.2013 13:16, Vladimir 'φ-coder/phcoder' Serbinenko napsal(a):
> On 19.12.2013 20:59, Aleš Nesrsta wrote:
>> Hi Vladimir,
>>
>> it would be fine if the bugfix, posted by me in ML thread "EHCI/USBMS
>> corrections" (12/16/2013), will be included in the final release. It
>> solves serious bug.
>>
> Check the git, it's already there, in cleaned up form.
Nice, thanks!

BR,
Ales


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