On Thu, Jul 26, 2018 at 11:12 AM, Miklos Szeredi wrote:
> On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote:
>> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
>>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>
>>> Maybe more waits in fuse need to be interruptible? E.g.
On Thu, Jul 26, 2018 at 11:12 AM, Miklos Szeredi wrote:
> On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote:
>> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
>>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>
>>> Maybe more waits in fuse need to be interruptible? E.g.
On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote:
> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>> Maybe more waits in fuse need to be interruptible? E.g. request_wait_answer?
>
> That's an interesting aspect. Making
On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote:
> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>> Maybe more waits in fuse need to be interruptible? E.g. request_wait_answer?
>
> That's an interesting aspect. Making
On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests
On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests
On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
> Biggest conceptual problem: your definition of fuse-server is weak.
> Take the following example: process A is holding the fuse device fd
> and is forwarding requests and replies to/from process B via a pipe.
> So basically
On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
> Biggest conceptual problem: your definition of fuse-server is weak.
> Take the following example: process A is holding the fuse device fd
> and is forwarding requests and replies to/from process B via a pipe.
> So basically
On Mon, Jul 23, 2018 at 5:19 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
>> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>>
Biggest conceptual problem: your definition of fuse-server
On Mon, Jul 23, 2018 at 5:19 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
>> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>>
Biggest conceptual problem: your definition of fuse-server
On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>
>>> Biggest conceptual problem: your definition of fuse-server is weak.
>>> Take the following example: process A is holding
On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>
>>> Biggest conceptual problem: your definition of fuse-server is weak.
>>> Take the following example: process A is holding
On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests and replies
On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests and replies
On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>>> git tree: upstream
>>> console output:
On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>>> git tree: upstream
>>> console output:
On Mon, Jul 23, 2018 at 2:46 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 2:33 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
On Mon, Jul 23, 2018 at 2:46 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 2:33 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
On Mon, Jul 23, 2018 at 2:33 PM, Miklos Szeredi wrote:
On Mon, Jul 23, 2018 at 9:59 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
> git tree: upstream
> console output:
On Mon, Jul 23, 2018 at 2:33 PM, Miklos Szeredi wrote:
On Mon, Jul 23, 2018 at 9:59 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
> git tree: upstream
> console output:
On Mon, Jul 23, 2018 at 2:22 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 2:12 PM, Miklos Szeredi wrote:
>> On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
>>> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
>>> wrote:
Hello,
syzbot found the following crash on:
On Mon, Jul 23, 2018 at 2:22 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 2:12 PM, Miklos Szeredi wrote:
>> On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
>>> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
>>> wrote:
Hello,
syzbot found the following crash on:
On Mon, Jul 23, 2018 at 2:12 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
>> wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>>> git tree:
On Mon, Jul 23, 2018 at 2:12 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
>> wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>>> git tree:
On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>> git tree: upstream
>> console output:
On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>> git tree: upstream
>> console output:
On Mon, Jul 23, 2018 at 9:59 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1324f79440
> kernel config:
On Mon, Jul 23, 2018 at 9:59 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1324f79440
> kernel config:
28 matches
Mail list logo