On 04/27/2016 10:40 AM, Stefan Roese wrote:
From: Ronald Zachariah
The function ext4fs_read_symlink was unable to handle a symlink
which had target name of exactly 60 characters.
Reviewed-by: Stephen Warren
This seems to match how the Linux kernel encodes symlinks.
- if (__le32_to_c
From: Ronald Zachariah
The function ext4fs_read_symlink was unable to handle a symlink
which had target name of exactly 60 characters.
Signed-off-by: Ronald Zachariah
Signed-off-by: Stefan Roese
Cc: Stephen Warren
Cc: Tom Rini
---
fs/ext4/ext4_common.c | 2 +-
1 file changed, 1 insertion(+)
Hi Gary,
On Tuesday, 8 September 2015, Gary Bisson
wrote:
>
> Hi Simon,
>
> On Tue, Sep 8, 2015 at 5:56 AM, Simon Glass wrote:
> > Hi Gary,
> >
> > On 7 September 2015 at 03:20, Gary Bisson
> > wrote:
> >> Since last API changes for files >2GB, the read of symlink is broken as
> >> ext4fs_read_
Hi Simon,
On Tue, Sep 8, 2015 at 5:56 AM, Simon Glass wrote:
> Hi Gary,
>
> On 7 September 2015 at 03:20, Gary Bisson
> wrote:
>> Since last API changes for files >2GB, the read of symlink is broken as
>> ext4fs_read_file now returns 0 instead of the length of the actual read.
>>
>> Signed-off-b
Hi Gary,
On 7 September 2015 at 03:20, Gary Bisson
wrote:
> Since last API changes for files >2GB, the read of symlink is broken as
> ext4fs_read_file now returns 0 instead of the length of the actual read.
>
> Signed-off-by: Gary Bisson
> ---
> Hi all,
>
> Switching from an old v2014.07 to v201
Since last API changes for files >2GB, the read of symlink is broken as
ext4fs_read_file now returns 0 instead of the length of the actual read.
Signed-off-by: Gary Bisson
---
Hi all,
Switching from an old v2014.07 to v2015.07 we've noticed that we couldn't
read symlinks any more. This is due to
6 matches
Mail list logo
