Dmitry noticed what is wrong and fixed the bug as
https://github.com/google/syzkaller/commit/06c33b3af0ff4072fb002879f83077c9d162a224
.
Since the bug did not reproduce for last 24 hours, it is OK to close this
report.
#syz invalid
Thanks all.
On 2018/06/19 20:10, Tetsuo Handa wrote:
> On 2018/06/16 4:40, Tetsuo Handa wrote:
>> Hmm, there might be other locations calling percpu_rwsem_release() ?
>
> There are other locations calling percpu_rwsem_release(), but quite few.
>
> include/linux/fs.h:1494:#define __sb_writers_release(sb, lev)
On 2018/06/19 20:47, Dmitry Vyukov wrote:
>> If no, we would want a git tree for testing under syzbot.
>
> Thinking of this, we could setup a sandbox instance that won't report
> anything over email at all, but crashes will be available on the web.
> We could point this instance to a custom git tr
On Tue, Jun 19, 2018 at 1:10 PM, Tetsuo Handa
wrote:
> On 2018/06/16 4:40, Tetsuo Handa wrote:
>> Hmm, there might be other locations calling percpu_rwsem_release() ?
>
> There are other locations calling percpu_rwsem_release(), but quite few.
>
> include/linux/fs.h:1494:#define __sb_writers_relea
On 2018/06/16 4:40, Tetsuo Handa wrote:
> Hmm, there might be other locations calling percpu_rwsem_release() ?
There are other locations calling percpu_rwsem_release(), but quite few.
include/linux/fs.h:1494:#define __sb_writers_release(sb, lev) \
include/linux/fs.h-1495-
percpu_rwsem_r
On 2018/06/15 18:19, Dmitry Vyukov wrote:
> On Thu, Jun 14, 2018 at 12:33 PM, Tetsuo Handa
> wrote:
>> On 2018/06/11 16:39, Dmitry Vyukov wrote:
>>> On Mon, Jun 11, 2018 at 9:30 AM, Peter Zijlstra
>>> wrote:
On Sun, Jun 10, 2018 at 11:47:56PM +0900, Tetsuo Handa wrote:
> This looks
On Thu, Jun 14, 2018 at 12:33 PM, Tetsuo Handa
wrote:
> On 2018/06/11 16:39, Dmitry Vyukov wrote:
>> On Mon, Jun 11, 2018 at 9:30 AM, Peter Zijlstra wrote:
>>> On Sun, Jun 10, 2018 at 11:47:56PM +0900, Tetsuo Handa wrote:
>>>
This looks quite strange that nobody is holding percpu_rw_semaphor
On 2018/06/11 16:39, Dmitry Vyukov wrote:
> On Mon, Jun 11, 2018 at 9:30 AM, Peter Zijlstra wrote:
>> On Sun, Jun 10, 2018 at 11:47:56PM +0900, Tetsuo Handa wrote:
>>
>>> This looks quite strange that nobody is holding percpu_rw_semaphore for
>>> write but everybody is stuck trying to hold it for
On Mon, Jun 11, 2018 at 9:30 AM, Peter Zijlstra wrote:
> On Sun, Jun 10, 2018 at 11:47:56PM +0900, Tetsuo Handa wrote:
>
>> This looks quite strange that nobody is holding percpu_rw_semaphore for
>> write but everybody is stuck trying to hold it for read. (Since there
>> is no "X locks held by ...
On Sun, Jun 10, 2018 at 11:47:56PM +0900, Tetsuo Handa wrote:
> This looks quite strange that nobody is holding percpu_rw_semaphore for
> write but everybody is stuck trying to hold it for read. (Since there
> is no "X locks held by ..." line without followup "#0:" line, there is
> no possibility
Hello.
Commits
401c636a0eeb0d51 "kernel/hung_task.c: show all hung tasks before panic"
8cc05c71ba5f7936 "locking/lockdep: Move sanity check to inside
lockdep_print_held_locks()"
arrived at linux.git and syzbot started giving us more hints.
Quoting from
https://syzkaller.appspot.com/text?t
Hello,
syzbot found the following crash on:
HEAD commit:06dd3dfeea60 Merge tag 'char-misc-4.17-rc1' of
git://git.k...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1291108780
kernel config: https://syzkaller.appspot.com/x/.config?x=301513bac2f9fd9
12 matches
Mail list logo
