On Sat, May 18, 2019 at 10:19 PM Theodore Ts'o wrote:
>
> On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> > IOW, Dan's fix folded into the offending commit. And that kind of
> > pattern is not rare; I would argue that appending Dan's patch at
> > the end of queue and leaving the crap i
On Sat, May 18, 2019 at 11:41 PM Al Viro wrote:
> > > What would you prefer to happen in such situations? Commit summaries
> > > modified enough to confuse CI tools into *NOT* noticing that those
> > > are versions of the same patch? Some kind of metadata telling the
> > > same tools that such-a
.On Sat, May 18, 2019 at 6:21 PM Al Viro wrote:
>
> On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> > On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> > >
> > > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > > >
> > > > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot
On Sat, May 18, 2019 at 04:18:43PM -0400, Theodore Ts'o wrote:
> > What would you prefer to happen in such situations? Commit summaries
> > modified enough to confuse CI tools into *NOT* noticing that those
> > are versions of the same patch? Some kind of metadata telling the
> > same tools that
On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> IOW, Dan's fix folded into the offending commit. And that kind of
> pattern is not rare; I would argue that appending Dan's patch at
> the end of queue and leaving the crap in between would be a fucking
> bad idea - it would've left a mass
On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> > On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> > >
> > > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > > >
> > > > On Fri, May 17, 2019 at 03:17:02AM -0700, s
On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> >
> > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > >
> > > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > > > This bug is marked as fixed by commit:
> > > > v
On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
>
> On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> >
> > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > > This bug is marked as fixed by commit:
> > > vfs: namespace: error pointer dereference in do_remount()
> > > But I can't fi
On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
>
> On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > This bug is marked as fixed by commit:
> > vfs: namespace: error pointer dereference in do_remount()
> > But I can't find it in any tested tree for more than 90 days.
> > Is it a correct
On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> This bug is marked as fixed by commit:
> vfs: namespace: error pointer dereference in do_remount()
> But I can't find it in any tested tree for more than 90 days.
> Is it a correct commit? Please update it by replying:
> #syz fix: exact-comm
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new cras
This is fixed by patch vfs: namespace: error pointer dereference in do_remount()
#syz fix: vfs: namespace: error pointer dereference in do_remount()
On 21.09.2018 09:44, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: a0cb0cabe4bb Add linux-next specific file
Hello,
syzbot found the following crash on:
HEAD commit:a0cb0cabe4bb Add linux-next specific files for 20180920
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164d651140
kernel config: https://syzkaller.appspot.com/x/.config?x=786006c5dafbadf6
dashb
19 matches
Mail list logo
