On Fri, May 11, 2018 at 12:53:36PM +0300, Nikolay Borisov wrote:
>
>
> On 11.05.2018 09:30, Omar Sandoval wrote:
> > From: Omar Sandoval
> >
> > Hi, everyone,
> >
> > Btrfs currently abuses current->journal_info in btrfs_direct_IO() in
> > order to pass around some state to
On Fri, May 11, 2018 at 12:53:36PM +0300, Nikolay Borisov wrote:
>
>
> On 11.05.2018 09:30, Omar Sandoval wrote:
> > From: Omar Sandoval
> >
> > Hi, everyone,
> >
> > Btrfs currently abuses current->journal_info in btrfs_direct_IO() in
> > order to pass around some state to
On 11.05.2018 09:30, Omar Sandoval wrote:
> From: Omar Sandoval
>
> Hi, everyone,
>
> Btrfs currently abuses current->journal_info in btrfs_direct_IO() in
> order to pass around some state to get_block() and submit_io(). This
> hack is ugly and unnecessary because the data we
On Thu, May 10, 2018 at 11:30:09PM -0700, Omar Sandoval wrote:
> From: Omar Sandoval
>
> Hi, everyone,
>
> Btrfs currently abuses current->journal_info in btrfs_direct_IO() in
> order to pass around some state to get_block() and submit_io(). This
> hack is ugly and unnecessary
From: Omar Sandoval
Hi, everyone,
Btrfs currently abuses current->journal_info in btrfs_direct_IO() in
order to pass around some state to get_block() and submit_io(). This
hack is ugly and unnecessary because the data we pass around is only
used in one call frame. Robbie Ko also