# Re: \[PATCH 1/9\] kernel: add a PF\_FORCE\_COMPAT flag

- From: Christoph Hellwig \<hch@lst.de\>
- Date: 2020-09-18 13:44:13 
- List: linux-block
- Page: https://ratatoskr.run/linux-block/2020/09/189077
- Thread: https://ratatoskr.run/linux-arm-kernel/2020/09/189069/t.md

```text
On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote:
> >  	/* Vector 0x110 is LINUX_32BIT_SYSCALL_TRAP */
> > -	return pt_regs_trap_type(current_pt_regs()) == 0x110;
> > +	return pt_regs_trap_type(current_pt_regs()) == 0x110 ||
> > +		(current->flags & PF_FORCE_COMPAT);
> 
> Can't say I like that approach ;-/  Reasoning about the behaviour is much
> harder when it's controlled like that - witness set_fs() shite...

I don't particularly like it either.  But do you have a better idea
how to deal with io_uring vs compat tasks?
```
