mkfs -t ext4 invoked oom-killer on i386 kernel running on x86_64 device
and started happening on linux -next master branch kernel tag next-20200430
and next-20200501. We did not bisect this problem.
metadata
git branch: master
git repo:
Thanks for looking into this problem.
On Sat, 2 May 2020 at 02:28, Andrew Morton wrote:
>
> On Fri, 1 May 2020 18:08:28 +0530 Naresh Kamboju
> wrote:
>
> > mkfs -t ext4 invoked oom-killer on i386 kernel running on x86_64 device
> > and started happening on linux -next
On Wed, 20 May 2020 at 17:26, Naresh Kamboju wrote:
>
>
> This issue is specific on 32-bit architectures i386 and arm on linux-next
> tree.
> As per the test results history this problem started happening from
> Bad : next-20200430
> Good : next-20200429
>
> steps to r
at 14:15, Michal Hocko wrote:
>
> On Tue 19-05-20 10:11:25, Arnd Bergmann wrote:
> > On Tue, May 19, 2020 at 9:52 AM Michal Hocko wrote:
> > >
> > > On Mon 18-05-20 19:40:55, Naresh Kamboju wrote:
> > > > Thanks for looking into this problem.
> >
On Thu, 21 May 2020 at 08:10, Yafang Shao wrote:
>
> On Thu, May 21, 2020 at 2:00 AM Naresh Kamboju
> wrote:
> >
> > On Wed, 20 May 2020 at 17:26, Naresh Kamboju
> > wrote:
> > >
> > >
> > > This issue is specific on 32-bit architecture
On Thu, 21 May 2020 at 15:25, Michal Hocko wrote:
>
> On Wed 20-05-20 20:09:06, Chris Down wrote:
> > Hi Naresh,
> >
> > Naresh Kamboju writes:
> > > As a part of investigation on this issue LKFT teammate Anders Roxell
> > > git bisected the pr
On Thu, 21 May 2020 at 00:39, Chris Down wrote:
>
> Hi Naresh,
>
> Naresh Kamboju writes:
> >As a part of investigation on this issue LKFT teammate Anders Roxell
> >git bisected the problem and found bad commit(s) which caused this problem.
> >
> >The foll
My apology !
As per the test results history this problem started happening from
Bad : next-20200430 (still reproducible on next-20200519)
Good : next-20200429
The git tree / tag used for testing is from linux next-20200430 tag and reverted
following three patches and oom-killer problem fixed.
On Thu, 21 May 2020 at 22:04, Michal Hocko wrote:
>
> On Thu 21-05-20 11:55:16, Michal Hocko wrote:
> > On Wed 20-05-20 20:09:06, Chris Down wrote:
> > > Hi Naresh,
> > >
> > > Naresh Kamboju writes:
> > > > As a part of investigation on this iss
On Thu, 28 May 2020 at 20:33, Michal Hocko wrote:
>
> On Fri 22-05-20 02:23:09, Naresh Kamboju wrote:
> > My apology !
> > As per the test results history this problem started happening from
> > Bad : next-20200430 (still reproducible on next-20200519)
> > Good :
On Thu, 21 May 2020 at 22:04, Michal Hocko wrote:
>
> On Thu 21-05-20 11:55:16, Michal Hocko wrote:
> > On Wed 20-05-20 20:09:06, Chris Down wrote:
> > > Hi Naresh,
> > >
> > > Naresh Kamboju writes:
> > > > As a part of investigation on this iss
On Wed, 17 Jun 2020 at 19:41, Michal Hocko wrote:
>
> [Our emails have crossed]
>
> On Wed 17-06-20 14:57:58, Chris Down wrote:
> > Naresh Kamboju writes:
> > > mkfs -t ext4 /dev/disk/by-id/ata-TOSHIBA_MG04ACA100N_Y8RQK14KF6XF
> > > mke2fs 1.43.8 (1
On Wed, 17 Jun 2020 at 21:36, Michal Hocko wrote:
>
> On Wed 17-06-20 21:23:05, Naresh Kamboju wrote:
> > On Wed, 17 Jun 2020 at 19:41, Michal Hocko wrote:
> > >
> > > [Our emails have crossed]
> > >
> > > On Wed 17-06-20 14:57:58, Chris Down wrot
On Thu, 11 Jun 2020 at 15:25, Michal Hocko wrote:
>
> On Fri 29-05-20 11:49:20, Michal Hocko wrote:
> > On Fri 29-05-20 02:56:44, Chris Down wrote:
> > > Yafang Shao writes:
> > Agreed. Even if e{low,min} might still have some rough edges I am
> > completely puzzled how we could end up oom if
14 matches
Mail list logo
